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_COBALT_BTNS
313 tristate "Cobalt button interface"
314 depends on MIPS_COBALT
316 Say Y here if you want to support MIPS Cobalt button interface.
318 To compile this driver as a module, choose M here: the
319 module will be called cobalt_btns.
321 config INPUT_CPCAP_PWRBUTTON
322 tristate "CPCAP OnKey"
325 Say Y here if you want to enable power key reporting via the
328 To compile this driver as a module, choose M here. The module will
329 be called cpcap-pwrbutton.
331 config INPUT_WISTRON_BTNS
332 tristate "x86 Wistron laptop button interface"
334 select INPUT_SPARSEKMAP
337 select CHECK_SIGNATURE
339 Say Y here for support of Wistron laptop button interfaces, used on
340 laptops of various brands, including Acer and Fujitsu-Siemens. If
341 available, mail and wifi LEDs will be controllable via /sys/class/leds.
343 To compile this driver as a module, choose M here: the module will
344 be called wistron_btns.
346 config INPUT_ATLAS_BTNS
347 tristate "x86 Atlas button interface"
348 depends on X86 && ACPI
350 Say Y here for support of Atlas wallmount touchscreen buttons.
351 The events will show up as scancodes F1 through F9 via evdev.
353 To compile this driver as a module, choose M here: the module will
354 be called atlas_btns.
356 config INPUT_ATI_REMOTE2
357 tristate "ATI / Philips USB RF remote control"
358 depends on USB_ARCH_HAS_HCD
361 Say Y here if you want to use an ATI or Philips USB RF remote control.
362 These are RF remotes with USB receivers.
363 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
364 and is also available as a separate product.
365 This driver provides mouse pointer, left and right mouse buttons,
366 and maps all the other remote buttons to keypress events.
368 To compile this driver as a module, choose M here: the module will be
371 config INPUT_KEYSPAN_REMOTE
372 tristate "Keyspan DMR USB remote control"
373 depends on USB_ARCH_HAS_HCD
376 Say Y here if you want to use a Keyspan DMR USB remote control.
377 Currently only the UIA-11 type of receiver has been tested. The tag
378 on the receiver that connects to the USB port should have a P/N that
379 will tell you what type of DMR you have. The UIA-10 type is not
380 supported at this time. This driver maps all buttons to keypress
383 To compile this driver as a module, choose M here: the module will
384 be called keyspan_remote.
387 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
390 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
393 To compile this driver as a module, choose M here: the module will
396 config INPUT_POWERMATE
397 tristate "Griffin PowerMate and Contour Jog support"
398 depends on USB_ARCH_HAS_HCD
401 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
402 These are aluminum dials which can measure clockwise and anticlockwise
403 rotation. The dial also acts as a pushbutton. The base contains an LED
404 which can be instructed to pulse or to switch to a particular intensity.
406 You can download userspace tools from
407 <http://sowerbutts.com/powermate/>.
409 To compile this driver as a module, choose M here: the
410 module will be called powermate.
413 tristate "Yealink usb-p1k voip phone"
414 depends on USB_ARCH_HAS_HCD
417 Say Y here if you want to enable keyboard and LCD functions of the
418 Yealink usb-p1k usb phones. The audio part is enabled by the generic
419 usb sound driver, so you might want to enable that as well.
421 For information about how to use these additional functions, see
422 <file:Documentation/input/devices/yealink.rst>.
424 To compile this driver as a module, choose M here: the module will be
428 tristate "C-Media CM109 USB I/O Controller"
429 depends on USB_ARCH_HAS_HCD
432 Say Y here if you want to enable keyboard and buzzer functions of the
433 C-Media CM109 usb phones. The audio part is enabled by the generic
434 usb sound driver, so you might want to enable that as well.
436 To compile this driver as a module, choose M here: the module will be
439 config INPUT_REGULATOR_HAPTIC
440 tristate "Regulator haptics support"
442 select INPUT_FF_MEMLESS
444 This option enables device driver support for the haptic controlled
445 by a regulator. This driver supports ff-memless interface
446 from input framework.
448 To compile this driver as a module, choose M here: the
449 module will be called regulator-haptic.
451 config INPUT_RETU_PWRBUTTON
452 tristate "Retu Power button Driver"
455 Say Y here if you want to enable power key reporting via the
456 Retu chips found in Nokia Internet Tablets (770, N800, N810).
458 To compile this driver as a module, choose M here. The module will
459 be called retu-pwrbutton.
461 config INPUT_TPS65218_PWRBUTTON
462 tristate "TPS65218 Power button driver"
463 depends on (MFD_TPS65217 || MFD_TPS65218)
465 Say Y here if you want to enable power button reporting for
466 TPS65217 and TPS65218 Power Management IC devices.
468 To compile this driver as a module, choose M here. The module will
469 be called tps65218-pwrbutton.
471 config INPUT_AXP20X_PEK
472 tristate "X-Powers AXP20X power button driver"
473 depends on MFD_AXP20X
475 Say Y here if you want to enable power key reporting via the
478 To compile this driver as a module, choose M here. The module will
479 be called axp20x-pek.
482 config INPUT_TWL4030_PWRBUTTON
483 tristate "TWL4030 Power button Driver"
484 depends on TWL4030_CORE
486 Say Y here if you want to enable power key reporting via the
487 TWL4030 family of chips.
489 To compile this driver as a module, choose M here. The module will
490 be called twl4030_pwrbutton.
492 config INPUT_TWL4030_VIBRA
493 tristate "Support for TWL4030 Vibrator"
494 depends on TWL4030_CORE
495 select MFD_TWL4030_AUDIO
496 select INPUT_FF_MEMLESS
498 This option enables support for TWL4030 Vibrator Driver.
500 To compile this driver as a module, choose M here. The module will
501 be called twl4030_vibra.
503 config INPUT_TWL6040_VIBRA
504 tristate "Support for TWL6040 Vibrator"
505 depends on TWL6040_CORE
506 select INPUT_FF_MEMLESS
508 This option enables support for TWL6040 Vibrator Driver.
510 To compile this driver as a module, choose M here. The module will
511 be called twl6040_vibra.
514 tristate "User level driver support"
516 Say Y here if you want to support user level drivers for input
517 subsystem accessible under char device 10:223 - /dev/input/uinput.
519 To compile this driver as a module, choose M here: the
520 module will be called uinput.
522 config INPUT_SGI_BTNS
523 tristate "SGI Indy/O2 volume button interface"
524 depends on SGI_IP22 || SGI_IP32
526 Say Y here if you want to support SGI Indy/O2 volume button interface.
528 To compile this driver as a module, choose M here: the
529 module will be called sgi_btns.
532 tristate "HP SDC Real Time Clock"
533 depends on (GSC || HP300) && SERIO
536 Say Y here if you want to support the built-in real time clock
537 of the HP SDC controller.
539 config INPUT_PALMAS_PWRBUTTON
540 tristate "Palmas Power button Driver"
541 depends on MFD_PALMAS
543 Say Y here if you want to enable power key reporting via the
544 Palmas family of PMICs.
546 To compile this driver as a module, choose M here. The module will
547 be called palmas_pwrbutton.
549 config INPUT_PCF50633_PMU
550 tristate "PCF50633 PMU events"
551 depends on MFD_PCF50633
553 Say Y to include support for delivering PMU events via input
554 layer on NXP PCF50633.
557 tristate "PCF8574 Keypad input device"
560 Say Y here if you want to support a keypad connected via I2C
563 To compile this driver as a module, choose M here: the
564 module will be called pcf8574_keypad.
566 config INPUT_PWM_BEEPER
567 tristate "PWM beeper support"
570 Say Y here to get support for PWM based beeper devices.
574 To compile this driver as a module, choose M here: the module will be
577 config INPUT_PWM_VIBRA
578 tristate "PWM vibrator support"
580 select INPUT_FF_MEMLESS
582 Say Y here to get support for PWM based vibrator devices.
586 To compile this driver as a module, choose M here: the module will be
589 config INPUT_RK805_PWRKEY
590 tristate "Rockchip RK805 PMIC power key support"
593 Select this option to enable power key driver for RK805.
597 To compile this driver as a module, choose M here: the module will be
600 config INPUT_GPIO_ROTARY_ENCODER
601 tristate "Rotary encoders connected to GPIO pins"
602 depends on GPIOLIB || COMPILE_TEST
604 Say Y here to add support for rotary encoders connected to GPIO lines.
605 Check file:Documentation/input/devices/rotary-encoder.rst for more
608 To compile this driver as a module, choose M here: the
609 module will be called rotary_encoder.
611 config INPUT_RB532_BUTTON
612 tristate "Mikrotik Routerboard 532 button interface"
613 depends on MIKROTIK_RB532
616 Say Y here if you want support for the S1 button built into
617 Mikrotik's Routerboard 532.
619 To compile this driver as a module, choose M here: the
620 module will be called rb532_button.
622 config INPUT_DA7280_HAPTICS
623 tristate "Dialog Semiconductor DA7280 haptics support"
624 depends on INPUT && I2C
627 Say Y to enable support for the Dialog DA7280 haptics driver.
628 The haptics can be controlled by PWM or GPIO
629 with I2C communication.
631 To compile this driver as a module, choose M here: the
632 module will be called da7280.
634 config INPUT_DA9052_ONKEY
635 tristate "Dialog DA9052/DA9053 Onkey"
636 depends on PMIC_DA9052
638 Support the ONKEY of Dialog DA9052 PMICs as an input device
639 reporting power button status.
641 To compile this driver as a module, choose M here: the
642 module will be called da9052_onkey.
644 config INPUT_DA9055_ONKEY
645 tristate "Dialog Semiconductor DA9055 ONKEY"
646 depends on MFD_DA9055
648 Support the ONKEY of DA9055 PMICs as an input device
649 reporting power button status.
651 To compile this driver as a module, choose M here: the module
652 will be called da9055_onkey.
654 config INPUT_DA9063_ONKEY
655 tristate "Dialog DA9063/62/61 OnKey"
656 depends on MFD_DA9063 || MFD_DA9062
658 Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
659 Management ICs as an input device capable of reporting the
662 To compile this driver as a module, choose M here: the module
663 will be called da9063_onkey.
665 config INPUT_DM355EVM
666 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
667 depends on MFD_DM355EVM_MSP
668 select INPUT_SPARSEKMAP
670 Supports the pushbuttons and IR remote used with
673 To compile this driver as a module, choose M here: the
674 module will be called dm355evm_keys.
676 config INPUT_WM831X_ON
677 tristate "WM831X ON pin"
678 depends on MFD_WM831X
680 Support the ON pin of WM831X PMICs as an input device
681 reporting power button status.
683 To compile this driver as a module, choose M here: the module
684 will be called wm831x_on.
687 tristate "Motorola EZX PCAP misc input events"
690 Say Y here if you want to use Power key and Headphone button
691 on Motorola EZX phones.
693 To compile this driver as a module, choose M here: the
694 module will be called pcap_keys.
697 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
700 Say Y here if you have a Accelerometer interface using the
701 ADXL345/6 controller, and your board-specific initialization
702 code includes that in its table of devices.
704 This driver can use either I2C or SPI communication to the
705 ADXL345/6 controller. Select the appropriate method for
708 If unsure, say N (but it's safe to say "Y").
710 To compile this driver as a module, choose M here: the
711 module will be called adxl34x.
713 config INPUT_ADXL34X_I2C
714 tristate "support I2C bus connection"
715 depends on INPUT_ADXL34X && I2C
718 Say Y here if you have ADXL345/6 hooked to an I2C bus.
720 To compile this driver as a module, choose M here: the
721 module will be called adxl34x-i2c.
723 config INPUT_ADXL34X_SPI
724 tristate "support SPI bus connection"
725 depends on INPUT_ADXL34X && SPI
728 Say Y here if you have ADXL345/6 hooked to a SPI bus.
730 To compile this driver as a module, choose M here: the
731 module will be called adxl34x-spi.
734 tristate "IMS Passenger Control Unit driver"
736 depends on LEDS_CLASS
738 Say Y here if you have system with IMS Rave Passenger Control Unit.
740 To compile this driver as a module, choose M here: the module will be
744 tristate "Azoteq IQS269A capacitive touch controller"
748 Say Y to enable support for the Azoteq IQS269A capacitive
751 To compile this driver as a module, choose M here: the
752 module will be called iqs269a.
755 tristate "Azoteq IQS626A capacitive touch controller"
759 Say Y to enable support for the Azoteq IQS626A capacitive
762 To compile this driver as a module, choose M here: the
763 module will be called iqs626a.
766 tristate "Azoteq IQS7222A/B/C capacitive touch controller"
769 Say Y to enable support for the Azoteq IQS7222A/B/C family
770 of capacitive touch controllers.
772 To compile this driver as a module, choose M here: the
773 module will be called iqs7222.
776 tristate "VTI CMA3000 Tri-axis accelerometer"
778 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
781 This driver currently only supports I2C interface to the
782 controller. Also select the I2C method.
786 To compile this driver as a module, choose M here: the
787 module will be called cma3000_d0x.
789 config INPUT_CMA3000_I2C
790 tristate "Support I2C bus connection"
791 depends on INPUT_CMA3000 && I2C
793 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
794 through I2C interface.
796 To compile this driver as a module, choose M here: the
797 module will be called cma3000_d0x_i2c.
799 config INPUT_XEN_KBDDEV_FRONTEND
800 tristate "Xen virtual keyboard and mouse support"
803 select XEN_XENBUS_FRONTEND
805 This driver implements the front-end of the Xen virtual
806 keyboard and mouse device driver. It communicates with a back-end
809 To compile this driver as a module, choose M here: the
810 module will be called xen-kbdfront.
812 config INPUT_IDEAPAD_SLIDEBAR
813 tristate "IdeaPad Laptop Slidebar"
815 depends on SERIO_I8042
817 Say Y here if you have an IdeaPad laptop with a slidebar.
819 To compile this driver as a module, choose M here: the
820 module will be called ideapad_slidebar.
822 config INPUT_SOC_BUTTON_ARRAY
823 tristate "Windows-compatible SoC Button Array"
824 depends on KEYBOARD_GPIO && ACPI
826 Say Y here if you have a SoC-based tablet that originally runs
827 Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later.
829 To compile this driver as a module, choose M here: the
830 module will be called soc_button_array.
832 config INPUT_DRV260X_HAPTICS
833 tristate "TI DRV260X haptics support"
834 depends on INPUT && I2C
835 depends on GPIOLIB || COMPILE_TEST
836 select INPUT_FF_MEMLESS
839 Say Y to enable support for the TI DRV260X haptics driver.
841 To compile this driver as a module, choose M here: the
842 module will be called drv260x-haptics.
844 config INPUT_DRV2665_HAPTICS
845 tristate "TI DRV2665 haptics support"
846 depends on INPUT && I2C
847 select INPUT_FF_MEMLESS
850 Say Y to enable support for the TI DRV2665 haptics driver.
852 To compile this driver as a module, choose M here: the
853 module will be called drv2665-haptics.
855 config INPUT_DRV2667_HAPTICS
856 tristate "TI DRV2667 haptics support"
857 depends on INPUT && I2C
858 select INPUT_FF_MEMLESS
861 Say Y to enable support for the TI DRV2667 haptics driver.
863 To compile this driver as a module, choose M here: the
864 module will be called drv2667-haptics.
866 config INPUT_HISI_POWERKEY
867 tristate "Hisilicon PMIC ONKEY support"
868 depends on ARCH_HISI || COMPILE_TEST
870 Say Y to enable support for PMIC ONKEY.
872 To compile this driver as a module, choose M here: the
873 module will be called hisi_powerkey.
875 config INPUT_RAVE_SP_PWRBUTTON
876 tristate "RAVE SP Power button Driver"
877 depends on RAVE_SP_CORE
879 Say Y here if you want to enable power key reporting from RAVE SP
881 To compile this driver as a module, choose M here: the
882 module will be called rave-sp-pwrbutton.
884 config INPUT_SC27XX_VIBRA
885 tristate "Spreadtrum sc27xx vibrator support"
886 depends on MFD_SC27XX_PMIC || COMPILE_TEST
887 select INPUT_FF_MEMLESS
889 This option enables support for Spreadtrum sc27xx vibrator driver.
891 To compile this driver as a module, choose M here. The module will
892 be called sc27xx_vibra.
894 config INPUT_STPMIC1_ONKEY
895 tristate "STPMIC1 PMIC Onkey support"
896 depends on MFD_STPMIC1
898 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
899 can be used to wakeup from low power modes and force a shut-down on
902 To compile this driver as a module, choose M here: the
903 module will be called stpmic1_onkey.