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_IXP4XX_BEEPER
294 tristate "IXP4XX Beeper support"
295 depends on ARCH_IXP4XX
297 If you say yes here, you can connect a beeper to the
298 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
302 To compile this driver as a module, choose M here: the
303 module will be called ixp4xx-beeper.
305 config INPUT_COBALT_BTNS
306 tristate "Cobalt button interface"
307 depends on MIPS_COBALT
310 Say Y here if you want to support MIPS Cobalt button interface.
312 To compile this driver as a module, choose M here: the
313 module will be called cobalt_btns.
315 config INPUT_CPCAP_PWRBUTTON
316 tristate "CPCAP OnKey"
319 Say Y here if you want to enable power key reporting via the
322 To compile this driver as a module, choose M here. The module will
323 be called cpcap-pwrbutton.
325 config INPUT_WISTRON_BTNS
326 tristate "x86 Wistron laptop button interface"
329 select INPUT_SPARSEKMAP
332 select CHECK_SIGNATURE
334 Say Y here for support of Wistron laptop button interfaces, used on
335 laptops of various brands, including Acer and Fujitsu-Siemens. If
336 available, mail and wifi LEDs will be controllable via /sys/class/leds.
338 To compile this driver as a module, choose M here: the module will
339 be called wistron_btns.
341 config INPUT_ATLAS_BTNS
342 tristate "x86 Atlas button interface"
343 depends on X86 && ACPI
345 Say Y here for support of Atlas wallmount touchscreen buttons.
346 The events will show up as scancodes F1 through F9 via evdev.
348 To compile this driver as a module, choose M here: the module will
349 be called atlas_btns.
351 config INPUT_ATI_REMOTE2
352 tristate "ATI / Philips USB RF remote control"
353 depends on USB_ARCH_HAS_HCD
356 Say Y here if you want to use an ATI or Philips USB RF remote control.
357 These are RF remotes with USB receivers.
358 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
359 and is also available as a separate product.
360 This driver provides mouse pointer, left and right mouse buttons,
361 and maps all the other remote buttons to keypress events.
363 To compile this driver as a module, choose M here: the module will be
366 config INPUT_KEYSPAN_REMOTE
367 tristate "Keyspan DMR USB remote control"
368 depends on USB_ARCH_HAS_HCD
371 Say Y here if you want to use a Keyspan DMR USB remote control.
372 Currently only the UIA-11 type of receiver has been tested. The tag
373 on the receiver that connects to the USB port should have a P/N that
374 will tell you what type of DMR you have. The UIA-10 type is not
375 supported at this time. This driver maps all buttons to keypress
378 To compile this driver as a module, choose M here: the module will
379 be called keyspan_remote.
382 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
385 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
388 To compile this driver as a module, choose M here: the module will
391 config INPUT_KXTJ9_POLLED_MODE
392 bool "Enable polling mode support"
393 depends on INPUT_KXTJ9
396 Say Y here if you need accelerometer to work in polling mode.
398 config INPUT_POWERMATE
399 tristate "Griffin PowerMate and Contour Jog support"
400 depends on USB_ARCH_HAS_HCD
403 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
404 These are aluminum dials which can measure clockwise and anticlockwise
405 rotation. The dial also acts as a pushbutton. The base contains an LED
406 which can be instructed to pulse or to switch to a particular intensity.
408 You can download userspace tools from
409 <http://sowerbutts.com/powermate/>.
411 To compile this driver as a module, choose M here: the
412 module will be called powermate.
415 tristate "Yealink usb-p1k voip phone"
416 depends on USB_ARCH_HAS_HCD
419 Say Y here if you want to enable keyboard and LCD functions of the
420 Yealink usb-p1k usb phones. The audio part is enabled by the generic
421 usb sound driver, so you might want to enable that as well.
423 For information about how to use these additional functions, see
424 <file:Documentation/input/devices/yealink.rst>.
426 To compile this driver as a module, choose M here: the module will be
430 tristate "C-Media CM109 USB I/O Controller"
431 depends on USB_ARCH_HAS_HCD
434 Say Y here if you want to enable keyboard and buzzer functions of the
435 C-Media CM109 usb phones. The audio part is enabled by the generic
436 usb sound driver, so you might want to enable that as well.
438 To compile this driver as a module, choose M here: the module will be
441 config INPUT_REGULATOR_HAPTIC
442 tristate "Regulator haptics support"
444 select INPUT_FF_MEMLESS
446 This option enables device driver support for the haptic controlled
447 by a regulator. This driver supports ff-memless interface
448 from input framework.
450 To compile this driver as a module, choose M here: the
451 module will be called regulator-haptic.
453 config INPUT_RETU_PWRBUTTON
454 tristate "Retu Power button Driver"
457 Say Y here if you want to enable power key reporting via the
458 Retu chips found in Nokia Internet Tablets (770, N800, N810).
460 To compile this driver as a module, choose M here. The module will
461 be called retu-pwrbutton.
463 config INPUT_TPS65218_PWRBUTTON
464 tristate "TPS65218 Power button driver"
465 depends on (MFD_TPS65217 || MFD_TPS65218)
467 Say Y here if you want to enable power button reporting for
468 TPS65217 and TPS65218 Power Management IC devices.
470 To compile this driver as a module, choose M here. The module will
471 be called tps65218-pwrbutton.
473 config INPUT_AXP20X_PEK
474 tristate "X-Powers AXP20X power button driver"
475 depends on MFD_AXP20X
477 Say Y here if you want to enable power key reporting via the
480 To compile this driver as a module, choose M here. The module will
481 be called axp20x-pek.
484 config INPUT_TWL4030_PWRBUTTON
485 tristate "TWL4030 Power button Driver"
486 depends on TWL4030_CORE
488 Say Y here if you want to enable power key reporting via the
489 TWL4030 family of chips.
491 To compile this driver as a module, choose M here. The module will
492 be called twl4030_pwrbutton.
494 config INPUT_TWL4030_VIBRA
495 tristate "Support for TWL4030 Vibrator"
496 depends on TWL4030_CORE
497 select MFD_TWL4030_AUDIO
498 select INPUT_FF_MEMLESS
500 This option enables support for TWL4030 Vibrator Driver.
502 To compile this driver as a module, choose M here. The module will
503 be called twl4030_vibra.
505 config INPUT_TWL6040_VIBRA
506 tristate "Support for TWL6040 Vibrator"
507 depends on TWL6040_CORE
508 select INPUT_FF_MEMLESS
510 This option enables support for TWL6040 Vibrator Driver.
512 To compile this driver as a module, choose M here. The module will
513 be called twl6040_vibra.
516 tristate "User level driver support"
518 Say Y here if you want to support user level drivers for input
519 subsystem accessible under char device 10:223 - /dev/input/uinput.
521 To compile this driver as a module, choose M here: the
522 module will be called uinput.
524 config INPUT_SGI_BTNS
525 tristate "SGI Indy/O2 volume button interface"
526 depends on SGI_IP22 || SGI_IP32
529 Say Y here if you want to support SGI Indy/O2 volume button interface.
531 To compile this driver as a module, choose M here: the
532 module will be called sgi_btns.
535 tristate "HP SDC Real Time Clock"
536 depends on (GSC || HP300) && SERIO
539 Say Y here if you want to support the built-in real time clock
540 of the HP SDC controller.
542 config INPUT_PALMAS_PWRBUTTON
543 tristate "Palmas Power button Driver"
544 depends on MFD_PALMAS
546 Say Y here if you want to enable power key reporting via the
547 Palmas family of PMICs.
549 To compile this driver as a module, choose M here. The module will
550 be called palmas_pwrbutton.
552 config INPUT_PCF50633_PMU
553 tristate "PCF50633 PMU events"
554 depends on MFD_PCF50633
556 Say Y to include support for delivering PMU events via input
557 layer on NXP PCF50633.
560 tristate "PCF8574 Keypad input device"
563 Say Y here if you want to support a keypad connected via I2C
566 To compile this driver as a module, choose M here: the
567 module will be called pcf8574_keypad.
569 config INPUT_PWM_BEEPER
570 tristate "PWM beeper support"
573 Say Y here to get support for PWM based beeper devices.
577 To compile this driver as a module, choose M here: the module will be
580 config INPUT_PWM_VIBRA
581 tristate "PWM vibrator support"
583 select INPUT_FF_MEMLESS
585 Say Y here to get support for PWM based vibrator devices.
589 To compile this driver as a module, choose M here: the module will be
592 config INPUT_RK805_PWRKEY
593 tristate "Rockchip RK805 PMIC power key support"
596 Select this option to enable power key driver for RK805.
600 To compile this driver as a module, choose M here: the module will be
603 config INPUT_GPIO_ROTARY_ENCODER
604 tristate "Rotary encoders connected to GPIO pins"
605 depends on GPIOLIB || COMPILE_TEST
607 Say Y here to add support for rotary encoders connected to GPIO lines.
608 Check file:Documentation/input/devices/rotary-encoder.rst for more
611 To compile this driver as a module, choose M here: the
612 module will be called rotary_encoder.
614 config INPUT_RB532_BUTTON
615 tristate "Mikrotik Routerboard 532 button interface"
616 depends on MIKROTIK_RB532
620 Say Y here if you want support for the S1 button built into
621 Mikrotik's Routerboard 532.
623 To compile this driver as a module, choose M here: the
624 module will be called rb532_button.
626 config INPUT_DA9052_ONKEY
627 tristate "Dialog DA9052/DA9053 Onkey"
628 depends on PMIC_DA9052
630 Support the ONKEY of Dialog DA9052 PMICs as an input device
631 reporting power button status.
633 To compile this driver as a module, choose M here: the
634 module will be called da9052_onkey.
636 config INPUT_DA9055_ONKEY
637 tristate "Dialog Semiconductor DA9055 ONKEY"
638 depends on MFD_DA9055
640 Support the ONKEY of DA9055 PMICs as an input device
641 reporting power button status.
643 To compile this driver as a module, choose M here: the module
644 will be called da9055_onkey.
646 config INPUT_DA9063_ONKEY
647 tristate "Dialog DA9063/62/61 OnKey"
648 depends on MFD_DA9063 || MFD_DA9062
650 Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
651 Management ICs as an input device capable of reporting the
654 To compile this driver as a module, choose M here: the module
655 will be called da9063_onkey.
657 config INPUT_DM355EVM
658 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
659 depends on MFD_DM355EVM_MSP
660 select INPUT_SPARSEKMAP
662 Supports the pushbuttons and IR remote used with
665 To compile this driver as a module, choose M here: the
666 module will be called dm355evm_keys.
668 config INPUT_WM831X_ON
669 tristate "WM831X ON pin"
670 depends on MFD_WM831X
672 Support the ON pin of WM831X PMICs as an input device
673 reporting power button status.
675 To compile this driver as a module, choose M here: the module
676 will be called wm831x_on.
679 tristate "Motorola EZX PCAP misc input events"
682 Say Y here if you want to use Power key and Headphone button
683 on Motorola EZX phones.
685 To compile this driver as a module, choose M here: the
686 module will be called pcap_keys.
689 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
692 Say Y here if you have a Accelerometer interface using the
693 ADXL345/6 controller, and your board-specific initialization
694 code includes that in its table of devices.
696 This driver can use either I2C or SPI communication to the
697 ADXL345/6 controller. Select the appropriate method for
700 If unsure, say N (but it's safe to say "Y").
702 To compile this driver as a module, choose M here: the
703 module will be called adxl34x.
705 config INPUT_ADXL34X_I2C
706 tristate "support I2C bus connection"
707 depends on INPUT_ADXL34X && I2C
710 Say Y here if you have ADXL345/6 hooked to an I2C bus.
712 To compile this driver as a module, choose M here: the
713 module will be called adxl34x-i2c.
715 config INPUT_ADXL34X_SPI
716 tristate "support SPI bus connection"
717 depends on INPUT_ADXL34X && SPI
720 Say Y here if you have ADXL345/6 hooked to a SPI bus.
722 To compile this driver as a module, choose M here: the
723 module will be called adxl34x-spi.
726 tristate "IMS Passenger Control Unit driver"
728 depends on LEDS_CLASS
730 Say Y here if you have system with IMS Rave Passenger Control Unit.
732 To compile this driver as a module, choose M here: the module will be
736 tristate "VTI CMA3000 Tri-axis accelerometer"
738 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
741 This driver currently only supports I2C interface to the
742 controller. Also select the I2C method.
746 To compile this driver as a module, choose M here: the
747 module will be called cma3000_d0x.
749 config INPUT_CMA3000_I2C
750 tristate "Support I2C bus connection"
751 depends on INPUT_CMA3000 && I2C
753 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
754 through I2C interface.
756 To compile this driver as a module, choose M here: the
757 module will be called cma3000_d0x_i2c.
759 config INPUT_XEN_KBDDEV_FRONTEND
760 tristate "Xen virtual keyboard and mouse support"
763 select XEN_XENBUS_FRONTEND
765 This driver implements the front-end of the Xen virtual
766 keyboard and mouse device driver. It communicates with a back-end
769 To compile this driver as a module, choose M here: the
770 module will be called xen-kbdfront.
772 config INPUT_SIRFSOC_ONKEY
773 tristate "CSR SiRFSoC power on/off/suspend key support"
774 depends on ARCH_SIRF && OF
777 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
778 in Linux, after you press the onkey, system will suspend.
782 config INPUT_IDEAPAD_SLIDEBAR
783 tristate "IdeaPad Laptop Slidebar"
785 depends on SERIO_I8042
787 Say Y here if you have an IdeaPad laptop with a slidebar.
789 To compile this driver as a module, choose M here: the
790 module will be called ideapad_slidebar.
792 config INPUT_SOC_BUTTON_ARRAY
793 tristate "Windows-compatible SoC Button Array"
794 depends on KEYBOARD_GPIO
796 Say Y here if you have a SoC-based tablet that originally
799 To compile this driver as a module, choose M here: the
800 module will be called soc_button_array.
802 config INPUT_DRV260X_HAPTICS
803 tristate "TI DRV260X haptics support"
804 depends on INPUT && I2C
805 depends on GPIOLIB || COMPILE_TEST
806 select INPUT_FF_MEMLESS
809 Say Y to enable support for the TI DRV260X haptics driver.
811 To compile this driver as a module, choose M here: the
812 module will be called drv260x-haptics.
814 config INPUT_DRV2665_HAPTICS
815 tristate "TI DRV2665 haptics support"
816 depends on INPUT && I2C
817 select INPUT_FF_MEMLESS
820 Say Y to enable support for the TI DRV2665 haptics driver.
822 To compile this driver as a module, choose M here: the
823 module will be called drv2665-haptics.
825 config INPUT_DRV2667_HAPTICS
826 tristate "TI DRV2667 haptics support"
827 depends on INPUT && I2C
828 select INPUT_FF_MEMLESS
831 Say Y to enable support for the TI DRV2667 haptics driver.
833 To compile this driver as a module, choose M here: the
834 module will be called drv2667-haptics.
836 config INPUT_HISI_POWERKEY
837 tristate "Hisilicon PMIC ONKEY support"
838 depends on ARCH_HISI || COMPILE_TEST
840 Say Y to enable support for PMIC ONKEY.
842 To compile this driver as a module, choose M here: the
843 module will be called hisi_powerkey.
845 config INPUT_RAVE_SP_PWRBUTTON
846 tristate "RAVE SP Power button Driver"
847 depends on RAVE_SP_CORE
849 Say Y here if you want to enable power key reporting from RAVE SP
851 To compile this driver as a module, choose M here: the
852 module will be called rave-sp-pwrbutton.
854 config INPUT_SC27XX_VIBRA
855 tristate "Spreadtrum sc27xx vibrator support"
856 depends on MFD_SC27XX_PMIC || COMPILE_TEST
857 select INPUT_FF_MEMLESS
859 This option enables support for Spreadtrum sc27xx vibrator driver.
861 To compile this driver as a module, choose M here. The module will
862 be called sc27xx_vibra.
864 config INPUT_STPMIC1_ONKEY
865 tristate "STPMIC1 PMIC Onkey support"
866 depends on MFD_STPMIC1
868 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
869 can be used to wakeup from low power modes and force a shut-down on
872 To compile this driver as a module, choose M here: the
873 module will be called stpmic1_onkey.