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.
86 tristate "BMA150/SMB380 acceleration sensor support"
90 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
91 acceleration sensor hooked to an I2C bus.
93 To compile this driver as a module, choose M here: the
94 module will be called bma150.
96 config INPUT_E3X0_BUTTON
97 tristate "NI Ettus Research USRP E3xx Button support."
100 Say Y here to enable support for the NI Ettus Research
103 To compile this driver as a module, choose M here: the
104 module will be called e3x0_button.
107 tristate "PC Speaker support"
108 depends on PCSPKR_PLATFORM
110 Say Y here if you want the standard PC Speaker to be used for
115 To compile this driver as a module, choose M here: the
116 module will be called pcspkr.
118 config INPUT_PM8941_PWRKEY
119 tristate "Qualcomm PM8941 power key support"
120 depends on MFD_SPMI_PMIC
122 Say Y here if you want support for the power key usually found
123 on boards using a Qualcomm PM8941 compatible PMIC.
127 To compile this driver as a module, choose M here: the module
128 will be called pm8941-pwrkey.
130 config INPUT_PM8XXX_VIBRATOR
131 tristate "Qualcomm PM8XXX vibrator support"
132 depends on MFD_PM8XXX
133 select INPUT_FF_MEMLESS
135 This option enables device driver support for the vibrator
136 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
137 from input framework.
139 To compile this driver as module, choose M here: the
140 module will be called pm8xxx-vibrator.
142 config INPUT_PMIC8XXX_PWRKEY
143 tristate "PMIC8XXX power key support"
144 depends on MFD_PM8XXX
146 Say Y here if you want support for the PMIC8XXX power key.
150 To compile this driver as a module, choose M here: the
151 module will be called pmic8xxx-pwrkey.
153 config INPUT_SPARCSPKR
154 tristate "SPARC Speaker support"
155 depends on PCI && SPARC64
157 Say Y here if you want the standard Speaker on Sparc PCI systems
158 to be used for bells and whistles.
162 To compile this driver as a module, choose M here: the
163 module will be called sparcspkr.
165 config INPUT_M68K_BEEP
166 tristate "M68k Beeper support"
169 config INPUT_MAX77693_HAPTIC
170 tristate "MAXIM MAX77693/MAX77843 haptic controller support"
171 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
172 select INPUT_FF_MEMLESS
174 This option enables support for the haptic controller on
175 MAXIM MAX77693 and MAX77843 chips.
177 To compile this driver as module, choose M here: the
178 module will be called max77693-haptic.
180 config INPUT_MAX8925_ONKEY
181 tristate "MAX8925 ONKEY support"
182 depends on MFD_MAX8925
184 Support the ONKEY of MAX8925 PMICs as an input device
185 reporting power button status.
187 To compile this driver as a module, choose M here: the module
188 will be called max8925_onkey.
190 config INPUT_MAX8997_HAPTIC
191 tristate "MAXIM MAX8997 haptic controller support"
192 depends on PWM && MFD_MAX8997
193 select INPUT_FF_MEMLESS
195 This option enables device driver support for the haptic controller
196 on MAXIM MAX8997 chip. This driver supports ff-memless interface
197 from input framework.
199 To compile this driver as module, choose M here: the
200 module will be called max8997-haptic.
202 config INPUT_MC13783_PWRBUTTON
203 tristate "MC13783 ON buttons"
204 depends on MFD_MC13XXX
206 Support the ON buttons of MC13783 PMIC as an input device
207 reporting power button status.
209 To compile this driver as a module, choose M here: the module
210 will be called mc13783-pwrbutton.
213 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
217 Say Y here if you want to support Freescale's MMA8450 Accelerometer
218 through I2C interface.
220 To compile this driver as a module, choose M here: the
221 module will be called mma8450.
224 tristate "MPU3050 Triaxial gyroscope sensor"
227 Say Y here if you want to support InvenSense MPU3050
228 connected via an I2C bus.
230 To compile this driver as a module, choose M here: the
231 module will be called mpu3050.
234 tristate "Fujitsu Lifebook Application Panel buttons"
235 depends on X86 && I2C && LEDS_CLASS
237 select CHECK_SIGNATURE
239 Say Y here for support of the Application Panel buttons, used on
240 Fujitsu Lifebook. These are attached to the mainboard through
241 an SMBus interface managed by the I2C Intel ICH (i801) driver,
242 which you should also build for this kernel.
244 To compile this driver as a module, choose M here: the module will
248 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
250 depends on GPIOLIB || COMPILE_TEST
252 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
253 hooked to an I2C bus.
255 To compile this driver as a module, choose M here: the
256 module will be called gp2ap002a00f.
258 config INPUT_GPIO_BEEPER
259 tristate "Generic GPIO Beeper support"
260 depends on GPIOLIB || COMPILE_TEST
262 Say Y here if you have a beeper connected to a GPIO pin.
264 To compile this driver as a module, choose M here: the
265 module will be called gpio-beeper.
267 config INPUT_GPIO_TILT_POLLED
268 tristate "Polled GPIO tilt switch"
269 depends on GPIOLIB || COMPILE_TEST
272 This driver implements support for tilt switches connected
273 to GPIO pins that are not capable of generating interrupts.
275 The list of gpios to use and the mapping of their states
276 to specific angles is done via platform data.
278 To compile this driver as a module, choose M here: the
279 module will be called gpio_tilt_polled.
281 config INPUT_IXP4XX_BEEPER
282 tristate "IXP4XX Beeper support"
283 depends on ARCH_IXP4XX
285 If you say yes here, you can connect a beeper to the
286 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
290 To compile this driver as a module, choose M here: the
291 module will be called ixp4xx-beeper.
293 config INPUT_COBALT_BTNS
294 tristate "Cobalt button interface"
295 depends on MIPS_COBALT
298 Say Y here if you want to support MIPS Cobalt button interface.
300 To compile this driver as a module, choose M here: the
301 module will be called cobalt_btns.
303 config INPUT_WISTRON_BTNS
304 tristate "x86 Wistron laptop button interface"
307 select INPUT_SPARSEKMAP
310 select CHECK_SIGNATURE
312 Say Y here for support of Wistron laptop button interfaces, used on
313 laptops of various brands, including Acer and Fujitsu-Siemens. If
314 available, mail and wifi LEDs will be controllable via /sys/class/leds.
316 To compile this driver as a module, choose M here: the module will
317 be called wistron_btns.
319 config INPUT_ATLAS_BTNS
320 tristate "x86 Atlas button interface"
321 depends on X86 && ACPI
323 Say Y here for support of Atlas wallmount touchscreen buttons.
324 The events will show up as scancodes F1 through F9 via evdev.
326 To compile this driver as a module, choose M here: the module will
327 be called atlas_btns.
329 config INPUT_ATI_REMOTE2
330 tristate "ATI / Philips USB RF remote control"
331 depends on USB_ARCH_HAS_HCD
334 Say Y here if you want to use an ATI or Philips USB RF remote control.
335 These are RF remotes with USB receivers.
336 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
337 and is also available as a separate product.
338 This driver provides mouse pointer, left and right mouse buttons,
339 and maps all the other remote buttons to keypress events.
341 To compile this driver as a module, choose M here: the module will be
344 config INPUT_KEYCHORD
345 tristate "Key chord input driver support"
347 Say Y here if you want to enable the key chord driver
348 accessible at /dev/keychord. This driver can be used
349 for receiving notifications when client specified key
350 combinations are pressed.
352 To compile this driver as a module, choose M here: the
353 module will be called keychord.
355 config INPUT_KEYSPAN_REMOTE
356 tristate "Keyspan DMR USB remote control"
357 depends on USB_ARCH_HAS_HCD
360 Say Y here if you want to use a Keyspan DMR USB remote control.
361 Currently only the UIA-11 type of receiver has been tested. The tag
362 on the receiver that connects to the USB port should have a P/N that
363 will tell you what type of DMR you have. The UIA-10 type is not
364 supported at this time. This driver maps all buttons to keypress
367 To compile this driver as a module, choose M here: the module will
368 be called keyspan_remote.
371 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
374 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
377 To compile this driver as a module, choose M here: the module will
380 config INPUT_KXTJ9_POLLED_MODE
381 bool "Enable polling mode support"
382 depends on INPUT_KXTJ9
385 Say Y here if you need accelerometer to work in polling mode.
387 config INPUT_POWERMATE
388 tristate "Griffin PowerMate and Contour Jog support"
389 depends on USB_ARCH_HAS_HCD
392 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
393 These are aluminum dials which can measure clockwise and anticlockwise
394 rotation. The dial also acts as a pushbutton. The base contains an LED
395 which can be instructed to pulse or to switch to a particular intensity.
397 You can download userspace tools from
398 <http://sowerbutts.com/powermate/>.
400 To compile this driver as a module, choose M here: the
401 module will be called powermate.
404 tristate "Yealink usb-p1k voip phone"
405 depends on USB_ARCH_HAS_HCD
408 Say Y here if you want to enable keyboard and LCD functions of the
409 Yealink usb-p1k usb phones. The audio part is enabled by the generic
410 usb sound driver, so you might want to enable that as well.
412 For information about how to use these additional functions, see
413 <file:Documentation/input/yealink.txt>.
415 To compile this driver as a module, choose M here: the module will be
419 tristate "C-Media CM109 USB I/O Controller"
420 depends on USB_ARCH_HAS_HCD
423 Say Y here if you want to enable keyboard and buzzer functions of the
424 C-Media CM109 usb phones. The audio part is enabled by the generic
425 usb sound driver, so you might want to enable that as well.
427 To compile this driver as a module, choose M here: the module will be
430 config INPUT_REGULATOR_HAPTIC
431 tristate "Regulator haptics support"
433 select INPUT_FF_MEMLESS
435 This option enables device driver support for the haptic controlled
436 by a regulator. This driver supports ff-memless interface
437 from input framework.
439 To compile this driver as a module, choose M here: the
440 module will be called regulator-haptic.
442 config INPUT_RETU_PWRBUTTON
443 tristate "Retu Power button Driver"
446 Say Y here if you want to enable power key reporting via the
447 Retu chips found in Nokia Internet Tablets (770, N800, N810).
449 To compile this driver as a module, choose M here. The module will
450 be called retu-pwrbutton.
452 config INPUT_RK8XX_PWRKEY
453 tristate "Rockchip RK8XX pwrkey driver"
456 Select this option to enable the pwrkey module of Rockchip RK8XX PMIC.
458 config INPUT_TPS65218_PWRBUTTON
459 tristate "TPS65218 Power button driver"
460 depends on MFD_TPS65218
462 Say Y here if you want to enable power buttong reporting for
463 the TPS65218 Power Management IC device.
465 To compile this driver as a module, choose M here. The module will
466 be called tps65218-pwrbutton.
468 config INPUT_AXP20X_PEK
469 tristate "X-Powers AXP20X power button driver"
470 depends on MFD_AXP20X
472 Say Y here if you want to enable power key reporting via the
475 To compile this driver as a module, choose M here. The module will
476 be called axp20x-pek.
479 config INPUT_TWL4030_PWRBUTTON
480 tristate "TWL4030 Power button Driver"
481 depends on TWL4030_CORE
483 Say Y here if you want to enable power key reporting via the
484 TWL4030 family of chips.
486 To compile this driver as a module, choose M here. The module will
487 be called twl4030_pwrbutton.
489 config INPUT_TWL4030_VIBRA
490 tristate "Support for TWL4030 Vibrator"
491 depends on TWL4030_CORE
492 select MFD_TWL4030_AUDIO
493 select INPUT_FF_MEMLESS
495 This option enables support for TWL4030 Vibrator Driver.
497 To compile this driver as a module, choose M here. The module will
498 be called twl4030_vibra.
500 config INPUT_TWL6040_VIBRA
501 tristate "Support for TWL6040 Vibrator"
502 depends on TWL6040_CORE
503 select INPUT_FF_MEMLESS
505 This option enables support for TWL6040 Vibrator Driver.
507 To compile this driver as a module, choose M here. The module will
508 be called twl6040_vibra.
511 tristate "User level driver support"
513 Say Y here if you want to support user level drivers for input
514 subsystem accessible under char device 10:223 - /dev/input/uinput.
516 To compile this driver as a module, choose M here: the
517 module will be called uinput.
519 config INPUT_SGI_BTNS
520 tristate "SGI Indy/O2 volume button interface"
521 depends on SGI_IP22 || SGI_IP32
524 Say Y here if you want to support SGI Indy/O2 volume button interface.
526 To compile this driver as a module, choose M here: the
527 module will be called sgi_btns.
530 tristate "GPIO driver support"
532 Say Y here if you want to support gpio based keys, wheels etc...
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_GPIO_ROTARY_ENCODER
581 tristate "Rotary encoders connected to GPIO pins"
582 depends on GPIOLIB || COMPILE_TEST
584 Say Y here to add support for rotary encoders connected to GPIO lines.
585 Check file:Documentation/input/rotary-encoder.txt for more
588 To compile this driver as a module, choose M here: the
589 module will be called rotary_encoder.
591 config INPUT_RB532_BUTTON
592 tristate "Mikrotik Routerboard 532 button interface"
593 depends on MIKROTIK_RB532
597 Say Y here if you want support for the S1 button built into
598 Mikrotik's Routerboard 532.
600 To compile this driver as a module, choose M here: the
601 module will be called rb532_button.
603 config INPUT_DA9052_ONKEY
604 tristate "Dialog DA9052/DA9053 Onkey"
605 depends on PMIC_DA9052
607 Support the ONKEY of Dialog DA9052 PMICs as an input device
608 reporting power button status.
610 To compile this driver as a module, choose M here: the
611 module will be called da9052_onkey.
613 config INPUT_DA9055_ONKEY
614 tristate "Dialog Semiconductor DA9055 ONKEY"
615 depends on MFD_DA9055
617 Support the ONKEY of DA9055 PMICs as an input device
618 reporting power button status.
620 To compile this driver as a module, choose M here: the module
621 will be called da9055_onkey.
623 config INPUT_DA9063_ONKEY
624 tristate "Dialog DA9062/63 OnKey"
625 depends on MFD_DA9063 || MFD_DA9062
627 Support the ONKEY of Dialog DA9063 and DA9062 Power Management ICs
628 as an input device capable of reporting the power button status.
630 To compile this driver as a module, choose M here: the module
631 will be called da9063_onkey.
633 config INPUT_DM355EVM
634 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
635 depends on MFD_DM355EVM_MSP
636 select INPUT_SPARSEKMAP
638 Supports the pushbuttons and IR remote used with
641 To compile this driver as a module, choose M here: the
642 module will be called dm355evm_keys.
644 config INPUT_BFIN_ROTARY
645 tristate "Blackfin Rotary support"
646 depends on BF54x || BF52x
648 Say Y here if you want to use the Blackfin Rotary.
650 To compile this driver as a module, choose M here: the
651 module will be called bfin-rotary.
653 config INPUT_WM831X_ON
654 tristate "WM831X ON pin"
655 depends on MFD_WM831X
657 Support the ON pin of WM831X PMICs as an input device
658 reporting power button status.
660 To compile this driver as a module, choose M here: the module
661 will be called wm831x_on.
664 tristate "Motorola EZX PCAP misc input events"
667 Say Y here if you want to use Power key and Headphone button
668 on Motorola EZX phones.
670 To compile this driver as a module, choose M here: the
671 module will be called pcap_keys.
674 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
677 Say Y here if you have a Accelerometer interface using the
678 ADXL345/6 controller, and your board-specific initialization
679 code includes that in its table of devices.
681 This driver can use either I2C or SPI communication to the
682 ADXL345/6 controller. Select the appropriate method for
685 If unsure, say N (but it's safe to say "Y").
687 To compile this driver as a module, choose M here: the
688 module will be called adxl34x.
690 config INPUT_ADXL34X_I2C
691 tristate "support I2C bus connection"
692 depends on INPUT_ADXL34X && I2C
695 Say Y here if you have ADXL345/6 hooked to an I2C bus.
697 To compile this driver as a module, choose M here: the
698 module will be called adxl34x-i2c.
700 config INPUT_ADXL34X_SPI
701 tristate "support SPI bus connection"
702 depends on INPUT_ADXL34X && SPI
705 Say Y here if you have ADXL345/6 hooked to a SPI bus.
707 To compile this driver as a module, choose M here: the
708 module will be called adxl34x-spi.
711 tristate "IMS Passenger Control Unit driver"
713 depends on LEDS_CLASS
715 Say Y here if you have system with IMS Rave Passenger Control Unit.
717 To compile this driver as a module, choose M here: the module will be
721 tristate "VTI CMA3000 Tri-axis accelerometer"
723 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
726 This driver currently only supports I2C interface to the
727 controller. Also select the I2C method.
731 To compile this driver as a module, choose M here: the
732 module will be called cma3000_d0x.
734 config INPUT_CMA3000_I2C
735 tristate "Support I2C bus connection"
736 depends on INPUT_CMA3000 && I2C
738 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
739 through I2C interface.
741 To compile this driver as a module, choose M here: the
742 module will be called cma3000_d0x_i2c.
744 config INPUT_XEN_KBDDEV_FRONTEND
745 tristate "Xen virtual keyboard and mouse support"
748 select XEN_XENBUS_FRONTEND
750 This driver implements the front-end of the Xen virtual
751 keyboard and mouse device driver. It communicates with a back-end
754 To compile this driver as a module, choose M here: the
755 module will be called xen-kbdfront.
757 config INPUT_SIRFSOC_ONKEY
758 bool "CSR SiRFSoC power on/off/suspend key support"
759 depends on ARCH_SIRF && OF
762 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
763 in Linux, after you press the onkey, system will suspend.
767 config INPUT_IDEAPAD_SLIDEBAR
768 tristate "IdeaPad Laptop Slidebar"
770 depends on SERIO_I8042
772 Say Y here if you have an IdeaPad laptop with a slidebar.
774 To compile this driver as a module, choose M here: the
775 module will be called ideapad_slidebar.
777 config INPUT_SOC_BUTTON_ARRAY
778 tristate "Windows-compatible SoC Button Array"
779 depends on KEYBOARD_GPIO
781 Say Y here if you have a SoC-based tablet that originally
784 To compile this driver as a module, choose M here: the
785 module will be called soc_button_array.
787 config INPUT_DRV260X_HAPTICS
788 tristate "TI DRV260X haptics support"
789 depends on INPUT && I2C
790 depends on GPIOLIB || COMPILE_TEST
791 select INPUT_FF_MEMLESS
794 Say Y to enable support for the TI DRV260X haptics driver.
796 To compile this driver as a module, choose M here: the
797 module will be called drv260x-haptics.
799 config INPUT_DRV2665_HAPTICS
800 tristate "TI DRV2665 haptics support"
801 depends on INPUT && I2C
802 select INPUT_FF_MEMLESS
805 Say Y to enable support for the TI DRV2665 haptics driver.
807 To compile this driver as a module, choose M here: the
808 module will be called drv2665-haptics.
810 config INPUT_DRV2667_HAPTICS
811 tristate "TI DRV2667 haptics support"
812 depends on INPUT && I2C
813 select INPUT_FF_MEMLESS
816 Say Y to enable support for the TI DRV2667 haptics driver.
818 To compile this driver as a module, choose M here: the
819 module will be called drv2667-haptics.