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_KEYSPAN_REMOTE
345 tristate "Keyspan DMR USB remote control"
346 depends on USB_ARCH_HAS_HCD
349 Say Y here if you want to use a Keyspan DMR USB remote control.
350 Currently only the UIA-11 type of receiver has been tested. The tag
351 on the receiver that connects to the USB port should have a P/N that
352 will tell you what type of DMR you have. The UIA-10 type is not
353 supported at this time. This driver maps all buttons to keypress
356 To compile this driver as a module, choose M here: the module will
357 be called keyspan_remote.
360 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
363 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
366 To compile this driver as a module, choose M here: the module will
369 config INPUT_KXTJ9_POLLED_MODE
370 bool "Enable polling mode support"
371 depends on INPUT_KXTJ9
374 Say Y here if you need accelerometer to work in polling mode.
376 config INPUT_POWERMATE
377 tristate "Griffin PowerMate and Contour Jog support"
378 depends on USB_ARCH_HAS_HCD
381 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
382 These are aluminum dials which can measure clockwise and anticlockwise
383 rotation. The dial also acts as a pushbutton. The base contains an LED
384 which can be instructed to pulse or to switch to a particular intensity.
386 You can download userspace tools from
387 <http://sowerbutts.com/powermate/>.
389 To compile this driver as a module, choose M here: the
390 module will be called powermate.
393 tristate "Yealink usb-p1k voip phone"
394 depends on USB_ARCH_HAS_HCD
397 Say Y here if you want to enable keyboard and LCD functions of the
398 Yealink usb-p1k usb phones. The audio part is enabled by the generic
399 usb sound driver, so you might want to enable that as well.
401 For information about how to use these additional functions, see
402 <file:Documentation/input/yealink.txt>.
404 To compile this driver as a module, choose M here: the module will be
408 tristate "C-Media CM109 USB I/O Controller"
409 depends on USB_ARCH_HAS_HCD
412 Say Y here if you want to enable keyboard and buzzer functions of the
413 C-Media CM109 usb phones. The audio part is enabled by the generic
414 usb sound driver, so you might want to enable that as well.
416 To compile this driver as a module, choose M here: the module will be
419 config INPUT_REGULATOR_HAPTIC
420 tristate "Regulator haptics support"
422 select INPUT_FF_MEMLESS
424 This option enables device driver support for the haptic controlled
425 by a regulator. This driver supports ff-memless interface
426 from input framework.
428 To compile this driver as a module, choose M here: the
429 module will be called regulator-haptic.
431 config INPUT_RETU_PWRBUTTON
432 tristate "Retu Power button Driver"
435 Say Y here if you want to enable power key reporting via the
436 Retu chips found in Nokia Internet Tablets (770, N800, N810).
438 To compile this driver as a module, choose M here. The module will
439 be called retu-pwrbutton.
441 config INPUT_TPS65218_PWRBUTTON
442 tristate "TPS65218 Power button driver"
443 depends on MFD_TPS65218
445 Say Y here if you want to enable power buttong reporting for
446 the TPS65218 Power Management IC device.
448 To compile this driver as a module, choose M here. The module will
449 be called tps65218-pwrbutton.
451 config INPUT_AXP20X_PEK
452 tristate "X-Powers AXP20X power button driver"
453 depends on MFD_AXP20X
455 Say Y here if you want to enable power key reporting via the
458 To compile this driver as a module, choose M here. The module will
459 be called axp20x-pek.
462 config INPUT_TWL4030_PWRBUTTON
463 tristate "TWL4030 Power button Driver"
464 depends on TWL4030_CORE
466 Say Y here if you want to enable power key reporting via the
467 TWL4030 family of chips.
469 To compile this driver as a module, choose M here. The module will
470 be called twl4030_pwrbutton.
472 config INPUT_TWL4030_VIBRA
473 tristate "Support for TWL4030 Vibrator"
474 depends on TWL4030_CORE
475 select MFD_TWL4030_AUDIO
476 select INPUT_FF_MEMLESS
478 This option enables support for TWL4030 Vibrator Driver.
480 To compile this driver as a module, choose M here. The module will
481 be called twl4030_vibra.
483 config INPUT_TWL6040_VIBRA
484 tristate "Support for TWL6040 Vibrator"
485 depends on TWL6040_CORE
486 select INPUT_FF_MEMLESS
488 This option enables support for TWL6040 Vibrator Driver.
490 To compile this driver as a module, choose M here. The module will
491 be called twl6040_vibra.
494 tristate "User level driver support"
496 Say Y here if you want to support user level drivers for input
497 subsystem accessible under char device 10:223 - /dev/input/uinput.
499 To compile this driver as a module, choose M here: the
500 module will be called uinput.
502 config INPUT_SGI_BTNS
503 tristate "SGI Indy/O2 volume button interface"
504 depends on SGI_IP22 || SGI_IP32
507 Say Y here if you want to support SGI Indy/O2 volume button interface.
509 To compile this driver as a module, choose M here: the
510 module will be called sgi_btns.
513 tristate "GPIO driver support"
515 Say Y here if you want to support gpio based keys, wheels etc...
518 tristate "HP SDC Real Time Clock"
519 depends on (GSC || HP300) && SERIO
522 Say Y here if you want to support the built-in real time clock
523 of the HP SDC controller.
525 config INPUT_PALMAS_PWRBUTTON
526 tristate "Palmas Power button Driver"
527 depends on MFD_PALMAS
529 Say Y here if you want to enable power key reporting via the
530 Palmas family of PMICs.
532 To compile this driver as a module, choose M here. The module will
533 be called palmas_pwrbutton.
535 config INPUT_PCF50633_PMU
536 tristate "PCF50633 PMU events"
537 depends on MFD_PCF50633
539 Say Y to include support for delivering PMU events via input
540 layer on NXP PCF50633.
543 tristate "PCF8574 Keypad input device"
546 Say Y here if you want to support a keypad connected via I2C
549 To compile this driver as a module, choose M here: the
550 module will be called pcf8574_keypad.
552 config INPUT_PWM_BEEPER
553 tristate "PWM beeper support"
556 Say Y here to get support for PWM based beeper devices.
560 To compile this driver as a module, choose M here: the module will be
563 config INPUT_GPIO_ROTARY_ENCODER
564 tristate "Rotary encoders connected to GPIO pins"
565 depends on GPIOLIB || COMPILE_TEST
567 Say Y here to add support for rotary encoders connected to GPIO lines.
568 Check file:Documentation/input/rotary-encoder.txt for more
571 To compile this driver as a module, choose M here: the
572 module will be called rotary_encoder.
574 config INPUT_RB532_BUTTON
575 tristate "Mikrotik Routerboard 532 button interface"
576 depends on MIKROTIK_RB532
580 Say Y here if you want support for the S1 button built into
581 Mikrotik's Routerboard 532.
583 To compile this driver as a module, choose M here: the
584 module will be called rb532_button.
586 config INPUT_DA9052_ONKEY
587 tristate "Dialog DA9052/DA9053 Onkey"
588 depends on PMIC_DA9052
590 Support the ONKEY of Dialog DA9052 PMICs as an input device
591 reporting power button status.
593 To compile this driver as a module, choose M here: the
594 module will be called da9052_onkey.
596 config INPUT_DA9055_ONKEY
597 tristate "Dialog Semiconductor DA9055 ONKEY"
598 depends on MFD_DA9055
600 Support the ONKEY of DA9055 PMICs as an input device
601 reporting power button status.
603 To compile this driver as a module, choose M here: the module
604 will be called da9055_onkey.
606 config INPUT_DA9063_ONKEY
607 tristate "Dialog DA9062/63 OnKey"
608 depends on MFD_DA9063 || MFD_DA9062
610 Support the ONKEY of Dialog DA9063 and DA9062 Power Management ICs
611 as an input device capable of reporting the power button status.
613 To compile this driver as a module, choose M here: the module
614 will be called da9063_onkey.
616 config INPUT_DM355EVM
617 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
618 depends on MFD_DM355EVM_MSP
619 select INPUT_SPARSEKMAP
621 Supports the pushbuttons and IR remote used with
624 To compile this driver as a module, choose M here: the
625 module will be called dm355evm_keys.
627 config INPUT_BFIN_ROTARY
628 tristate "Blackfin Rotary support"
629 depends on BF54x || BF52x
631 Say Y here if you want to use the Blackfin Rotary.
633 To compile this driver as a module, choose M here: the
634 module will be called bfin-rotary.
636 config INPUT_WM831X_ON
637 tristate "WM831X ON pin"
638 depends on MFD_WM831X
640 Support the ON pin of WM831X 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 wm831x_on.
647 tristate "Motorola EZX PCAP misc input events"
650 Say Y here if you want to use Power key and Headphone button
651 on Motorola EZX phones.
653 To compile this driver as a module, choose M here: the
654 module will be called pcap_keys.
657 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
660 Say Y here if you have a Accelerometer interface using the
661 ADXL345/6 controller, and your board-specific initialization
662 code includes that in its table of devices.
664 This driver can use either I2C or SPI communication to the
665 ADXL345/6 controller. Select the appropriate method for
668 If unsure, say N (but it's safe to say "Y").
670 To compile this driver as a module, choose M here: the
671 module will be called adxl34x.
673 config INPUT_ADXL34X_I2C
674 tristate "support I2C bus connection"
675 depends on INPUT_ADXL34X && I2C
678 Say Y here if you have ADXL345/6 hooked to an I2C bus.
680 To compile this driver as a module, choose M here: the
681 module will be called adxl34x-i2c.
683 config INPUT_ADXL34X_SPI
684 tristate "support SPI bus connection"
685 depends on INPUT_ADXL34X && SPI
688 Say Y here if you have ADXL345/6 hooked to a SPI bus.
690 To compile this driver as a module, choose M here: the
691 module will be called adxl34x-spi.
694 tristate "IMS Passenger Control Unit driver"
696 depends on LEDS_CLASS
698 Say Y here if you have system with IMS Rave Passenger Control Unit.
700 To compile this driver as a module, choose M here: the module will be
704 tristate "VTI CMA3000 Tri-axis accelerometer"
706 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
709 This driver currently only supports I2C interface to the
710 controller. Also select the I2C method.
714 To compile this driver as a module, choose M here: the
715 module will be called cma3000_d0x.
717 config INPUT_CMA3000_I2C
718 tristate "Support I2C bus connection"
719 depends on INPUT_CMA3000 && I2C
721 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
722 through I2C interface.
724 To compile this driver as a module, choose M here: the
725 module will be called cma3000_d0x_i2c.
727 config INPUT_XEN_KBDDEV_FRONTEND
728 tristate "Xen virtual keyboard and mouse support"
731 select XEN_XENBUS_FRONTEND
733 This driver implements the front-end of the Xen virtual
734 keyboard and mouse device driver. It communicates with a back-end
737 To compile this driver as a module, choose M here: the
738 module will be called xen-kbdfront.
740 config INPUT_SIRFSOC_ONKEY
741 bool "CSR SiRFSoC power on/off/suspend key support"
742 depends on ARCH_SIRF && OF
745 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
746 in Linux, after you press the onkey, system will suspend.
750 config INPUT_IDEAPAD_SLIDEBAR
751 tristate "IdeaPad Laptop Slidebar"
753 depends on SERIO_I8042
755 Say Y here if you have an IdeaPad laptop with a slidebar.
757 To compile this driver as a module, choose M here: the
758 module will be called ideapad_slidebar.
760 config INPUT_SOC_BUTTON_ARRAY
761 tristate "Windows-compatible SoC Button Array"
762 depends on KEYBOARD_GPIO
764 Say Y here if you have a SoC-based tablet that originally
767 To compile this driver as a module, choose M here: the
768 module will be called soc_button_array.
770 config INPUT_DRV260X_HAPTICS
771 tristate "TI DRV260X haptics support"
772 depends on INPUT && I2C
773 depends on GPIOLIB || COMPILE_TEST
774 select INPUT_FF_MEMLESS
777 Say Y to enable support for the TI DRV260X haptics driver.
779 To compile this driver as a module, choose M here: the
780 module will be called drv260x-haptics.
782 config INPUT_DRV2665_HAPTICS
783 tristate "TI DRV2665 haptics support"
784 depends on INPUT && I2C
785 select INPUT_FF_MEMLESS
788 Say Y to enable support for the TI DRV2665 haptics driver.
790 To compile this driver as a module, choose M here: the
791 module will be called drv2665-haptics.
793 config INPUT_DRV2667_HAPTICS
794 tristate "TI DRV2667 haptics support"
795 depends on INPUT && I2C
796 select INPUT_FF_MEMLESS
799 Say Y to enable support for the TI DRV2667 haptics driver.
801 To compile this driver as a module, choose M here: the
802 module will be called drv2667-haptics.