2 # Input misc drivers configuration
5 bool "Miscellaneous devices"
7 Say Y here, and a list of miscellaneous input drivers will be displayed.
8 Everything that didn't fit into the other categories is here. This option
9 doesn't affect the kernel.
15 config INPUT_88PM860X_ONKEY
16 tristate "88PM860x ONKEY support"
17 depends on MFD_88PM860X
19 Support the ONKEY of Marvell 88PM860x PMICs as an input device
20 reporting power button status.
22 To compile this driver as a module, choose M here: the module
23 will be called 88pm860x_onkey.
25 config INPUT_88PM80X_ONKEY
26 tristate "88PM80x ONKEY support"
27 depends on MFD_88PM800
29 Support the ONKEY of Marvell 88PM80x PMICs as an input device
30 reporting power button status.
32 To compile this driver as a module, choose M here: the module
33 will be called 88pm80x_onkey.
35 config INPUT_AB8500_PONKEY
36 tristate "AB8500 Pon (PowerOn) Key"
37 depends on AB8500_CORE
39 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
42 To compile this driver as a module, choose M here: the module
43 will be called ab8500-ponkey.
46 tristate "Analog Devices AD714x Capacitance Touch Sensor"
48 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
50 You should select a bus connection too.
52 To compile this driver as a module, choose M here: the
53 module will be called ad714x.
55 config INPUT_AD714X_I2C
56 tristate "support I2C bus connection"
57 depends on INPUT_AD714X && I2C
60 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
62 To compile this driver as a module, choose M here: the
63 module will be called ad714x-i2c.
65 config INPUT_AD714X_SPI
66 tristate "support SPI bus connection"
67 depends on INPUT_AD714X && SPI
70 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
72 To compile this driver as a module, choose M here: the
73 module will be called ad714x-spi.
75 config INPUT_ARIZONA_HAPTICS
76 tristate "Arizona haptics support"
77 depends on MFD_ARIZONA && SND_SOC
78 select INPUT_FF_MEMLESS
80 Say Y to enable support for the haptics module in Arizona CODECs.
82 To compile this driver as a module, choose M here: the
83 module will be called arizona-haptics.
85 config INPUT_ATMEL_CAPTOUCH
86 tristate "Atmel Capacitive Touch Button Driver"
87 depends on OF || COMPILE_TEST
90 Say Y here if an Atmel Capacitive Touch Button device which
91 implements "captouch" protocol is connected to I2C bus. Typically
92 this device consists of Atmel Touch sensor controlled by AtMegaXX
93 MCU running firmware based on Qtouch library.
94 One should find "atmel,captouch" node in the board specific DTS.
96 To compile this driver as a module, choose M here: the
97 module will be called atmel_captouch.
100 tristate "BMA150/SMB380 acceleration sensor support"
104 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
105 acceleration sensor hooked to an I2C bus.
107 To compile this driver as a module, choose M here: the
108 module will be called bma150.
110 config INPUT_E3X0_BUTTON
111 tristate "NI Ettus Research USRP E3xx Button support."
114 Say Y here to enable support for the NI Ettus Research
117 To compile this driver as a module, choose M here: the
118 module will be called e3x0_button.
120 config INPUT_MSM_VIBRATOR
121 tristate "Qualcomm MSM vibrator driver"
122 select INPUT_FF_MEMLESS
124 Support for the vibrator that is found on various Qualcomm MSM
127 To compile this driver as a module, choose M here: the module
128 will be called msm_vibrator.
131 tristate "PC Speaker support"
132 depends on PCSPKR_PLATFORM
134 Say Y here if you want the standard PC Speaker to be used for
139 To compile this driver as a module, choose M here: the
140 module will be called pcspkr.
142 config INPUT_PM8941_PWRKEY
143 tristate "Qualcomm PM8941 power key support"
144 depends on MFD_SPMI_PMIC
146 Say Y here if you want support for the power key usually found
147 on boards using a Qualcomm PM8941 compatible PMIC.
151 To compile this driver as a module, choose M here: the module
152 will be called pm8941-pwrkey.
154 config INPUT_PM8XXX_VIBRATOR
155 tristate "Qualcomm PM8XXX vibrator support"
156 depends on MFD_PM8XXX || MFD_SPMI_PMIC
157 select INPUT_FF_MEMLESS
159 This option enables device driver support for the vibrator
160 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
161 from input framework.
163 To compile this driver as module, choose M here: the
164 module will be called pm8xxx-vibrator.
166 config INPUT_PMIC8XXX_PWRKEY
167 tristate "PMIC8XXX power key support"
168 depends on MFD_PM8XXX
170 Say Y here if you want support for the PMIC8XXX power key.
174 To compile this driver as a module, choose M here: the
175 module will be called pmic8xxx-pwrkey.
177 config INPUT_SPARCSPKR
178 tristate "SPARC Speaker support"
179 depends on PCI && SPARC64
181 Say Y here if you want the standard Speaker on Sparc PCI systems
182 to be used for bells and whistles.
186 To compile this driver as a module, choose M here: the
187 module will be called sparcspkr.
189 config INPUT_M68K_BEEP
190 tristate "M68k Beeper support"
193 config INPUT_MAX77693_HAPTIC
194 tristate "MAXIM MAX77693/MAX77843 haptic controller support"
195 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
196 select INPUT_FF_MEMLESS
198 This option enables support for the haptic controller on
199 MAXIM MAX77693 and MAX77843 chips.
201 To compile this driver as module, choose M here: the
202 module will be called max77693-haptic.
204 config INPUT_MAX8925_ONKEY
205 tristate "MAX8925 ONKEY support"
206 depends on MFD_MAX8925
208 Support the ONKEY of MAX8925 PMICs as an input device
209 reporting power button status.
211 To compile this driver as a module, choose M here: the module
212 will be called max8925_onkey.
214 config INPUT_MAX8997_HAPTIC
215 tristate "MAXIM MAX8997 haptic controller support"
216 depends on PWM && MFD_MAX8997
217 select INPUT_FF_MEMLESS
219 This option enables device driver support for the haptic controller
220 on MAXIM MAX8997 chip. This driver supports ff-memless interface
221 from input framework.
223 To compile this driver as module, choose M here: the
224 module will be called max8997-haptic.
226 config INPUT_MC13783_PWRBUTTON
227 tristate "MC13783 ON buttons"
228 depends on MFD_MC13XXX
230 Support the ON buttons of MC13783 PMIC as an input device
231 reporting power button status.
233 To compile this driver as a module, choose M here: the module
234 will be called mc13783-pwrbutton.
237 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
241 Say Y here if you want to support Freescale's MMA8450 Accelerometer
242 through I2C interface.
244 To compile this driver as a module, choose M here: the
245 module will be called mma8450.
248 tristate "Fujitsu Lifebook Application Panel buttons"
249 depends on X86 && I2C && LEDS_CLASS
251 select CHECK_SIGNATURE
253 Say Y here for support of the Application Panel buttons, used on
254 Fujitsu Lifebook. These are attached to the mainboard through
255 an SMBus interface managed by the I2C Intel ICH (i801) driver,
256 which you should also build for this kernel.
258 To compile this driver as a module, choose M here: the module will
262 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
264 depends on GPIOLIB || COMPILE_TEST
266 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
267 hooked to an I2C bus.
269 To compile this driver as a module, choose M here: the
270 module will be called gp2ap002a00f.
272 config INPUT_GPIO_BEEPER
273 tristate "Generic GPIO Beeper support"
274 depends on GPIOLIB || COMPILE_TEST
276 Say Y here if you have a beeper connected to a GPIO pin.
278 To compile this driver as a module, choose M here: the
279 module will be called gpio-beeper.
281 config INPUT_GPIO_DECODER
282 tristate "Polled GPIO Decoder Input driver"
283 depends on GPIOLIB || COMPILE_TEST
286 Say Y here if you want driver to read status of multiple GPIO
287 lines and report the encoded value as an absolute integer to
290 To compile this driver as a module, choose M here: the module
291 will be called gpio_decoder.
293 config INPUT_GPIO_VIBRA
294 tristate "GPIO vibrator support"
295 depends on GPIOLIB || COMPILE_TEST
296 select INPUT_FF_MEMLESS
298 Say Y here to get support for GPIO based vibrator devices.
302 To compile this driver as a module, choose M here: the module will be
305 config INPUT_IXP4XX_BEEPER
306 tristate "IXP4XX Beeper support"
307 depends on ARCH_IXP4XX
309 If you say yes here, you can connect a beeper to the
310 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
314 To compile this driver as a module, choose M here: the
315 module will be called ixp4xx-beeper.
317 config INPUT_COBALT_BTNS
318 tristate "Cobalt button interface"
319 depends on MIPS_COBALT
322 Say Y here if you want to support MIPS Cobalt button interface.
324 To compile this driver as a module, choose M here: the
325 module will be called cobalt_btns.
327 config INPUT_CPCAP_PWRBUTTON
328 tristate "CPCAP OnKey"
331 Say Y here if you want to enable power key reporting via the
334 To compile this driver as a module, choose M here. The module will
335 be called cpcap-pwrbutton.
337 config INPUT_WISTRON_BTNS
338 tristate "x86 Wistron laptop button interface"
341 select INPUT_SPARSEKMAP
344 select CHECK_SIGNATURE
346 Say Y here for support of Wistron laptop button interfaces, used on
347 laptops of various brands, including Acer and Fujitsu-Siemens. If
348 available, mail and wifi LEDs will be controllable via /sys/class/leds.
350 To compile this driver as a module, choose M here: the module will
351 be called wistron_btns.
353 config INPUT_ATLAS_BTNS
354 tristate "x86 Atlas button interface"
355 depends on X86 && ACPI
357 Say Y here for support of Atlas wallmount touchscreen buttons.
358 The events will show up as scancodes F1 through F9 via evdev.
360 To compile this driver as a module, choose M here: the module will
361 be called atlas_btns.
363 config INPUT_ATI_REMOTE2
364 tristate "ATI / Philips USB RF remote control"
365 depends on USB_ARCH_HAS_HCD
368 Say Y here if you want to use an ATI or Philips USB RF remote control.
369 These are RF remotes with USB receivers.
370 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
371 and is also available as a separate product.
372 This driver provides mouse pointer, left and right mouse buttons,
373 and maps all the other remote buttons to keypress events.
375 To compile this driver as a module, choose M here: the module will be
378 config INPUT_KEYSPAN_REMOTE
379 tristate "Keyspan DMR USB remote control"
380 depends on USB_ARCH_HAS_HCD
383 Say Y here if you want to use a Keyspan DMR USB remote control.
384 Currently only the UIA-11 type of receiver has been tested. The tag
385 on the receiver that connects to the USB port should have a P/N that
386 will tell you what type of DMR you have. The UIA-10 type is not
387 supported at this time. This driver maps all buttons to keypress
390 To compile this driver as a module, choose M here: the module will
391 be called keyspan_remote.
394 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
397 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
400 To compile this driver as a module, choose M here: the module will
403 config INPUT_KXTJ9_POLLED_MODE
404 bool "Enable polling mode support"
405 depends on INPUT_KXTJ9
408 Say Y here if you need accelerometer to work in polling mode.
410 config INPUT_POWERMATE
411 tristate "Griffin PowerMate and Contour Jog support"
412 depends on USB_ARCH_HAS_HCD
415 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
416 These are aluminum dials which can measure clockwise and anticlockwise
417 rotation. The dial also acts as a pushbutton. The base contains an LED
418 which can be instructed to pulse or to switch to a particular intensity.
420 You can download userspace tools from
421 <http://sowerbutts.com/powermate/>.
423 To compile this driver as a module, choose M here: the
424 module will be called powermate.
427 tristate "Yealink usb-p1k voip phone"
428 depends on USB_ARCH_HAS_HCD
431 Say Y here if you want to enable keyboard and LCD functions of the
432 Yealink usb-p1k usb phones. The audio part is enabled by the generic
433 usb sound driver, so you might want to enable that as well.
435 For information about how to use these additional functions, see
436 <file:Documentation/input/devices/yealink.rst>.
438 To compile this driver as a module, choose M here: the module will be
442 tristate "C-Media CM109 USB I/O Controller"
443 depends on USB_ARCH_HAS_HCD
446 Say Y here if you want to enable keyboard and buzzer functions of the
447 C-Media CM109 usb phones. The audio part is enabled by the generic
448 usb sound driver, so you might want to enable that as well.
450 To compile this driver as a module, choose M here: the module will be
453 config INPUT_REGULATOR_HAPTIC
454 tristate "Regulator haptics support"
456 select INPUT_FF_MEMLESS
458 This option enables device driver support for the haptic controlled
459 by a regulator. This driver supports ff-memless interface
460 from input framework.
462 To compile this driver as a module, choose M here: the
463 module will be called regulator-haptic.
465 config INPUT_RETU_PWRBUTTON
466 tristate "Retu Power button Driver"
469 Say Y here if you want to enable power key reporting via the
470 Retu chips found in Nokia Internet Tablets (770, N800, N810).
472 To compile this driver as a module, choose M here. The module will
473 be called retu-pwrbutton.
475 config INPUT_TPS65218_PWRBUTTON
476 tristate "TPS65218 Power button driver"
477 depends on (MFD_TPS65217 || MFD_TPS65218)
479 Say Y here if you want to enable power button reporting for
480 TPS65217 and TPS65218 Power Management IC devices.
482 To compile this driver as a module, choose M here. The module will
483 be called tps65218-pwrbutton.
485 config INPUT_AXP20X_PEK
486 tristate "X-Powers AXP20X power button driver"
487 depends on MFD_AXP20X
489 Say Y here if you want to enable power key reporting via the
492 To compile this driver as a module, choose M here. The module will
493 be called axp20x-pek.
496 config INPUT_TWL4030_PWRBUTTON
497 tristate "TWL4030 Power button Driver"
498 depends on TWL4030_CORE
500 Say Y here if you want to enable power key reporting via the
501 TWL4030 family of chips.
503 To compile this driver as a module, choose M here. The module will
504 be called twl4030_pwrbutton.
506 config INPUT_TWL4030_VIBRA
507 tristate "Support for TWL4030 Vibrator"
508 depends on TWL4030_CORE
509 select MFD_TWL4030_AUDIO
510 select INPUT_FF_MEMLESS
512 This option enables support for TWL4030 Vibrator Driver.
514 To compile this driver as a module, choose M here. The module will
515 be called twl4030_vibra.
517 config INPUT_TWL6040_VIBRA
518 tristate "Support for TWL6040 Vibrator"
519 depends on TWL6040_CORE
520 select INPUT_FF_MEMLESS
522 This option enables support for TWL6040 Vibrator Driver.
524 To compile this driver as a module, choose M here. The module will
525 be called twl6040_vibra.
528 tristate "User level driver support"
530 Say Y here if you want to support user level drivers for input
531 subsystem accessible under char device 10:223 - /dev/input/uinput.
533 To compile this driver as a module, choose M here: the
534 module will be called uinput.
536 config INPUT_SGI_BTNS
537 tristate "SGI Indy/O2 volume button interface"
538 depends on SGI_IP22 || SGI_IP32
541 Say Y here if you want to support SGI Indy/O2 volume button interface.
543 To compile this driver as a module, choose M here: the
544 module will be called sgi_btns.
547 tristate "HP SDC Real Time Clock"
548 depends on (GSC || HP300) && SERIO
551 Say Y here if you want to support the built-in real time clock
552 of the HP SDC controller.
554 config INPUT_PALMAS_PWRBUTTON
555 tristate "Palmas Power button Driver"
556 depends on MFD_PALMAS
558 Say Y here if you want to enable power key reporting via the
559 Palmas family of PMICs.
561 To compile this driver as a module, choose M here. The module will
562 be called palmas_pwrbutton.
564 config INPUT_PCF50633_PMU
565 tristate "PCF50633 PMU events"
566 depends on MFD_PCF50633
568 Say Y to include support for delivering PMU events via input
569 layer on NXP PCF50633.
572 tristate "PCF8574 Keypad input device"
575 Say Y here if you want to support a keypad connected via I2C
578 To compile this driver as a module, choose M here: the
579 module will be called pcf8574_keypad.
581 config INPUT_PWM_BEEPER
582 tristate "PWM beeper support"
585 Say Y here to get support for PWM based beeper devices.
589 To compile this driver as a module, choose M here: the module will be
592 config INPUT_PWM_VIBRA
593 tristate "PWM vibrator support"
595 select INPUT_FF_MEMLESS
597 Say Y here to get support for PWM based vibrator devices.
601 To compile this driver as a module, choose M here: the module will be
604 config INPUT_RK805_PWRKEY
605 tristate "Rockchip RK805 PMIC power key support"
608 Select this option to enable power key driver for RK805.
612 To compile this driver as a module, choose M here: the module will be
615 config INPUT_GPIO_ROTARY_ENCODER
616 tristate "Rotary encoders connected to GPIO pins"
617 depends on GPIOLIB || COMPILE_TEST
619 Say Y here to add support for rotary encoders connected to GPIO lines.
620 Check file:Documentation/input/devices/rotary-encoder.rst for more
623 To compile this driver as a module, choose M here: the
624 module will be called rotary_encoder.
626 config INPUT_RB532_BUTTON
627 tristate "Mikrotik Routerboard 532 button interface"
628 depends on MIKROTIK_RB532
632 Say Y here if you want support for the S1 button built into
633 Mikrotik's Routerboard 532.
635 To compile this driver as a module, choose M here: the
636 module will be called rb532_button.
638 config INPUT_DA9052_ONKEY
639 tristate "Dialog DA9052/DA9053 Onkey"
640 depends on PMIC_DA9052
642 Support the ONKEY of Dialog DA9052 PMICs as an input device
643 reporting power button status.
645 To compile this driver as a module, choose M here: the
646 module will be called da9052_onkey.
648 config INPUT_DA9055_ONKEY
649 tristate "Dialog Semiconductor DA9055 ONKEY"
650 depends on MFD_DA9055
652 Support the ONKEY of DA9055 PMICs as an input device
653 reporting power button status.
655 To compile this driver as a module, choose M here: the module
656 will be called da9055_onkey.
658 config INPUT_DA9063_ONKEY
659 tristate "Dialog DA9063/62/61 OnKey"
660 depends on MFD_DA9063 || MFD_DA9062
662 Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
663 Management ICs as an input device capable of reporting the
666 To compile this driver as a module, choose M here: the module
667 will be called da9063_onkey.
669 config INPUT_DM355EVM
670 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
671 depends on MFD_DM355EVM_MSP
672 select INPUT_SPARSEKMAP
674 Supports the pushbuttons and IR remote used with
677 To compile this driver as a module, choose M here: the
678 module will be called dm355evm_keys.
680 config INPUT_WM831X_ON
681 tristate "WM831X ON pin"
682 depends on MFD_WM831X
684 Support the ON pin of WM831X PMICs as an input device
685 reporting power button status.
687 To compile this driver as a module, choose M here: the module
688 will be called wm831x_on.
691 tristate "Motorola EZX PCAP misc input events"
694 Say Y here if you want to use Power key and Headphone button
695 on Motorola EZX phones.
697 To compile this driver as a module, choose M here: the
698 module will be called pcap_keys.
701 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
704 Say Y here if you have a Accelerometer interface using the
705 ADXL345/6 controller, and your board-specific initialization
706 code includes that in its table of devices.
708 This driver can use either I2C or SPI communication to the
709 ADXL345/6 controller. Select the appropriate method for
712 If unsure, say N (but it's safe to say "Y").
714 To compile this driver as a module, choose M here: the
715 module will be called adxl34x.
717 config INPUT_ADXL34X_I2C
718 tristate "support I2C bus connection"
719 depends on INPUT_ADXL34X && I2C
722 Say Y here if you have ADXL345/6 hooked to an I2C bus.
724 To compile this driver as a module, choose M here: the
725 module will be called adxl34x-i2c.
727 config INPUT_ADXL34X_SPI
728 tristate "support SPI bus connection"
729 depends on INPUT_ADXL34X && SPI
732 Say Y here if you have ADXL345/6 hooked to a SPI bus.
734 To compile this driver as a module, choose M here: the
735 module will be called adxl34x-spi.
738 tristate "IMS Passenger Control Unit driver"
740 depends on LEDS_CLASS
742 Say Y here if you have system with IMS Rave Passenger Control Unit.
744 To compile this driver as a module, choose M here: the module will be
748 tristate "VTI CMA3000 Tri-axis accelerometer"
750 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
753 This driver currently only supports I2C interface to the
754 controller. Also select the I2C method.
758 To compile this driver as a module, choose M here: the
759 module will be called cma3000_d0x.
761 config INPUT_CMA3000_I2C
762 tristate "Support I2C bus connection"
763 depends on INPUT_CMA3000 && I2C
765 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
766 through I2C interface.
768 To compile this driver as a module, choose M here: the
769 module will be called cma3000_d0x_i2c.
771 config INPUT_XEN_KBDDEV_FRONTEND
772 tristate "Xen virtual keyboard and mouse support"
775 select XEN_XENBUS_FRONTEND
777 This driver implements the front-end of the Xen virtual
778 keyboard and mouse device driver. It communicates with a back-end
781 To compile this driver as a module, choose M here: the
782 module will be called xen-kbdfront.
784 config INPUT_SIRFSOC_ONKEY
785 tristate "CSR SiRFSoC power on/off/suspend key support"
786 depends on ARCH_SIRF && OF
789 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
790 in Linux, after you press the onkey, system will suspend.
794 config INPUT_IDEAPAD_SLIDEBAR
795 tristate "IdeaPad Laptop Slidebar"
797 depends on SERIO_I8042
799 Say Y here if you have an IdeaPad laptop with a slidebar.
801 To compile this driver as a module, choose M here: the
802 module will be called ideapad_slidebar.
804 config INPUT_SOC_BUTTON_ARRAY
805 tristate "Windows-compatible SoC Button Array"
806 depends on KEYBOARD_GPIO
808 Say Y here if you have a SoC-based tablet that originally
811 To compile this driver as a module, choose M here: the
812 module will be called soc_button_array.
814 config INPUT_DRV260X_HAPTICS
815 tristate "TI DRV260X haptics support"
816 depends on INPUT && I2C
817 depends on GPIOLIB || COMPILE_TEST
818 select INPUT_FF_MEMLESS
821 Say Y to enable support for the TI DRV260X haptics driver.
823 To compile this driver as a module, choose M here: the
824 module will be called drv260x-haptics.
826 config INPUT_DRV2665_HAPTICS
827 tristate "TI DRV2665 haptics support"
828 depends on INPUT && I2C
829 select INPUT_FF_MEMLESS
832 Say Y to enable support for the TI DRV2665 haptics driver.
834 To compile this driver as a module, choose M here: the
835 module will be called drv2665-haptics.
837 config INPUT_DRV2667_HAPTICS
838 tristate "TI DRV2667 haptics support"
839 depends on INPUT && I2C
840 select INPUT_FF_MEMLESS
843 Say Y to enable support for the TI DRV2667 haptics driver.
845 To compile this driver as a module, choose M here: the
846 module will be called drv2667-haptics.
848 config INPUT_HISI_POWERKEY
849 tristate "Hisilicon PMIC ONKEY support"
850 depends on ARCH_HISI || COMPILE_TEST
852 Say Y to enable support for PMIC ONKEY.
854 To compile this driver as a module, choose M here: the
855 module will be called hisi_powerkey.
857 config INPUT_RAVE_SP_PWRBUTTON
858 tristate "RAVE SP Power button Driver"
859 depends on RAVE_SP_CORE
861 Say Y here if you want to enable power key reporting from RAVE SP
863 To compile this driver as a module, choose M here: the
864 module will be called rave-sp-pwrbutton.
866 config INPUT_SC27XX_VIBRA
867 tristate "Spreadtrum sc27xx vibrator support"
868 depends on MFD_SC27XX_PMIC || COMPILE_TEST
869 select INPUT_FF_MEMLESS
871 This option enables support for Spreadtrum sc27xx vibrator driver.
873 To compile this driver as a module, choose M here. The module will
874 be called sc27xx_vibra.
876 config INPUT_STPMIC1_ONKEY
877 tristate "STPMIC1 PMIC Onkey support"
878 depends on MFD_STPMIC1
880 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
881 can be used to wakeup from low power modes and force a shut-down on
884 To compile this driver as a module, choose M here: the
885 module will be called stpmic1_onkey.