1 # SPDX-License-Identifier: GPL-2.0-only
3 # Input misc drivers configuration
6 bool "Miscellaneous devices"
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.
16 config INPUT_88PM860X_ONKEY
17 tristate "88PM860x ONKEY support"
18 depends on MFD_88PM860X
20 Support the ONKEY of Marvell 88PM860x PMICs as an input device
21 reporting power button status.
23 To compile this driver as a module, choose M here: the module
24 will be called 88pm860x_onkey.
26 config INPUT_88PM80X_ONKEY
27 tristate "88PM80x ONKEY support"
28 depends on MFD_88PM800
30 Support the ONKEY of Marvell 88PM80x PMICs as an input device
31 reporting power button status.
33 To compile this driver as a module, choose M here: the module
34 will be called 88pm80x_onkey.
36 config INPUT_AB8500_PONKEY
37 tristate "AB8500 Pon (PowerOn) Key"
38 depends on AB8500_CORE
40 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
43 To compile this driver as a module, choose M here: the module
44 will be called ab8500-ponkey.
47 tristate "Analog Devices AD714x Capacitance Touch Sensor"
49 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
51 You should select a bus connection too.
53 To compile this driver as a module, choose M here: the
54 module will be called ad714x.
56 config INPUT_AD714X_I2C
57 tristate "support I2C bus connection"
58 depends on INPUT_AD714X && I2C
61 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
63 To compile this driver as a module, choose M here: the
64 module will be called ad714x-i2c.
66 config INPUT_AD714X_SPI
67 tristate "support SPI bus connection"
68 depends on INPUT_AD714X && SPI
71 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
73 To compile this driver as a module, choose M here: the
74 module will be called ad714x-spi.
76 config INPUT_ARIEL_PWRBUTTON
77 tristate "Dell Wyse 3020 Power Button Driver"
79 depends on MACH_MMP3_DT || COMPILE_TEST
81 Say Y to enable support for reporting power button status on
82 on Dell Wyse 3020 ("Ariel") thin client.
84 To compile this driver as a module, choose M here: the module
85 will be called ariel-pwrbutton.
87 config INPUT_ARIZONA_HAPTICS
88 tristate "Arizona haptics support"
89 depends on MFD_ARIZONA && SND_SOC
90 select INPUT_FF_MEMLESS
92 Say Y to enable support for the haptics module in Arizona CODECs.
94 To compile this driver as a module, choose M here: the
95 module will be called arizona-haptics.
97 config INPUT_ATC260X_ONKEY
98 tristate "Actions Semi ATC260x PMIC ONKEY"
99 depends on MFD_ATC260X
101 Support the ONKEY of ATC260x PMICs as an input device reporting
102 power button status. ONKEY can be used to wakeup from low power
103 modes and force a reset on long press.
105 To compile this driver as a module, choose M here: the
106 module will be called atc260x-onkey.
108 config INPUT_ATMEL_CAPTOUCH
109 tristate "Atmel Capacitive Touch Button Driver"
110 depends on OF || COMPILE_TEST
113 Say Y here if an Atmel Capacitive Touch Button device which
114 implements "captouch" protocol is connected to I2C bus. Typically
115 this device consists of Atmel Touch sensor controlled by AtMegaXX
116 MCU running firmware based on Qtouch library.
117 One should find "atmel,captouch" node in the board specific DTS.
119 To compile this driver as a module, choose M here: the
120 module will be called atmel_captouch.
123 tristate "BMA150/SMB380 acceleration sensor support"
126 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
127 acceleration sensor hooked to an I2C bus.
129 To compile this driver as a module, choose M here: the
130 module will be called bma150.
132 config INPUT_E3X0_BUTTON
133 tristate "NI Ettus Research USRP E3xx Button support."
136 Say Y here to enable support for the NI Ettus Research
139 To compile this driver as a module, choose M here: the
140 module will be called e3x0_button.
143 tristate "PC Speaker support"
144 depends on PCSPKR_PLATFORM
146 Say Y here if you want the standard PC Speaker to be used for
151 To compile this driver as a module, choose M here: the
152 module will be called pcspkr.
154 config INPUT_PM8941_PWRKEY
155 tristate "Qualcomm PM8941 power key support"
156 depends on MFD_SPMI_PMIC
158 Say Y here if you want support for the power key usually found
159 on boards using a Qualcomm PM8941 compatible PMIC.
163 To compile this driver as a module, choose M here: the module
164 will be called pm8941-pwrkey.
166 config INPUT_PM8XXX_VIBRATOR
167 tristate "Qualcomm PM8XXX vibrator support"
168 depends on MFD_PM8XXX || MFD_SPMI_PMIC
169 select INPUT_FF_MEMLESS
171 This option enables device driver support for the vibrator
172 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
173 from input framework.
175 To compile this driver as module, choose M here: the
176 module will be called pm8xxx-vibrator.
178 config INPUT_PMIC8XXX_PWRKEY
179 tristate "PMIC8XXX power key support"
180 depends on MFD_PM8XXX
182 Say Y here if you want support for the PMIC8XXX power key.
186 To compile this driver as a module, choose M here: the
187 module will be called pmic8xxx-pwrkey.
189 config INPUT_SPARCSPKR
190 tristate "SPARC Speaker support"
191 depends on PCI && SPARC64
193 Say Y here if you want the standard Speaker on Sparc PCI systems
194 to be used for bells and whistles.
198 To compile this driver as a module, choose M here: the
199 module will be called sparcspkr.
201 config INPUT_M68K_BEEP
202 tristate "M68k Beeper support"
205 config INPUT_MAX77650_ONKEY
206 tristate "Maxim MAX77650 ONKEY support"
207 depends on MFD_MAX77650
209 Support the ONKEY of the MAX77650 PMIC as an input device.
211 To compile this driver as a module, choose M here: the module
212 will be called max77650-onkey.
214 config INPUT_MAX77693_HAPTIC
215 tristate "MAXIM MAX77693/MAX77843 haptic controller support"
216 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
217 select INPUT_FF_MEMLESS
219 This option enables support for the haptic controller on
220 MAXIM MAX77693 and MAX77843 chips.
222 To compile this driver as module, choose M here: the
223 module will be called max77693-haptic.
225 config INPUT_MAX8925_ONKEY
226 tristate "MAX8925 ONKEY support"
227 depends on MFD_MAX8925
229 Support the ONKEY of MAX8925 PMICs as an input device
230 reporting power button status.
232 To compile this driver as a module, choose M here: the module
233 will be called max8925_onkey.
235 config INPUT_MAX8997_HAPTIC
236 tristate "MAXIM MAX8997 haptic controller support"
237 depends on PWM && MFD_MAX8997
238 select INPUT_FF_MEMLESS
240 This option enables device driver support for the haptic controller
241 on MAXIM MAX8997 chip. This driver supports ff-memless interface
242 from input framework.
244 To compile this driver as module, choose M here: the
245 module will be called max8997-haptic.
247 config INPUT_MC13783_PWRBUTTON
248 tristate "MC13783 ON buttons"
249 depends on MFD_MC13XXX
251 Support the ON buttons of MC13783 PMIC as an input device
252 reporting power button status.
254 To compile this driver as a module, choose M here: the module
255 will be called mc13783-pwrbutton.
258 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
261 Say Y here if you want to support Freescale's MMA8450 Accelerometer
262 through I2C interface.
264 To compile this driver as a module, choose M here: the
265 module will be called mma8450.
268 tristate "Fujitsu Lifebook Application Panel buttons"
269 depends on X86 && I2C && LEDS_CLASS
270 select CHECK_SIGNATURE
272 Say Y here for support of the Application Panel buttons, used on
273 Fujitsu Lifebook. These are attached to the mainboard through
274 an SMBus interface managed by the I2C Intel ICH (i801) driver,
275 which you should also build for this kernel.
277 To compile this driver as a module, choose M here: the module will
280 config INPUT_GPIO_BEEPER
281 tristate "Generic GPIO Beeper support"
282 depends on GPIOLIB || COMPILE_TEST
284 Say Y here if you have a beeper connected to a GPIO pin.
286 To compile this driver as a module, choose M here: the
287 module will be called gpio-beeper.
289 config INPUT_GPIO_DECODER
290 tristate "Polled GPIO Decoder Input driver"
291 depends on GPIOLIB || COMPILE_TEST
293 Say Y here if you want driver to read status of multiple GPIO
294 lines and report the encoded value as an absolute integer to
297 To compile this driver as a module, choose M here: the module
298 will be called gpio_decoder.
300 config INPUT_GPIO_VIBRA
301 tristate "GPIO vibrator support"
302 depends on GPIOLIB || COMPILE_TEST
303 select INPUT_FF_MEMLESS
305 Say Y here to get support for GPIO based vibrator devices.
309 To compile this driver as a module, choose M here: the module will be
312 config INPUT_IXP4XX_BEEPER
313 tristate "IXP4XX Beeper support"
314 depends on ARCH_IXP4XX
316 If you say yes here, you can connect a beeper to the
317 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
321 To compile this driver as a module, choose M here: the
322 module will be called ixp4xx-beeper.
324 config INPUT_COBALT_BTNS
325 tristate "Cobalt button interface"
326 depends on MIPS_COBALT
328 Say Y here if you want to support MIPS Cobalt button interface.
330 To compile this driver as a module, choose M here: the
331 module will be called cobalt_btns.
333 config INPUT_CPCAP_PWRBUTTON
334 tristate "CPCAP OnKey"
337 Say Y here if you want to enable power key reporting via the
340 To compile this driver as a module, choose M here. The module will
341 be called cpcap-pwrbutton.
343 config INPUT_WISTRON_BTNS
344 tristate "x86 Wistron laptop button interface"
346 select INPUT_SPARSEKMAP
349 select CHECK_SIGNATURE
351 Say Y here for support of Wistron laptop button interfaces, used on
352 laptops of various brands, including Acer and Fujitsu-Siemens. If
353 available, mail and wifi LEDs will be controllable via /sys/class/leds.
355 To compile this driver as a module, choose M here: the module will
356 be called wistron_btns.
358 config INPUT_ATLAS_BTNS
359 tristate "x86 Atlas button interface"
360 depends on X86 && ACPI
362 Say Y here for support of Atlas wallmount touchscreen buttons.
363 The events will show up as scancodes F1 through F9 via evdev.
365 To compile this driver as a module, choose M here: the module will
366 be called atlas_btns.
368 config INPUT_ATI_REMOTE2
369 tristate "ATI / Philips USB RF remote control"
370 depends on USB_ARCH_HAS_HCD
373 Say Y here if you want to use an ATI or Philips USB RF remote control.
374 These are RF remotes with USB receivers.
375 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
376 and is also available as a separate product.
377 This driver provides mouse pointer, left and right mouse buttons,
378 and maps all the other remote buttons to keypress events.
380 To compile this driver as a module, choose M here: the module will be
383 config INPUT_KEYSPAN_REMOTE
384 tristate "Keyspan DMR USB remote control"
385 depends on USB_ARCH_HAS_HCD
388 Say Y here if you want to use a Keyspan DMR USB remote control.
389 Currently only the UIA-11 type of receiver has been tested. The tag
390 on the receiver that connects to the USB port should have a P/N that
391 will tell you what type of DMR you have. The UIA-10 type is not
392 supported at this time. This driver maps all buttons to keypress
395 To compile this driver as a module, choose M here: the module will
396 be called keyspan_remote.
399 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
402 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
405 To compile this driver as a module, choose M here: the module will
408 config INPUT_POWERMATE
409 tristate "Griffin PowerMate and Contour Jog support"
410 depends on USB_ARCH_HAS_HCD
413 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
414 These are aluminum dials which can measure clockwise and anticlockwise
415 rotation. The dial also acts as a pushbutton. The base contains an LED
416 which can be instructed to pulse or to switch to a particular intensity.
418 You can download userspace tools from
419 <http://sowerbutts.com/powermate/>.
421 To compile this driver as a module, choose M here: the
422 module will be called powermate.
425 tristate "Yealink usb-p1k voip phone"
426 depends on USB_ARCH_HAS_HCD
429 Say Y here if you want to enable keyboard and LCD functions of the
430 Yealink usb-p1k usb phones. The audio part is enabled by the generic
431 usb sound driver, so you might want to enable that as well.
433 For information about how to use these additional functions, see
434 <file:Documentation/input/devices/yealink.rst>.
436 To compile this driver as a module, choose M here: the module will be
440 tristate "C-Media CM109 USB I/O Controller"
441 depends on USB_ARCH_HAS_HCD
444 Say Y here if you want to enable keyboard and buzzer functions of the
445 C-Media CM109 usb phones. The audio part is enabled by the generic
446 usb sound driver, so you might want to enable that as well.
448 To compile this driver as a module, choose M here: the module will be
451 config INPUT_REGULATOR_HAPTIC
452 tristate "Regulator haptics support"
454 select INPUT_FF_MEMLESS
456 This option enables device driver support for the haptic controlled
457 by a regulator. This driver supports ff-memless interface
458 from input framework.
460 To compile this driver as a module, choose M here: the
461 module will be called regulator-haptic.
463 config INPUT_RETU_PWRBUTTON
464 tristate "Retu Power button Driver"
467 Say Y here if you want to enable power key reporting via the
468 Retu chips found in Nokia Internet Tablets (770, N800, N810).
470 To compile this driver as a module, choose M here. The module will
471 be called retu-pwrbutton.
473 config INPUT_TPS65218_PWRBUTTON
474 tristate "TPS65218 Power button driver"
475 depends on (MFD_TPS65217 || MFD_TPS65218)
477 Say Y here if you want to enable power button reporting for
478 TPS65217 and TPS65218 Power Management IC devices.
480 To compile this driver as a module, choose M here. The module will
481 be called tps65218-pwrbutton.
483 config INPUT_AXP20X_PEK
484 tristate "X-Powers AXP20X power button driver"
485 depends on MFD_AXP20X
487 Say Y here if you want to enable power key reporting via the
490 To compile this driver as a module, choose M here. The module will
491 be called axp20x-pek.
494 config INPUT_TWL4030_PWRBUTTON
495 tristate "TWL4030 Power button Driver"
496 depends on TWL4030_CORE
498 Say Y here if you want to enable power key reporting via the
499 TWL4030 family of chips.
501 To compile this driver as a module, choose M here. The module will
502 be called twl4030_pwrbutton.
504 config INPUT_TWL4030_VIBRA
505 tristate "Support for TWL4030 Vibrator"
506 depends on TWL4030_CORE
507 select MFD_TWL4030_AUDIO
508 select INPUT_FF_MEMLESS
510 This option enables support for TWL4030 Vibrator Driver.
512 To compile this driver as a module, choose M here. The module will
513 be called twl4030_vibra.
515 config INPUT_TWL6040_VIBRA
516 tristate "Support for TWL6040 Vibrator"
517 depends on TWL6040_CORE
518 select INPUT_FF_MEMLESS
520 This option enables support for TWL6040 Vibrator Driver.
522 To compile this driver as a module, choose M here. The module will
523 be called twl6040_vibra.
526 tristate "User level driver support"
528 Say Y here if you want to support user level drivers for input
529 subsystem accessible under char device 10:223 - /dev/input/uinput.
531 To compile this driver as a module, choose M here: the
532 module will be called uinput.
534 config INPUT_SGI_BTNS
535 tristate "SGI Indy/O2 volume button interface"
536 depends on SGI_IP22 || SGI_IP32
538 Say Y here if you want to support SGI Indy/O2 volume button interface.
540 To compile this driver as a module, choose M here: the
541 module will be called sgi_btns.
544 tristate "HP SDC Real Time Clock"
545 depends on (GSC || HP300) && SERIO
548 Say Y here if you want to support the built-in real time clock
549 of the HP SDC controller.
551 config INPUT_PALMAS_PWRBUTTON
552 tristate "Palmas Power button Driver"
553 depends on MFD_PALMAS
555 Say Y here if you want to enable power key reporting via the
556 Palmas family of PMICs.
558 To compile this driver as a module, choose M here. The module will
559 be called palmas_pwrbutton.
561 config INPUT_PCF50633_PMU
562 tristate "PCF50633 PMU events"
563 depends on MFD_PCF50633
565 Say Y to include support for delivering PMU events via input
566 layer on NXP PCF50633.
569 tristate "PCF8574 Keypad input device"
572 Say Y here if you want to support a keypad connected via I2C
575 To compile this driver as a module, choose M here: the
576 module will be called pcf8574_keypad.
578 config INPUT_PWM_BEEPER
579 tristate "PWM beeper support"
582 Say Y here to get support for PWM based beeper devices.
586 To compile this driver as a module, choose M here: the module will be
589 config INPUT_PWM_VIBRA
590 tristate "PWM vibrator support"
592 select INPUT_FF_MEMLESS
594 Say Y here to get support for PWM based vibrator devices.
598 To compile this driver as a module, choose M here: the module will be
601 config INPUT_RK805_PWRKEY
602 tristate "Rockchip RK805 PMIC power key support"
605 Select this option to enable power key driver for RK805.
609 To compile this driver as a module, choose M here: the module will be
612 config INPUT_GPIO_ROTARY_ENCODER
613 tristate "Rotary encoders connected to GPIO pins"
614 depends on GPIOLIB || COMPILE_TEST
616 Say Y here to add support for rotary encoders connected to GPIO lines.
617 Check file:Documentation/input/devices/rotary-encoder.rst for more
620 To compile this driver as a module, choose M here: the
621 module will be called rotary_encoder.
623 config INPUT_RB532_BUTTON
624 tristate "Mikrotik Routerboard 532 button interface"
625 depends on MIKROTIK_RB532
628 Say Y here if you want support for the S1 button built into
629 Mikrotik's Routerboard 532.
631 To compile this driver as a module, choose M here: the
632 module will be called rb532_button.
634 config INPUT_DA7280_HAPTICS
635 tristate "Dialog Semiconductor DA7280 haptics support"
636 depends on INPUT && I2C
639 Say Y to enable support for the Dialog DA7280 haptics driver.
640 The haptics can be controlled by PWM or GPIO
641 with I2C communication.
643 To compile this driver as a module, choose M here: the
644 module will be called da7280.
646 config INPUT_DA9052_ONKEY
647 tristate "Dialog DA9052/DA9053 Onkey"
648 depends on PMIC_DA9052
650 Support the ONKEY of Dialog DA9052 PMICs as an input device
651 reporting power button status.
653 To compile this driver as a module, choose M here: the
654 module will be called da9052_onkey.
656 config INPUT_DA9055_ONKEY
657 tristate "Dialog Semiconductor DA9055 ONKEY"
658 depends on MFD_DA9055
660 Support the ONKEY of DA9055 PMICs as an input device
661 reporting power button status.
663 To compile this driver as a module, choose M here: the module
664 will be called da9055_onkey.
666 config INPUT_DA9063_ONKEY
667 tristate "Dialog DA9063/62/61 OnKey"
668 depends on MFD_DA9063 || MFD_DA9062
670 Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
671 Management ICs as an input device capable of reporting the
674 To compile this driver as a module, choose M here: the module
675 will be called da9063_onkey.
677 config INPUT_DM355EVM
678 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
679 depends on MFD_DM355EVM_MSP
680 select INPUT_SPARSEKMAP
682 Supports the pushbuttons and IR remote used with
685 To compile this driver as a module, choose M here: the
686 module will be called dm355evm_keys.
688 config INPUT_WM831X_ON
689 tristate "WM831X ON pin"
690 depends on MFD_WM831X
692 Support the ON pin of WM831X PMICs as an input device
693 reporting power button status.
695 To compile this driver as a module, choose M here: the module
696 will be called wm831x_on.
699 tristate "Motorola EZX PCAP misc input events"
702 Say Y here if you want to use Power key and Headphone button
703 on Motorola EZX phones.
705 To compile this driver as a module, choose M here: the
706 module will be called pcap_keys.
709 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
712 Say Y here if you have a Accelerometer interface using the
713 ADXL345/6 controller, and your board-specific initialization
714 code includes that in its table of devices.
716 This driver can use either I2C or SPI communication to the
717 ADXL345/6 controller. Select the appropriate method for
720 If unsure, say N (but it's safe to say "Y").
722 To compile this driver as a module, choose M here: the
723 module will be called adxl34x.
725 config INPUT_ADXL34X_I2C
726 tristate "support I2C bus connection"
727 depends on INPUT_ADXL34X && I2C
730 Say Y here if you have ADXL345/6 hooked to an I2C bus.
732 To compile this driver as a module, choose M here: the
733 module will be called adxl34x-i2c.
735 config INPUT_ADXL34X_SPI
736 tristate "support SPI bus connection"
737 depends on INPUT_ADXL34X && SPI
740 Say Y here if you have ADXL345/6 hooked to a SPI bus.
742 To compile this driver as a module, choose M here: the
743 module will be called adxl34x-spi.
746 tristate "IMS Passenger Control Unit driver"
748 depends on LEDS_CLASS
750 Say Y here if you have system with IMS Rave Passenger Control Unit.
752 To compile this driver as a module, choose M here: the module will be
756 tristate "Azoteq IQS269A capacitive touch controller"
760 Say Y to enable support for the Azoteq IQS269A capacitive
763 To compile this driver as a module, choose M here: the
764 module will be called iqs269a.
767 tristate "Azoteq IQS626A capacitive touch controller"
771 Say Y to enable support for the Azoteq IQS626A capacitive
774 To compile this driver as a module, choose M here: the
775 module will be called iqs626a.
778 tristate "VTI CMA3000 Tri-axis accelerometer"
780 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
783 This driver currently only supports I2C interface to the
784 controller. Also select the I2C method.
788 To compile this driver as a module, choose M here: the
789 module will be called cma3000_d0x.
791 config INPUT_CMA3000_I2C
792 tristate "Support I2C bus connection"
793 depends on INPUT_CMA3000 && I2C
795 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
796 through I2C interface.
798 To compile this driver as a module, choose M here: the
799 module will be called cma3000_d0x_i2c.
801 config INPUT_XEN_KBDDEV_FRONTEND
802 tristate "Xen virtual keyboard and mouse support"
805 select XEN_XENBUS_FRONTEND
807 This driver implements the front-end of the Xen virtual
808 keyboard and mouse device driver. It communicates with a back-end
811 To compile this driver as a module, choose M here: the
812 module will be called xen-kbdfront.
814 config INPUT_SIRFSOC_ONKEY
815 tristate "CSR SiRFSoC power on/off/suspend key support"
816 depends on ARCH_SIRF && OF
819 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
820 in Linux, after you press the onkey, system will suspend.
824 config INPUT_IDEAPAD_SLIDEBAR
825 tristate "IdeaPad Laptop Slidebar"
827 depends on SERIO_I8042
829 Say Y here if you have an IdeaPad laptop with a slidebar.
831 To compile this driver as a module, choose M here: the
832 module will be called ideapad_slidebar.
834 config INPUT_SOC_BUTTON_ARRAY
835 tristate "Windows-compatible SoC Button Array"
836 depends on KEYBOARD_GPIO && ACPI
838 Say Y here if you have a SoC-based tablet that originally runs
839 Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later.
841 To compile this driver as a module, choose M here: the
842 module will be called soc_button_array.
844 config INPUT_DRV260X_HAPTICS
845 tristate "TI DRV260X haptics support"
846 depends on INPUT && I2C
847 depends on GPIOLIB || COMPILE_TEST
848 select INPUT_FF_MEMLESS
851 Say Y to enable support for the TI DRV260X haptics driver.
853 To compile this driver as a module, choose M here: the
854 module will be called drv260x-haptics.
856 config INPUT_DRV2665_HAPTICS
857 tristate "TI DRV2665 haptics support"
858 depends on INPUT && I2C
859 select INPUT_FF_MEMLESS
862 Say Y to enable support for the TI DRV2665 haptics driver.
864 To compile this driver as a module, choose M here: the
865 module will be called drv2665-haptics.
867 config INPUT_DRV2667_HAPTICS
868 tristate "TI DRV2667 haptics support"
869 depends on INPUT && I2C
870 select INPUT_FF_MEMLESS
873 Say Y to enable support for the TI DRV2667 haptics driver.
875 To compile this driver as a module, choose M here: the
876 module will be called drv2667-haptics.
878 config INPUT_HISI_POWERKEY
879 tristate "Hisilicon PMIC ONKEY support"
880 depends on ARCH_HISI || COMPILE_TEST
882 Say Y to enable support for PMIC ONKEY.
884 To compile this driver as a module, choose M here: the
885 module will be called hisi_powerkey.
887 config INPUT_RAVE_SP_PWRBUTTON
888 tristate "RAVE SP Power button Driver"
889 depends on RAVE_SP_CORE
891 Say Y here if you want to enable power key reporting from RAVE SP
893 To compile this driver as a module, choose M here: the
894 module will be called rave-sp-pwrbutton.
896 config INPUT_SC27XX_VIBRA
897 tristate "Spreadtrum sc27xx vibrator support"
898 depends on MFD_SC27XX_PMIC || COMPILE_TEST
899 select INPUT_FF_MEMLESS
901 This option enables support for Spreadtrum sc27xx vibrator driver.
903 To compile this driver as a module, choose M here. The module will
904 be called sc27xx_vibra.
906 config INPUT_STPMIC1_ONKEY
907 tristate "STPMIC1 PMIC Onkey support"
908 depends on MFD_STPMIC1
910 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
911 can be used to wakeup from low power modes and force a shut-down on
914 To compile this driver as a module, choose M here: the
915 module will be called stpmic1_onkey.