0001 # SPDX-License-Identifier: GPL-2.0-only
0002 #
0003 # Input misc drivers configuration
0004 #
0005 menuconfig INPUT_MISC
0006 bool "Miscellaneous devices"
0007 help
0008 Say Y here, and a list of miscellaneous input drivers will be displayed.
0009 Everything that didn't fit into the other categories is here. This option
0010 doesn't affect the kernel.
0011
0012 If unsure, say Y.
0013
0014 if INPUT_MISC
0015
0016 config INPUT_88PM860X_ONKEY
0017 tristate "88PM860x ONKEY support"
0018 depends on MFD_88PM860X
0019 help
0020 Support the ONKEY of Marvell 88PM860x PMICs as an input device
0021 reporting power button status.
0022
0023 To compile this driver as a module, choose M here: the module
0024 will be called 88pm860x_onkey.
0025
0026 config INPUT_88PM80X_ONKEY
0027 tristate "88PM80x ONKEY support"
0028 depends on MFD_88PM800
0029 help
0030 Support the ONKEY of Marvell 88PM80x PMICs as an input device
0031 reporting power button status.
0032
0033 To compile this driver as a module, choose M here: the module
0034 will be called 88pm80x_onkey.
0035
0036 config INPUT_AB8500_PONKEY
0037 tristate "AB8500 Pon (PowerOn) Key"
0038 depends on AB8500_CORE
0039 help
0040 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
0041 Mix-Sig PMIC.
0042
0043 To compile this driver as a module, choose M here: the module
0044 will be called ab8500-ponkey.
0045
0046 config INPUT_AD714X
0047 tristate "Analog Devices AD714x Capacitance Touch Sensor"
0048 help
0049 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
0050
0051 You should select a bus connection too.
0052
0053 To compile this driver as a module, choose M here: the
0054 module will be called ad714x.
0055
0056 config INPUT_AD714X_I2C
0057 tristate "support I2C bus connection"
0058 depends on INPUT_AD714X && I2C
0059 default y
0060 help
0061 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
0062
0063 To compile this driver as a module, choose M here: the
0064 module will be called ad714x-i2c.
0065
0066 config INPUT_AD714X_SPI
0067 tristate "support SPI bus connection"
0068 depends on INPUT_AD714X && SPI
0069 default y
0070 help
0071 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
0072
0073 To compile this driver as a module, choose M here: the
0074 module will be called ad714x-spi.
0075
0076 config INPUT_ARIEL_PWRBUTTON
0077 tristate "Dell Wyse 3020 Power Button Driver"
0078 depends on SPI
0079 depends on MACH_MMP3_DT || COMPILE_TEST
0080 help
0081 Say Y to enable support for reporting power button status on
0082 on Dell Wyse 3020 ("Ariel") thin client.
0083
0084 To compile this driver as a module, choose M here: the module
0085 will be called ariel-pwrbutton.
0086
0087 config INPUT_ARIZONA_HAPTICS
0088 tristate "Arizona haptics support"
0089 depends on MFD_ARIZONA && SND_SOC
0090 select INPUT_FF_MEMLESS
0091 help
0092 Say Y to enable support for the haptics module in Arizona CODECs.
0093
0094 To compile this driver as a module, choose M here: the
0095 module will be called arizona-haptics.
0096
0097 config INPUT_ATC260X_ONKEY
0098 tristate "Actions Semi ATC260x PMIC ONKEY"
0099 depends on MFD_ATC260X
0100 help
0101 Support the ONKEY of ATC260x PMICs as an input device reporting
0102 power button status. ONKEY can be used to wakeup from low power
0103 modes and force a reset on long press.
0104
0105 To compile this driver as a module, choose M here: the
0106 module will be called atc260x-onkey.
0107
0108 config INPUT_ATMEL_CAPTOUCH
0109 tristate "Atmel Capacitive Touch Button Driver"
0110 depends on OF || COMPILE_TEST
0111 depends on I2C
0112 help
0113 Say Y here if an Atmel Capacitive Touch Button device which
0114 implements "captouch" protocol is connected to I2C bus. Typically
0115 this device consists of Atmel Touch sensor controlled by AtMegaXX
0116 MCU running firmware based on Qtouch library.
0117 One should find "atmel,captouch" node in the board specific DTS.
0118
0119 To compile this driver as a module, choose M here: the
0120 module will be called atmel_captouch.
0121
0122 config INPUT_BMA150
0123 tristate "BMA150/SMB380 acceleration sensor support"
0124 depends on I2C
0125 help
0126 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
0127 acceleration sensor hooked to an I2C bus.
0128
0129 To compile this driver as a module, choose M here: the
0130 module will be called bma150.
0131
0132 config INPUT_E3X0_BUTTON
0133 tristate "NI Ettus Research USRP E3xx Button support."
0134 default n
0135 help
0136 Say Y here to enable support for the NI Ettus Research
0137 USRP E3xx Button.
0138
0139 To compile this driver as a module, choose M here: the
0140 module will be called e3x0_button.
0141
0142 config INPUT_PCSPKR
0143 tristate "PC Speaker support"
0144 depends on PCSPKR_PLATFORM
0145 help
0146 Say Y here if you want the standard PC Speaker to be used for
0147 bells and whistles.
0148
0149 If unsure, say Y.
0150
0151 To compile this driver as a module, choose M here: the
0152 module will be called pcspkr.
0153
0154 config INPUT_PM8941_PWRKEY
0155 tristate "Qualcomm PM8941 power key support"
0156 depends on MFD_SPMI_PMIC
0157 help
0158 Say Y here if you want support for the power key usually found
0159 on boards using a Qualcomm PM8941 compatible PMIC.
0160
0161 If unsure, say Y.
0162
0163 To compile this driver as a module, choose M here: the module
0164 will be called pm8941-pwrkey.
0165
0166 config INPUT_PM8XXX_VIBRATOR
0167 tristate "Qualcomm PM8XXX vibrator support"
0168 depends on MFD_PM8XXX || MFD_SPMI_PMIC
0169 select INPUT_FF_MEMLESS
0170 help
0171 This option enables device driver support for the vibrator
0172 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
0173 from input framework.
0174
0175 To compile this driver as module, choose M here: the
0176 module will be called pm8xxx-vibrator.
0177
0178 config INPUT_PMIC8XXX_PWRKEY
0179 tristate "PMIC8XXX power key support"
0180 depends on MFD_PM8XXX
0181 help
0182 Say Y here if you want support for the PMIC8XXX power key.
0183
0184 If unsure, say N.
0185
0186 To compile this driver as a module, choose M here: the
0187 module will be called pmic8xxx-pwrkey.
0188
0189 config INPUT_SPARCSPKR
0190 tristate "SPARC Speaker support"
0191 depends on PCI && SPARC64
0192 help
0193 Say Y here if you want the standard Speaker on Sparc PCI systems
0194 to be used for bells and whistles.
0195
0196 If unsure, say Y.
0197
0198 To compile this driver as a module, choose M here: the
0199 module will be called sparcspkr.
0200
0201 config INPUT_M68K_BEEP
0202 tristate "M68k Beeper support"
0203 depends on M68K
0204
0205 config INPUT_MAX77650_ONKEY
0206 tristate "Maxim MAX77650 ONKEY support"
0207 depends on MFD_MAX77650
0208 help
0209 Support the ONKEY of the MAX77650 PMIC as an input device.
0210
0211 To compile this driver as a module, choose M here: the module
0212 will be called max77650-onkey.
0213
0214 config INPUT_MAX77693_HAPTIC
0215 tristate "MAXIM MAX77693/MAX77843 haptic controller support"
0216 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
0217 select INPUT_FF_MEMLESS
0218 help
0219 This option enables support for the haptic controller on
0220 MAXIM MAX77693 and MAX77843 chips.
0221
0222 To compile this driver as module, choose M here: the
0223 module will be called max77693-haptic.
0224
0225 config INPUT_MAX8925_ONKEY
0226 tristate "MAX8925 ONKEY support"
0227 depends on MFD_MAX8925
0228 help
0229 Support the ONKEY of MAX8925 PMICs as an input device
0230 reporting power button status.
0231
0232 To compile this driver as a module, choose M here: the module
0233 will be called max8925_onkey.
0234
0235 config INPUT_MAX8997_HAPTIC
0236 tristate "MAXIM MAX8997 haptic controller support"
0237 depends on PWM && MFD_MAX8997
0238 select INPUT_FF_MEMLESS
0239 help
0240 This option enables device driver support for the haptic controller
0241 on MAXIM MAX8997 chip. This driver supports ff-memless interface
0242 from input framework.
0243
0244 To compile this driver as module, choose M here: the
0245 module will be called max8997-haptic.
0246
0247 config INPUT_MC13783_PWRBUTTON
0248 tristate "MC13783 ON buttons"
0249 depends on MFD_MC13XXX
0250 help
0251 Support the ON buttons of MC13783 PMIC as an input device
0252 reporting power button status.
0253
0254 To compile this driver as a module, choose M here: the module
0255 will be called mc13783-pwrbutton.
0256
0257 config INPUT_MMA8450
0258 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
0259 depends on I2C
0260 help
0261 Say Y here if you want to support Freescale's MMA8450 Accelerometer
0262 through I2C interface.
0263
0264 To compile this driver as a module, choose M here: the
0265 module will be called mma8450.
0266
0267 config INPUT_APANEL
0268 tristate "Fujitsu Lifebook Application Panel buttons"
0269 depends on X86 && I2C && LEDS_CLASS
0270 select CHECK_SIGNATURE
0271 help
0272 Say Y here for support of the Application Panel buttons, used on
0273 Fujitsu Lifebook. These are attached to the mainboard through
0274 an SMBus interface managed by the I2C Intel ICH (i801) driver,
0275 which you should also build for this kernel.
0276
0277 To compile this driver as a module, choose M here: the module will
0278 be called apanel.
0279
0280 config INPUT_GPIO_BEEPER
0281 tristate "Generic GPIO Beeper support"
0282 depends on GPIOLIB || COMPILE_TEST
0283 help
0284 Say Y here if you have a beeper connected to a GPIO pin.
0285
0286 To compile this driver as a module, choose M here: the
0287 module will be called gpio-beeper.
0288
0289 config INPUT_GPIO_DECODER
0290 tristate "Polled GPIO Decoder Input driver"
0291 depends on GPIOLIB || COMPILE_TEST
0292 help
0293 Say Y here if you want driver to read status of multiple GPIO
0294 lines and report the encoded value as an absolute integer to
0295 input subsystem.
0296
0297 To compile this driver as a module, choose M here: the module
0298 will be called gpio_decoder.
0299
0300 config INPUT_GPIO_VIBRA
0301 tristate "GPIO vibrator support"
0302 depends on GPIOLIB || COMPILE_TEST
0303 select INPUT_FF_MEMLESS
0304 help
0305 Say Y here to get support for GPIO based vibrator devices.
0306
0307 If unsure, say N.
0308
0309 To compile this driver as a module, choose M here: the module will be
0310 called gpio-vibra.
0311
0312 config INPUT_COBALT_BTNS
0313 tristate "Cobalt button interface"
0314 depends on MIPS_COBALT
0315 help
0316 Say Y here if you want to support MIPS Cobalt button interface.
0317
0318 To compile this driver as a module, choose M here: the
0319 module will be called cobalt_btns.
0320
0321 config INPUT_CPCAP_PWRBUTTON
0322 tristate "CPCAP OnKey"
0323 depends on MFD_CPCAP
0324 help
0325 Say Y here if you want to enable power key reporting via the
0326 Motorola CPCAP chip.
0327
0328 To compile this driver as a module, choose M here. The module will
0329 be called cpcap-pwrbutton.
0330
0331 config INPUT_WISTRON_BTNS
0332 tristate "x86 Wistron laptop button interface"
0333 depends on X86_32
0334 select INPUT_SPARSEKMAP
0335 select NEW_LEDS
0336 select LEDS_CLASS
0337 select CHECK_SIGNATURE
0338 help
0339 Say Y here for support of Wistron laptop button interfaces, used on
0340 laptops of various brands, including Acer and Fujitsu-Siemens. If
0341 available, mail and wifi LEDs will be controllable via /sys/class/leds.
0342
0343 To compile this driver as a module, choose M here: the module will
0344 be called wistron_btns.
0345
0346 config INPUT_ATLAS_BTNS
0347 tristate "x86 Atlas button interface"
0348 depends on X86 && ACPI
0349 help
0350 Say Y here for support of Atlas wallmount touchscreen buttons.
0351 The events will show up as scancodes F1 through F9 via evdev.
0352
0353 To compile this driver as a module, choose M here: the module will
0354 be called atlas_btns.
0355
0356 config INPUT_ATI_REMOTE2
0357 tristate "ATI / Philips USB RF remote control"
0358 depends on USB_ARCH_HAS_HCD
0359 select USB
0360 help
0361 Say Y here if you want to use an ATI or Philips USB RF remote control.
0362 These are RF remotes with USB receivers.
0363 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
0364 and is also available as a separate product.
0365 This driver provides mouse pointer, left and right mouse buttons,
0366 and maps all the other remote buttons to keypress events.
0367
0368 To compile this driver as a module, choose M here: the module will be
0369 called ati_remote2.
0370
0371 config INPUT_KEYSPAN_REMOTE
0372 tristate "Keyspan DMR USB remote control"
0373 depends on USB_ARCH_HAS_HCD
0374 select USB
0375 help
0376 Say Y here if you want to use a Keyspan DMR USB remote control.
0377 Currently only the UIA-11 type of receiver has been tested. The tag
0378 on the receiver that connects to the USB port should have a P/N that
0379 will tell you what type of DMR you have. The UIA-10 type is not
0380 supported at this time. This driver maps all buttons to keypress
0381 events.
0382
0383 To compile this driver as a module, choose M here: the module will
0384 be called keyspan_remote.
0385
0386 config INPUT_KXTJ9
0387 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
0388 depends on I2C
0389 help
0390 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
0391 accelerometer.
0392
0393 To compile this driver as a module, choose M here: the module will
0394 be called kxtj9.
0395
0396 config INPUT_POWERMATE
0397 tristate "Griffin PowerMate and Contour Jog support"
0398 depends on USB_ARCH_HAS_HCD
0399 select USB
0400 help
0401 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
0402 These are aluminum dials which can measure clockwise and anticlockwise
0403 rotation. The dial also acts as a pushbutton. The base contains an LED
0404 which can be instructed to pulse or to switch to a particular intensity.
0405
0406 You can download userspace tools from
0407 <http://sowerbutts.com/powermate/>.
0408
0409 To compile this driver as a module, choose M here: the
0410 module will be called powermate.
0411
0412 config INPUT_YEALINK
0413 tristate "Yealink usb-p1k voip phone"
0414 depends on USB_ARCH_HAS_HCD
0415 select USB
0416 help
0417 Say Y here if you want to enable keyboard and LCD functions of the
0418 Yealink usb-p1k usb phones. The audio part is enabled by the generic
0419 usb sound driver, so you might want to enable that as well.
0420
0421 For information about how to use these additional functions, see
0422 <file:Documentation/input/devices/yealink.rst>.
0423
0424 To compile this driver as a module, choose M here: the module will be
0425 called yealink.
0426
0427 config INPUT_CM109
0428 tristate "C-Media CM109 USB I/O Controller"
0429 depends on USB_ARCH_HAS_HCD
0430 select USB
0431 help
0432 Say Y here if you want to enable keyboard and buzzer functions of the
0433 C-Media CM109 usb phones. The audio part is enabled by the generic
0434 usb sound driver, so you might want to enable that as well.
0435
0436 To compile this driver as a module, choose M here: the module will be
0437 called cm109.
0438
0439 config INPUT_REGULATOR_HAPTIC
0440 tristate "Regulator haptics support"
0441 depends on REGULATOR
0442 select INPUT_FF_MEMLESS
0443 help
0444 This option enables device driver support for the haptic controlled
0445 by a regulator. This driver supports ff-memless interface
0446 from input framework.
0447
0448 To compile this driver as a module, choose M here: the
0449 module will be called regulator-haptic.
0450
0451 config INPUT_RETU_PWRBUTTON
0452 tristate "Retu Power button Driver"
0453 depends on MFD_RETU
0454 help
0455 Say Y here if you want to enable power key reporting via the
0456 Retu chips found in Nokia Internet Tablets (770, N800, N810).
0457
0458 To compile this driver as a module, choose M here. The module will
0459 be called retu-pwrbutton.
0460
0461 config INPUT_TPS65218_PWRBUTTON
0462 tristate "TPS65218 Power button driver"
0463 depends on (MFD_TPS65217 || MFD_TPS65218)
0464 help
0465 Say Y here if you want to enable power button reporting for
0466 TPS65217 and TPS65218 Power Management IC devices.
0467
0468 To compile this driver as a module, choose M here. The module will
0469 be called tps65218-pwrbutton.
0470
0471 config INPUT_AXP20X_PEK
0472 tristate "X-Powers AXP20X power button driver"
0473 depends on MFD_AXP20X
0474 help
0475 Say Y here if you want to enable power key reporting via the
0476 AXP20X PMIC.
0477
0478 To compile this driver as a module, choose M here. The module will
0479 be called axp20x-pek.
0480
0481
0482 config INPUT_TWL4030_PWRBUTTON
0483 tristate "TWL4030 Power button Driver"
0484 depends on TWL4030_CORE
0485 help
0486 Say Y here if you want to enable power key reporting via the
0487 TWL4030 family of chips.
0488
0489 To compile this driver as a module, choose M here. The module will
0490 be called twl4030_pwrbutton.
0491
0492 config INPUT_TWL4030_VIBRA
0493 tristate "Support for TWL4030 Vibrator"
0494 depends on TWL4030_CORE
0495 select MFD_TWL4030_AUDIO
0496 select INPUT_FF_MEMLESS
0497 help
0498 This option enables support for TWL4030 Vibrator Driver.
0499
0500 To compile this driver as a module, choose M here. The module will
0501 be called twl4030_vibra.
0502
0503 config INPUT_TWL6040_VIBRA
0504 tristate "Support for TWL6040 Vibrator"
0505 depends on TWL6040_CORE
0506 select INPUT_FF_MEMLESS
0507 help
0508 This option enables support for TWL6040 Vibrator Driver.
0509
0510 To compile this driver as a module, choose M here. The module will
0511 be called twl6040_vibra.
0512
0513 config INPUT_UINPUT
0514 tristate "User level driver support"
0515 help
0516 Say Y here if you want to support user level drivers for input
0517 subsystem accessible under char device 10:223 - /dev/input/uinput.
0518
0519 To compile this driver as a module, choose M here: the
0520 module will be called uinput.
0521
0522 config INPUT_SGI_BTNS
0523 tristate "SGI Indy/O2 volume button interface"
0524 depends on SGI_IP22 || SGI_IP32
0525 help
0526 Say Y here if you want to support SGI Indy/O2 volume button interface.
0527
0528 To compile this driver as a module, choose M here: the
0529 module will be called sgi_btns.
0530
0531 config HP_SDC_RTC
0532 tristate "HP SDC Real Time Clock"
0533 depends on (GSC || HP300) && SERIO
0534 select HP_SDC
0535 help
0536 Say Y here if you want to support the built-in real time clock
0537 of the HP SDC controller.
0538
0539 config INPUT_PALMAS_PWRBUTTON
0540 tristate "Palmas Power button Driver"
0541 depends on MFD_PALMAS
0542 help
0543 Say Y here if you want to enable power key reporting via the
0544 Palmas family of PMICs.
0545
0546 To compile this driver as a module, choose M here. The module will
0547 be called palmas_pwrbutton.
0548
0549 config INPUT_PCF50633_PMU
0550 tristate "PCF50633 PMU events"
0551 depends on MFD_PCF50633
0552 help
0553 Say Y to include support for delivering PMU events via input
0554 layer on NXP PCF50633.
0555
0556 config INPUT_PCF8574
0557 tristate "PCF8574 Keypad input device"
0558 depends on I2C
0559 help
0560 Say Y here if you want to support a keypad connected via I2C
0561 with a PCF8574.
0562
0563 To compile this driver as a module, choose M here: the
0564 module will be called pcf8574_keypad.
0565
0566 config INPUT_PWM_BEEPER
0567 tristate "PWM beeper support"
0568 depends on PWM
0569 help
0570 Say Y here to get support for PWM based beeper devices.
0571
0572 If unsure, say N.
0573
0574 To compile this driver as a module, choose M here: the module will be
0575 called pwm-beeper.
0576
0577 config INPUT_PWM_VIBRA
0578 tristate "PWM vibrator support"
0579 depends on PWM
0580 select INPUT_FF_MEMLESS
0581 help
0582 Say Y here to get support for PWM based vibrator devices.
0583
0584 If unsure, say N.
0585
0586 To compile this driver as a module, choose M here: the module will be
0587 called pwm-vibra.
0588
0589 config INPUT_RK805_PWRKEY
0590 tristate "Rockchip RK805 PMIC power key support"
0591 depends on MFD_RK808
0592 help
0593 Select this option to enable power key driver for RK805.
0594
0595 If unsure, say N.
0596
0597 To compile this driver as a module, choose M here: the module will be
0598 called rk805_pwrkey.
0599
0600 config INPUT_GPIO_ROTARY_ENCODER
0601 tristate "Rotary encoders connected to GPIO pins"
0602 depends on GPIOLIB || COMPILE_TEST
0603 help
0604 Say Y here to add support for rotary encoders connected to GPIO lines.
0605 Check file:Documentation/input/devices/rotary-encoder.rst for more
0606 information.
0607
0608 To compile this driver as a module, choose M here: the
0609 module will be called rotary_encoder.
0610
0611 config INPUT_RB532_BUTTON
0612 tristate "Mikrotik Routerboard 532 button interface"
0613 depends on MIKROTIK_RB532
0614 depends on GPIOLIB
0615 help
0616 Say Y here if you want support for the S1 button built into
0617 Mikrotik's Routerboard 532.
0618
0619 To compile this driver as a module, choose M here: the
0620 module will be called rb532_button.
0621
0622 config INPUT_DA7280_HAPTICS
0623 tristate "Dialog Semiconductor DA7280 haptics support"
0624 depends on INPUT && I2C
0625 select REGMAP_I2C
0626 help
0627 Say Y to enable support for the Dialog DA7280 haptics driver.
0628 The haptics can be controlled by PWM or GPIO
0629 with I2C communication.
0630
0631 To compile this driver as a module, choose M here: the
0632 module will be called da7280.
0633
0634 config INPUT_DA9052_ONKEY
0635 tristate "Dialog DA9052/DA9053 Onkey"
0636 depends on PMIC_DA9052
0637 help
0638 Support the ONKEY of Dialog DA9052 PMICs as an input device
0639 reporting power button status.
0640
0641 To compile this driver as a module, choose M here: the
0642 module will be called da9052_onkey.
0643
0644 config INPUT_DA9055_ONKEY
0645 tristate "Dialog Semiconductor DA9055 ONKEY"
0646 depends on MFD_DA9055
0647 help
0648 Support the ONKEY of DA9055 PMICs as an input device
0649 reporting power button status.
0650
0651 To compile this driver as a module, choose M here: the module
0652 will be called da9055_onkey.
0653
0654 config INPUT_DA9063_ONKEY
0655 tristate "Dialog DA9063/62/61 OnKey"
0656 depends on MFD_DA9063 || MFD_DA9062
0657 help
0658 Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
0659 Management ICs as an input device capable of reporting the
0660 power button status.
0661
0662 To compile this driver as a module, choose M here: the module
0663 will be called da9063_onkey.
0664
0665 config INPUT_DM355EVM
0666 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
0667 depends on MFD_DM355EVM_MSP
0668 select INPUT_SPARSEKMAP
0669 help
0670 Supports the pushbuttons and IR remote used with
0671 the DM355 EVM board.
0672
0673 To compile this driver as a module, choose M here: the
0674 module will be called dm355evm_keys.
0675
0676 config INPUT_WM831X_ON
0677 tristate "WM831X ON pin"
0678 depends on MFD_WM831X
0679 help
0680 Support the ON pin of WM831X PMICs as an input device
0681 reporting power button status.
0682
0683 To compile this driver as a module, choose M here: the module
0684 will be called wm831x_on.
0685
0686 config INPUT_PCAP
0687 tristate "Motorola EZX PCAP misc input events"
0688 depends on EZX_PCAP
0689 help
0690 Say Y here if you want to use Power key and Headphone button
0691 on Motorola EZX phones.
0692
0693 To compile this driver as a module, choose M here: the
0694 module will be called pcap_keys.
0695
0696 config INPUT_ADXL34X
0697 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
0698 default n
0699 help
0700 Say Y here if you have a Accelerometer interface using the
0701 ADXL345/6 controller, and your board-specific initialization
0702 code includes that in its table of devices.
0703
0704 This driver can use either I2C or SPI communication to the
0705 ADXL345/6 controller. Select the appropriate method for
0706 your system.
0707
0708 If unsure, say N (but it's safe to say "Y").
0709
0710 To compile this driver as a module, choose M here: the
0711 module will be called adxl34x.
0712
0713 config INPUT_ADXL34X_I2C
0714 tristate "support I2C bus connection"
0715 depends on INPUT_ADXL34X && I2C
0716 default y
0717 help
0718 Say Y here if you have ADXL345/6 hooked to an I2C bus.
0719
0720 To compile this driver as a module, choose M here: the
0721 module will be called adxl34x-i2c.
0722
0723 config INPUT_ADXL34X_SPI
0724 tristate "support SPI bus connection"
0725 depends on INPUT_ADXL34X && SPI
0726 default y
0727 help
0728 Say Y here if you have ADXL345/6 hooked to a SPI bus.
0729
0730 To compile this driver as a module, choose M here: the
0731 module will be called adxl34x-spi.
0732
0733 config INPUT_IMS_PCU
0734 tristate "IMS Passenger Control Unit driver"
0735 depends on USB
0736 depends on LEDS_CLASS
0737 help
0738 Say Y here if you have system with IMS Rave Passenger Control Unit.
0739
0740 To compile this driver as a module, choose M here: the module will be
0741 called ims_pcu.
0742
0743 config INPUT_IQS269A
0744 tristate "Azoteq IQS269A capacitive touch controller"
0745 depends on I2C
0746 select REGMAP_I2C
0747 help
0748 Say Y to enable support for the Azoteq IQS269A capacitive
0749 touch controller.
0750
0751 To compile this driver as a module, choose M here: the
0752 module will be called iqs269a.
0753
0754 config INPUT_IQS626A
0755 tristate "Azoteq IQS626A capacitive touch controller"
0756 depends on I2C
0757 select REGMAP_I2C
0758 help
0759 Say Y to enable support for the Azoteq IQS626A capacitive
0760 touch controller.
0761
0762 To compile this driver as a module, choose M here: the
0763 module will be called iqs626a.
0764
0765 config INPUT_IQS7222
0766 tristate "Azoteq IQS7222A/B/C capacitive touch controller"
0767 depends on I2C
0768 help
0769 Say Y to enable support for the Azoteq IQS7222A/B/C family
0770 of capacitive touch controllers.
0771
0772 To compile this driver as a module, choose M here: the
0773 module will be called iqs7222.
0774
0775 config INPUT_CMA3000
0776 tristate "VTI CMA3000 Tri-axis accelerometer"
0777 help
0778 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
0779 driver
0780
0781 This driver currently only supports I2C interface to the
0782 controller. Also select the I2C method.
0783
0784 If unsure, say N
0785
0786 To compile this driver as a module, choose M here: the
0787 module will be called cma3000_d0x.
0788
0789 config INPUT_CMA3000_I2C
0790 tristate "Support I2C bus connection"
0791 depends on INPUT_CMA3000 && I2C
0792 help
0793 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
0794 through I2C interface.
0795
0796 To compile this driver as a module, choose M here: the
0797 module will be called cma3000_d0x_i2c.
0798
0799 config INPUT_XEN_KBDDEV_FRONTEND
0800 tristate "Xen virtual keyboard and mouse support"
0801 depends on XEN
0802 default y
0803 select XEN_XENBUS_FRONTEND
0804 help
0805 This driver implements the front-end of the Xen virtual
0806 keyboard and mouse device driver. It communicates with a back-end
0807 in another domain.
0808
0809 To compile this driver as a module, choose M here: the
0810 module will be called xen-kbdfront.
0811
0812 config INPUT_IDEAPAD_SLIDEBAR
0813 tristate "IdeaPad Laptop Slidebar"
0814 depends on INPUT
0815 depends on SERIO_I8042
0816 help
0817 Say Y here if you have an IdeaPad laptop with a slidebar.
0818
0819 To compile this driver as a module, choose M here: the
0820 module will be called ideapad_slidebar.
0821
0822 config INPUT_SOC_BUTTON_ARRAY
0823 tristate "Windows-compatible SoC Button Array"
0824 depends on KEYBOARD_GPIO && ACPI
0825 help
0826 Say Y here if you have a SoC-based tablet that originally runs
0827 Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later.
0828
0829 To compile this driver as a module, choose M here: the
0830 module will be called soc_button_array.
0831
0832 config INPUT_DRV260X_HAPTICS
0833 tristate "TI DRV260X haptics support"
0834 depends on INPUT && I2C
0835 depends on GPIOLIB || COMPILE_TEST
0836 select INPUT_FF_MEMLESS
0837 select REGMAP_I2C
0838 help
0839 Say Y to enable support for the TI DRV260X haptics driver.
0840
0841 To compile this driver as a module, choose M here: the
0842 module will be called drv260x-haptics.
0843
0844 config INPUT_DRV2665_HAPTICS
0845 tristate "TI DRV2665 haptics support"
0846 depends on INPUT && I2C
0847 select INPUT_FF_MEMLESS
0848 select REGMAP_I2C
0849 help
0850 Say Y to enable support for the TI DRV2665 haptics driver.
0851
0852 To compile this driver as a module, choose M here: the
0853 module will be called drv2665-haptics.
0854
0855 config INPUT_DRV2667_HAPTICS
0856 tristate "TI DRV2667 haptics support"
0857 depends on INPUT && I2C
0858 select INPUT_FF_MEMLESS
0859 select REGMAP_I2C
0860 help
0861 Say Y to enable support for the TI DRV2667 haptics driver.
0862
0863 To compile this driver as a module, choose M here: the
0864 module will be called drv2667-haptics.
0865
0866 config INPUT_HISI_POWERKEY
0867 tristate "Hisilicon PMIC ONKEY support"
0868 depends on ARCH_HISI || COMPILE_TEST
0869 help
0870 Say Y to enable support for PMIC ONKEY.
0871
0872 To compile this driver as a module, choose M here: the
0873 module will be called hisi_powerkey.
0874
0875 config INPUT_RAVE_SP_PWRBUTTON
0876 tristate "RAVE SP Power button Driver"
0877 depends on RAVE_SP_CORE
0878 help
0879 Say Y here if you want to enable power key reporting from RAVE SP
0880
0881 To compile this driver as a module, choose M here: the
0882 module will be called rave-sp-pwrbutton.
0883
0884 config INPUT_SC27XX_VIBRA
0885 tristate "Spreadtrum sc27xx vibrator support"
0886 depends on MFD_SC27XX_PMIC || COMPILE_TEST
0887 select INPUT_FF_MEMLESS
0888 help
0889 This option enables support for Spreadtrum sc27xx vibrator driver.
0890
0891 To compile this driver as a module, choose M here. The module will
0892 be called sc27xx_vibra.
0893
0894 config INPUT_STPMIC1_ONKEY
0895 tristate "STPMIC1 PMIC Onkey support"
0896 depends on MFD_STPMIC1
0897 help
0898 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
0899 can be used to wakeup from low power modes and force a shut-down on
0900 long press.
0901
0902 To compile this driver as a module, choose M here: the
0903 module will be called stpmic1_onkey.
0904
0905 endif
