1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Input misc drivers configuration 4# 5menuconfig INPUT_MISC 6 bool "Miscellaneous devices" 7 help 8 Say Y here, and a list of miscellaneous input drivers will be displayed. 9 Everything that didn't fit into the other categories is here. This option 10 doesn't affect the kernel. 11 12 If unsure, say Y. 13 14if INPUT_MISC 15 16config INPUT_88PM860X_ONKEY 17 tristate "88PM860x ONKEY support" 18 depends on MFD_88PM860X 19 help 20 Support the ONKEY of Marvell 88PM860x PMICs as an input device 21 reporting power button status. 22 23 To compile this driver as a module, choose M here: the module 24 will be called 88pm860x_onkey. 25 26config INPUT_88PM80X_ONKEY 27 tristate "88PM80x ONKEY support" 28 depends on MFD_88PM800 29 help 30 Support the ONKEY of Marvell 88PM80x PMICs as an input device 31 reporting power button status. 32 33 To compile this driver as a module, choose M here: the module 34 will be called 88pm80x_onkey. 35 36config INPUT_88PM886_ONKEY 37 tristate "Marvell 88PM886 onkey support" 38 depends on MFD_88PM886_PMIC 39 help 40 Support the onkey of Marvell 88PM886 PMIC as an input device 41 reporting power button status. 42 43config INPUT_AB8500_PONKEY 44 tristate "AB8500 Pon (PowerOn) Key" 45 depends on AB8500_CORE 46 help 47 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500 48 Mix-Sig PMIC. 49 50 To compile this driver as a module, choose M here: the module 51 will be called ab8500-ponkey. 52 53config INPUT_AD714X 54 tristate "Analog Devices AD714x Capacitance Touch Sensor" 55 help 56 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. 57 58 You should select a bus connection too. 59 60 To compile this driver as a module, choose M here: the 61 module will be called ad714x. 62 63config INPUT_AD714X_I2C 64 tristate "support I2C bus connection" 65 depends on INPUT_AD714X && I2C 66 default y 67 help 68 Say Y here if you have AD7142/AD7147 hooked to an I2C bus. 69 70 To compile this driver as a module, choose M here: the 71 module will be called ad714x-i2c. 72 73config INPUT_AD714X_SPI 74 tristate "support SPI bus connection" 75 depends on INPUT_AD714X && SPI 76 default y 77 help 78 Say Y here if you have AD7142/AD7147 hooked to a SPI bus. 79 80 To compile this driver as a module, choose M here: the 81 module will be called ad714x-spi. 82 83config INPUT_ARIEL_PWRBUTTON 84 tristate "Dell Wyse 3020 Power Button Driver" 85 depends on SPI 86 depends on MACH_MMP3_DT || COMPILE_TEST 87 help 88 Say Y to enable support for reporting power button status on 89 on Dell Wyse 3020 ("Ariel") thin client. 90 91 To compile this driver as a module, choose M here: the module 92 will be called ariel-pwrbutton. 93 94config INPUT_ARIZONA_HAPTICS 95 tristate "Arizona haptics support" 96 depends on MFD_ARIZONA && SND_SOC 97 select INPUT_FF_MEMLESS 98 help 99 Say Y to enable support for the haptics module in Arizona CODECs. 100 101 To compile this driver as a module, choose M here: the 102 module will be called arizona-haptics. 103 104config INPUT_ATC260X_ONKEY 105 tristate "Actions Semi ATC260x PMIC ONKEY" 106 depends on MFD_ATC260X 107 help 108 Support the ONKEY of ATC260x PMICs as an input device reporting 109 power button status. ONKEY can be used to wakeup from low power 110 modes and force a reset on long press. 111 112 To compile this driver as a module, choose M here: the 113 module will be called atc260x-onkey. 114 115config INPUT_ATMEL_CAPTOUCH 116 tristate "Atmel Capacitive Touch Button Driver" 117 depends on OF 118 depends on I2C 119 help 120 Say Y here if an Atmel Capacitive Touch Button device which 121 implements "captouch" protocol is connected to I2C bus. Typically 122 this device consists of Atmel Touch sensor controlled by AtMegaXX 123 MCU running firmware based on Qtouch library. 124 One should find "atmel,captouch" node in the board specific DTS. 125 126 To compile this driver as a module, choose M here: the 127 module will be called atmel_captouch. 128 129config INPUT_BBNSM_PWRKEY 130 tristate "NXP BBNSM Power Key Driver" 131 depends on ARCH_MXC || COMPILE_TEST 132 depends on OF 133 help 134 This is the bbnsm powerkey driver for the NXP i.MX application 135 processors. 136 137 To compile this driver as a module, choose M here; the 138 module will be called bbnsm_pwrkey. 139 140config INPUT_BMA150 141 tristate "BMA150/SMB380 acceleration sensor support" 142 depends on I2C 143 help 144 Say Y here if you have Bosch Sensortec's BMA150 or SMB380 145 acceleration sensor hooked to an I2C bus. 146 147 To compile this driver as a module, choose M here: the 148 module will be called bma150. 149 150config INPUT_CS40L50_VIBRA 151 tristate "CS40L50 Haptic Driver support" 152 depends on MFD_CS40L50_CORE 153 help 154 Say Y here to enable support for Cirrus Logic's CS40L50 155 haptic driver. 156 157 To compile this driver as a module, choose M here: the 158 module will be called cs40l50-vibra. 159 160config INPUT_E3X0_BUTTON 161 tristate "NI Ettus Research USRP E3xx Button support." 162 default n 163 help 164 Say Y here to enable support for the NI Ettus Research 165 USRP E3xx Button. 166 167 To compile this driver as a module, choose M here: the 168 module will be called e3x0_button. 169 170config INPUT_PCSPKR 171 tristate "PC Speaker support" 172 depends on PCSPKR_PLATFORM 173 help 174 Say Y here if you want the standard PC Speaker to be used for 175 bells and whistles. 176 177 If unsure, say Y. 178 179 To compile this driver as a module, choose M here: the 180 module will be called pcspkr. 181 182config INPUT_PM8941_PWRKEY 183 tristate "Qualcomm PM8941 power key support" 184 depends on MFD_SPMI_PMIC 185 help 186 Say Y here if you want support for the power key usually found 187 on boards using a Qualcomm PM8941 compatible PMIC. 188 189 If unsure, say Y. 190 191 To compile this driver as a module, choose M here: the module 192 will be called pm8941-pwrkey. 193 194config INPUT_PM8XXX_VIBRATOR 195 tristate "Qualcomm PM8XXX vibrator support" 196 depends on MFD_PM8XXX || MFD_SPMI_PMIC 197 select INPUT_FF_MEMLESS 198 help 199 This option enables device driver support for the vibrator 200 on Qualcomm PM8xxx chip. This driver supports ff-memless interface 201 from input framework. 202 203 To compile this driver as module, choose M here: the 204 module will be called pm8xxx-vibrator. 205 206config INPUT_PMIC8XXX_PWRKEY 207 tristate "PMIC8XXX power key support" 208 depends on MFD_PM8XXX 209 help 210 Say Y here if you want support for the PMIC8XXX power key. 211 212 If unsure, say N. 213 214 To compile this driver as a module, choose M here: the 215 module will be called pmic8xxx-pwrkey. 216 217config INPUT_SPARCSPKR 218 tristate "SPARC Speaker support" 219 depends on PCI && SPARC64 220 help 221 Say Y here if you want the standard Speaker on Sparc PCI systems 222 to be used for bells and whistles. 223 224 If unsure, say Y. 225 226 To compile this driver as a module, choose M here: the 227 module will be called sparcspkr. 228 229config INPUT_M68K_BEEP 230 tristate "M68k Beeper support" 231 depends on M68K 232 233config INPUT_MAX77650_ONKEY 234 tristate "Maxim MAX77650 ONKEY support" 235 depends on MFD_MAX77650 236 help 237 Support the ONKEY of the MAX77650 PMIC as an input device. 238 239 To compile this driver as a module, choose M here: the module 240 will be called max77650-onkey. 241 242config INPUT_MAX77693_HAPTIC 243 tristate "MAXIM MAX77693/MAX77843 haptic controller support" 244 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM 245 select INPUT_FF_MEMLESS 246 help 247 This option enables support for the haptic controller on 248 MAXIM MAX77693 and MAX77843 chips. 249 250 To compile this driver as module, choose M here: the 251 module will be called max77693-haptic. 252 253config INPUT_MAX8925_ONKEY 254 tristate "MAX8925 ONKEY support" 255 depends on MFD_MAX8925 256 help 257 Support the ONKEY of MAX8925 PMICs as an input device 258 reporting power button status. 259 260 To compile this driver as a module, choose M here: the module 261 will be called max8925_onkey. 262 263config INPUT_MAX8997_HAPTIC 264 tristate "MAXIM MAX8997 haptic controller support" 265 depends on PWM && MFD_MAX8997 266 select INPUT_FF_MEMLESS 267 help 268 This option enables device driver support for the haptic controller 269 on MAXIM MAX8997 chip. This driver supports ff-memless interface 270 from input framework. 271 272 To compile this driver as module, choose M here: the 273 module will be called max8997-haptic. 274 275config INPUT_MC13783_PWRBUTTON 276 tristate "MC13783 ON buttons" 277 depends on MFD_MC13XXX 278 help 279 Support the ON buttons of MC13783 PMIC as an input device 280 reporting power button status. 281 282 To compile this driver as a module, choose M here: the module 283 will be called mc13783-pwrbutton. 284 285config INPUT_MMA8450 286 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" 287 depends on I2C 288 help 289 Say Y here if you want to support Freescale's MMA8450 Accelerometer 290 through I2C interface. 291 292 To compile this driver as a module, choose M here: the 293 module will be called mma8450. 294 295config INPUT_APANEL 296 tristate "Fujitsu Lifebook Application Panel buttons" 297 depends on X86 && I2C && LEDS_CLASS 298 select CHECK_SIGNATURE 299 help 300 Say Y here for support of the Application Panel buttons, used on 301 Fujitsu Lifebook. These are attached to the mainboard through 302 an SMBus interface managed by the I2C Intel ICH (i801) driver, 303 which you should also build for this kernel. 304 305 To compile this driver as a module, choose M here: the module will 306 be called apanel. 307 308config INPUT_GPIO_BEEPER 309 tristate "Generic GPIO Beeper support" 310 depends on GPIOLIB || COMPILE_TEST 311 help 312 Say Y here if you have a beeper connected to a GPIO pin. 313 314 To compile this driver as a module, choose M here: the 315 module will be called gpio-beeper. 316 317config INPUT_GPIO_DECODER 318 tristate "Polled GPIO Decoder Input driver" 319 depends on GPIOLIB || COMPILE_TEST 320 help 321 Say Y here if you want driver to read status of multiple GPIO 322 lines and report the encoded value as an absolute integer to 323 input subsystem. 324 325 To compile this driver as a module, choose M here: the module 326 will be called gpio_decoder. 327 328config INPUT_GPIO_VIBRA 329 tristate "GPIO vibrator support" 330 depends on GPIOLIB || COMPILE_TEST 331 select INPUT_FF_MEMLESS 332 help 333 Say Y here to get support for GPIO based vibrator devices. 334 335 If unsure, say N. 336 337 To compile this driver as a module, choose M here: the module will be 338 called gpio-vibra. 339 340config INPUT_COBALT_BTNS 341 tristate "Cobalt button interface" 342 depends on MIPS_COBALT 343 help 344 Say Y here if you want to support MIPS Cobalt button interface. 345 346 To compile this driver as a module, choose M here: the 347 module will be called cobalt_btns. 348 349config INPUT_CPCAP_PWRBUTTON 350 tristate "CPCAP OnKey" 351 depends on MFD_CPCAP 352 help 353 Say Y here if you want to enable power key reporting via the 354 Motorola CPCAP chip. 355 356 To compile this driver as a module, choose M here. The module will 357 be called cpcap-pwrbutton. 358 359config INPUT_WISTRON_BTNS 360 tristate "x86 Wistron laptop button interface" 361 depends on X86_32 && !UML 362 select INPUT_SPARSEKMAP 363 select NEW_LEDS 364 select LEDS_CLASS 365 select CHECK_SIGNATURE 366 help 367 Say Y here for support of Wistron laptop button interfaces, used on 368 laptops of various brands, including Acer and Fujitsu-Siemens. If 369 available, mail and wifi LEDs will be controllable via /sys/class/leds. 370 371 To compile this driver as a module, choose M here: the module will 372 be called wistron_btns. 373 374config INPUT_ATLAS_BTNS 375 tristate "x86 Atlas button interface" 376 depends on X86 && ACPI 377 help 378 Say Y here for support of Atlas wallmount touchscreen buttons. 379 The events will show up as scancodes F1 through F9 via evdev. 380 381 To compile this driver as a module, choose M here: the module will 382 be called atlas_btns. 383 384config INPUT_ATI_REMOTE2 385 tristate "ATI / Philips USB RF remote control" 386 depends on USB_ARCH_HAS_HCD 387 select USB 388 help 389 Say Y here if you want to use an ATI or Philips USB RF remote control. 390 These are RF remotes with USB receivers. 391 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 392 and is also available as a separate product. 393 This driver provides mouse pointer, left and right mouse buttons, 394 and maps all the other remote buttons to keypress events. 395 396 To compile this driver as a module, choose M here: the module will be 397 called ati_remote2. 398 399config INPUT_KEYSPAN_REMOTE 400 tristate "Keyspan DMR USB remote control" 401 depends on USB_ARCH_HAS_HCD 402 select USB 403 help 404 Say Y here if you want to use a Keyspan DMR USB remote control. 405 Currently only the UIA-11 type of receiver has been tested. The tag 406 on the receiver that connects to the USB port should have a P/N that 407 will tell you what type of DMR you have. The UIA-10 type is not 408 supported at this time. This driver maps all buttons to keypress 409 events. 410 411 To compile this driver as a module, choose M here: the module will 412 be called keyspan_remote. 413 414config INPUT_KXTJ9 415 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 416 depends on I2C 417 help 418 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 419 accelerometer. 420 421 To compile this driver as a module, choose M here: the module will 422 be called kxtj9. 423 424config INPUT_POWERMATE 425 tristate "Griffin PowerMate and Contour Jog support" 426 depends on USB_ARCH_HAS_HCD 427 select USB 428 help 429 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 430 These are aluminum dials which can measure clockwise and anticlockwise 431 rotation. The dial also acts as a pushbutton. The base contains an LED 432 which can be instructed to pulse or to switch to a particular intensity. 433 434 You can download userspace tools from 435 <http://sowerbutts.com/powermate/>. 436 437 To compile this driver as a module, choose M here: the 438 module will be called powermate. 439 440config INPUT_YEALINK 441 tristate "Yealink usb-p1k voip phone" 442 depends on USB_ARCH_HAS_HCD 443 select USB 444 help 445 Say Y here if you want to enable keyboard and LCD functions of the 446 Yealink usb-p1k usb phones. The audio part is enabled by the generic 447 usb sound driver, so you might want to enable that as well. 448 449 For information about how to use these additional functions, see 450 <file:Documentation/input/devices/yealink.rst>. 451 452 To compile this driver as a module, choose M here: the module will be 453 called yealink. 454 455config INPUT_CM109 456 tristate "C-Media CM109 USB I/O Controller" 457 depends on USB_ARCH_HAS_HCD 458 select USB 459 help 460 Say Y here if you want to enable keyboard and buzzer functions of the 461 C-Media CM109 usb phones. The audio part is enabled by the generic 462 usb sound driver, so you might want to enable that as well. 463 464 To compile this driver as a module, choose M here: the module will be 465 called cm109. 466 467config INPUT_REGULATOR_HAPTIC 468 tristate "Regulator haptics support" 469 depends on REGULATOR 470 select INPUT_FF_MEMLESS 471 help 472 This option enables device driver support for the haptic controlled 473 by a regulator. This driver supports ff-memless interface 474 from input framework. 475 476 To compile this driver as a module, choose M here: the 477 module will be called regulator-haptic. 478 479config INPUT_RETU_PWRBUTTON 480 tristate "Retu Power button Driver" 481 depends on MFD_RETU 482 help 483 Say Y here if you want to enable power key reporting via the 484 Retu chips found in Nokia Internet Tablets (770, N800, N810). 485 486 To compile this driver as a module, choose M here. The module will 487 be called retu-pwrbutton. 488 489config INPUT_TPS65218_PWRBUTTON 490 tristate "TPS65218 Power button driver" 491 depends on (MFD_TPS65217 || MFD_TPS65218) 492 help 493 Say Y here if you want to enable power button reporting for 494 TPS65217 and TPS65218 Power Management IC devices. 495 496 To compile this driver as a module, choose M here. The module will 497 be called tps65218-pwrbutton. 498 499config INPUT_TPS65219_PWRBUTTON 500 tristate "TPS65219 Power button driver" 501 depends on MFD_TPS65219 502 help 503 Say Y here if you want to enable power button reporting for 504 TPS65219 Power Management IC devices. 505 506 To compile this driver as a module, choose M here. The module will 507 be called tps65219-pwrbutton. 508 509config INPUT_AXP20X_PEK 510 tristate "X-Powers AXP20X power button driver" 511 depends on MFD_AXP20X 512 help 513 Say Y here if you want to enable power key reporting via the 514 AXP20X PMIC. 515 516 To compile this driver as a module, choose M here. The module will 517 be called axp20x-pek. 518 519 520config INPUT_TWL4030_PWRBUTTON 521 tristate "TWL4030 Power button Driver" 522 depends on TWL4030_CORE 523 help 524 Say Y here if you want to enable power key reporting via the 525 TWL4030 family of chips. 526 527 To compile this driver as a module, choose M here. The module will 528 be called twl4030_pwrbutton. 529 530config INPUT_TWL4030_VIBRA 531 tristate "Support for TWL4030 Vibrator" 532 depends on TWL4030_CORE 533 select MFD_TWL4030_AUDIO 534 select INPUT_FF_MEMLESS 535 help 536 This option enables support for TWL4030 Vibrator Driver. 537 538 To compile this driver as a module, choose M here. The module will 539 be called twl4030_vibra. 540 541config INPUT_TWL6040_VIBRA 542 tristate "Support for TWL6040 Vibrator" 543 depends on TWL6040_CORE 544 select INPUT_FF_MEMLESS 545 help 546 This option enables support for TWL6040 Vibrator Driver. 547 548 To compile this driver as a module, choose M here. The module will 549 be called twl6040_vibra. 550 551config INPUT_UINPUT 552 tristate "User level driver support" 553 help 554 Say Y here if you want to support user level drivers for input 555 subsystem accessible under char device 10:223 - /dev/input/uinput. 556 557 To compile this driver as a module, choose M here: the 558 module will be called uinput. 559 560config INPUT_SGI_BTNS 561 tristate "SGI Indy/O2 volume button interface" 562 depends on SGI_IP22 || SGI_IP32 563 help 564 Say Y here if you want to support SGI Indy/O2 volume button interface. 565 566 To compile this driver as a module, choose M here: the 567 module will be called sgi_btns. 568 569config HP_SDC_RTC 570 tristate "HP SDC Real Time Clock" 571 depends on (GSC || HP300) && SERIO 572 select HP_SDC 573 help 574 Say Y here if you want to support the built-in real time clock 575 of the HP SDC controller. 576 577config INPUT_PALMAS_PWRBUTTON 578 tristate "Palmas Power button Driver" 579 depends on MFD_PALMAS 580 help 581 Say Y here if you want to enable power key reporting via the 582 Palmas family of PMICs. 583 584 To compile this driver as a module, choose M here. The module will 585 be called palmas_pwrbutton. 586 587config INPUT_PCF50633_PMU 588 tristate "PCF50633 PMU events" 589 depends on MFD_PCF50633 590 help 591 Say Y to include support for delivering PMU events via input 592 layer on NXP PCF50633. 593 594config INPUT_PCF8574 595 tristate "PCF8574 Keypad input device" 596 depends on I2C 597 help 598 Say Y here if you want to support a keypad connected via I2C 599 with a PCF8574. 600 601 To compile this driver as a module, choose M here: the 602 module will be called pcf8574_keypad. 603 604config INPUT_PWM_BEEPER 605 tristate "PWM beeper support" 606 depends on PWM 607 help 608 Say Y here to get support for PWM based beeper devices. 609 610 If unsure, say N. 611 612 To compile this driver as a module, choose M here: the module will be 613 called pwm-beeper. 614 615config INPUT_PWM_VIBRA 616 tristate "PWM vibrator support" 617 depends on PWM 618 select INPUT_FF_MEMLESS 619 help 620 Say Y here to get support for PWM based vibrator devices. 621 622 If unsure, say N. 623 624 To compile this driver as a module, choose M here: the module will be 625 called pwm-vibra. 626 627config INPUT_RK805_PWRKEY 628 tristate "Rockchip RK805 PMIC power key support" 629 depends on MFD_RK8XX 630 help 631 Select this option to enable power key driver for RK805. 632 633 If unsure, say N. 634 635 To compile this driver as a module, choose M here: the module will be 636 called rk805_pwrkey. 637 638config INPUT_GPIO_ROTARY_ENCODER 639 tristate "Rotary encoders connected to GPIO pins" 640 depends on GPIOLIB || COMPILE_TEST 641 help 642 Say Y here to add support for rotary encoders connected to GPIO lines. 643 Check file:Documentation/input/devices/rotary-encoder.rst for more 644 information. 645 646 To compile this driver as a module, choose M here: the 647 module will be called rotary_encoder. 648 649config INPUT_RB532_BUTTON 650 tristate "Mikrotik Routerboard 532 button interface" 651 depends on MIKROTIK_RB532 652 depends on GPIOLIB 653 help 654 Say Y here if you want support for the S1 button built into 655 Mikrotik's Routerboard 532. 656 657 To compile this driver as a module, choose M here: the 658 module will be called rb532_button. 659 660config INPUT_DA7280_HAPTICS 661 tristate "Dialog Semiconductor DA7280 haptics support" 662 depends on INPUT && I2C 663 select REGMAP_I2C 664 help 665 Say Y to enable support for the Dialog DA7280 haptics driver. 666 The haptics can be controlled by PWM or GPIO 667 with I2C communication. 668 669 To compile this driver as a module, choose M here: the 670 module will be called da7280. 671 672config INPUT_DA9052_ONKEY 673 tristate "Dialog DA9052/DA9053 Onkey" 674 depends on PMIC_DA9052 675 help 676 Support the ONKEY of Dialog DA9052 PMICs as an input device 677 reporting power button status. 678 679 To compile this driver as a module, choose M here: the 680 module will be called da9052_onkey. 681 682config INPUT_DA9055_ONKEY 683 tristate "Dialog Semiconductor DA9055 ONKEY" 684 depends on MFD_DA9055 685 help 686 Support the ONKEY of DA9055 PMICs as an input device 687 reporting power button status. 688 689 To compile this driver as a module, choose M here: the module 690 will be called da9055_onkey. 691 692config INPUT_DA9063_ONKEY 693 tristate "Dialog DA9063/62/61 OnKey" 694 depends on MFD_DA9063 || MFD_DA9062 695 help 696 Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power 697 Management ICs as an input device capable of reporting the 698 power button status. 699 700 To compile this driver as a module, choose M here: the module 701 will be called da9063_onkey. 702 703config INPUT_WM831X_ON 704 tristate "WM831X ON pin" 705 depends on MFD_WM831X 706 help 707 Support the ON pin of WM831X PMICs as an input device 708 reporting power button status. 709 710 To compile this driver as a module, choose M here: the module 711 will be called wm831x_on. 712 713config INPUT_PCAP 714 tristate "Motorola EZX PCAP misc input events" 715 depends on EZX_PCAP 716 help 717 Say Y here if you want to use Power key and Headphone button 718 on Motorola EZX phones. 719 720 To compile this driver as a module, choose M here: the 721 module will be called pcap_keys. 722 723config INPUT_ADXL34X 724 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 725 default n 726 help 727 Say Y here if you have a Accelerometer interface using the 728 ADXL345/6 controller, and your board-specific initialization 729 code includes that in its table of devices. 730 731 This driver can use either I2C or SPI communication to the 732 ADXL345/6 controller. Select the appropriate method for 733 your system. 734 735 If unsure, say N (but it's safe to say "Y"). 736 737 To compile this driver as a module, choose M here: the 738 module will be called adxl34x. 739 740config INPUT_ADXL34X_I2C 741 tristate "support I2C bus connection" 742 depends on INPUT_ADXL34X && I2C 743 default y 744 help 745 Say Y here if you have ADXL345/6 hooked to an I2C bus. 746 747 To compile this driver as a module, choose M here: the 748 module will be called adxl34x-i2c. 749 750config INPUT_ADXL34X_SPI 751 tristate "support SPI bus connection" 752 depends on INPUT_ADXL34X && SPI 753 default y 754 help 755 Say Y here if you have ADXL345/6 hooked to a SPI bus. 756 757 To compile this driver as a module, choose M here: the 758 module will be called adxl34x-spi. 759 760config INPUT_IBM_PANEL 761 tristate "IBM Operation Panel driver" 762 depends on I2C && I2C_SLAVE 763 help 764 Say Y here if you have an IBM Operation Panel connected to your system 765 over I2C. The panel is typically connected only to a system's service 766 processor (BMC). 767 768 If unsure, say N. 769 770 The Operation Panel is a controller with some buttons and an LCD 771 display that allows someone with physical access to the system to 772 perform various administrative tasks. This driver only supports the part 773 of the controller that sends commands to the system. 774 775 To compile this driver as a module, choose M here: the module will be 776 called ibm-panel. 777 778config INPUT_IMS_PCU 779 tristate "IMS Passenger Control Unit driver" 780 depends on USB 781 depends on LEDS_CLASS 782 help 783 Say Y here if you have system with IMS Rave Passenger Control Unit. 784 785 To compile this driver as a module, choose M here: the module will be 786 called ims_pcu. 787 788config INPUT_IQS269A 789 tristate "Azoteq IQS269A capacitive touch controller" 790 depends on I2C 791 select REGMAP_I2C 792 help 793 Say Y to enable support for the Azoteq IQS269A capacitive 794 touch controller. 795 796 To compile this driver as a module, choose M here: the 797 module will be called iqs269a. 798 799config INPUT_IQS626A 800 tristate "Azoteq IQS626A capacitive touch controller" 801 depends on I2C 802 select REGMAP_I2C 803 help 804 Say Y to enable support for the Azoteq IQS626A capacitive 805 touch controller. 806 807 To compile this driver as a module, choose M here: the 808 module will be called iqs626a. 809 810config INPUT_IQS7222 811 tristate "Azoteq IQS7222A/B/C/D capacitive touch controller" 812 depends on I2C 813 help 814 Say Y to enable support for the Azoteq IQS7222A/B/C/D family 815 of capacitive touch controllers. 816 817 To compile this driver as a module, choose M here: the 818 module will be called iqs7222. 819 820config INPUT_CMA3000 821 tristate "VTI CMA3000 Tri-axis accelerometer" 822 help 823 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 824 driver 825 826 This driver currently only supports I2C interface to the 827 controller. Also select the I2C method. 828 829 If unsure, say N 830 831 To compile this driver as a module, choose M here: the 832 module will be called cma3000_d0x. 833 834config INPUT_CMA3000_I2C 835 tristate "Support I2C bus connection" 836 depends on INPUT_CMA3000 && I2C 837 help 838 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 839 through I2C interface. 840 841 To compile this driver as a module, choose M here: the 842 module will be called cma3000_d0x_i2c. 843 844config INPUT_XEN_KBDDEV_FRONTEND 845 tristate "Xen virtual keyboard and mouse support" 846 depends on XEN 847 default y 848 select XEN_XENBUS_FRONTEND 849 help 850 This driver implements the front-end of the Xen virtual 851 keyboard and mouse device driver. It communicates with a back-end 852 in another domain. 853 854 To compile this driver as a module, choose M here: the 855 module will be called xen-kbdfront. 856 857config INPUT_IDEAPAD_SLIDEBAR 858 tristate "IdeaPad Laptop Slidebar" 859 depends on INPUT 860 depends on SERIO_I8042 861 help 862 Say Y here if you have an IdeaPad laptop with a slidebar. 863 864 To compile this driver as a module, choose M here: the 865 module will be called ideapad_slidebar. 866 867config INPUT_SOC_BUTTON_ARRAY 868 tristate "Windows-compatible SoC Button Array" 869 depends on KEYBOARD_GPIO && ACPI 870 help 871 Say Y here if you have a SoC-based tablet that originally runs 872 Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later. 873 874 To compile this driver as a module, choose M here: the 875 module will be called soc_button_array. 876 877config INPUT_DRV260X_HAPTICS 878 tristate "TI DRV260X haptics support" 879 depends on INPUT && I2C 880 depends on GPIOLIB || COMPILE_TEST 881 select INPUT_FF_MEMLESS 882 select REGMAP_I2C 883 help 884 Say Y to enable support for the TI DRV260X haptics driver. 885 886 To compile this driver as a module, choose M here: the 887 module will be called drv260x-haptics. 888 889config INPUT_DRV2665_HAPTICS 890 tristate "TI DRV2665 haptics support" 891 depends on INPUT && I2C 892 select INPUT_FF_MEMLESS 893 select REGMAP_I2C 894 help 895 Say Y to enable support for the TI DRV2665 haptics driver. 896 897 To compile this driver as a module, choose M here: the 898 module will be called drv2665-haptics. 899 900config INPUT_DRV2667_HAPTICS 901 tristate "TI DRV2667 haptics support" 902 depends on INPUT && I2C 903 select INPUT_FF_MEMLESS 904 select REGMAP_I2C 905 help 906 Say Y to enable support for the TI DRV2667 haptics driver. 907 908 To compile this driver as a module, choose M here: the 909 module will be called drv2667-haptics. 910 911config INPUT_HISI_POWERKEY 912 tristate "Hisilicon PMIC ONKEY support" 913 depends on ARCH_HISI || COMPILE_TEST 914 help 915 Say Y to enable support for PMIC ONKEY. 916 917 To compile this driver as a module, choose M here: the 918 module will be called hisi_powerkey. 919 920config INPUT_RAVE_SP_PWRBUTTON 921 tristate "RAVE SP Power button Driver" 922 depends on RAVE_SP_CORE 923 help 924 Say Y here if you want to enable power key reporting from RAVE SP 925 926 To compile this driver as a module, choose M here: the 927 module will be called rave-sp-pwrbutton. 928 929config INPUT_SC27XX_VIBRA 930 tristate "Spreadtrum sc27xx vibrator support" 931 depends on MFD_SC27XX_PMIC || COMPILE_TEST 932 select INPUT_FF_MEMLESS 933 help 934 This option enables support for Spreadtrum sc27xx vibrator driver. 935 936 To compile this driver as a module, choose M here. The module will 937 be called sc27xx_vibra. 938 939config INPUT_RT5120_PWRKEY 940 tristate "RT5120 PMIC power key support" 941 depends on MFD_RT5120 || COMPILE_TEST 942 help 943 This enables support for RT5120 PMIC power key driver. 944 945 To compile this driver as a module, choose M here. the module will 946 be called rt5120-pwrkey. 947 948config INPUT_STPMIC1_ONKEY 949 tristate "STPMIC1 PMIC Onkey support" 950 depends on MFD_STPMIC1 951 help 952 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey 953 can be used to wakeup from low power modes and force a shut-down on 954 long press. 955 956 To compile this driver as a module, choose M here: the 957 module will be called stpmic1_onkey. 958 959endif 960