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 E3x0 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_PM8XXX_VIBRATOR
119 tristate "Qualcomm PM8XXX vibrator support"
120 depends on MFD_PM8XXX
121 select INPUT_FF_MEMLESS
123 This option enables device driver support for the vibrator
124 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
125 from input framework.
127 To compile this driver as module, choose M here: the
128 module will be called pm8xxx-vibrator.
130 config INPUT_PMIC8XXX_PWRKEY
131 tristate "PMIC8XXX power key support"
132 depends on MFD_PM8XXX
134 Say Y here if you want support for the PMIC8XXX power key.
138 To compile this driver as a module, choose M here: the
139 module will be called pmic8xxx-pwrkey.
141 config INPUT_SPARCSPKR
142 tristate "SPARC Speaker support"
143 depends on PCI && SPARC64
145 Say Y here if you want the standard Speaker on Sparc PCI systems
146 to be used for bells and whistles.
150 To compile this driver as a module, choose M here: the
151 module will be called sparcspkr.
153 config INPUT_M68K_BEEP
154 tristate "M68k Beeper support"
157 config INPUT_MAX77693_HAPTIC
158 tristate "MAXIM MAX77693 haptic controller support"
159 depends on MFD_MAX77693 && PWM
160 select INPUT_FF_MEMLESS
162 This option enables support for the haptic controller on
165 To compile this driver as module, choose M here: the
166 module will be called max77693-haptic.
168 config INPUT_MAX8925_ONKEY
169 tristate "MAX8925 ONKEY support"
170 depends on MFD_MAX8925
172 Support the ONKEY of MAX8925 PMICs as an input device
173 reporting power button status.
175 To compile this driver as a module, choose M here: the module
176 will be called max8925_onkey.
178 config INPUT_MAX8997_HAPTIC
179 tristate "MAXIM MAX8997 haptic controller support"
180 depends on PWM && MFD_MAX8997
181 select INPUT_FF_MEMLESS
183 This option enables device driver support for the haptic controller
184 on MAXIM MAX8997 chip. This driver supports ff-memless interface
185 from input framework.
187 To compile this driver as module, choose M here: the
188 module will be called max8997-haptic.
190 config INPUT_MC13783_PWRBUTTON
191 tristate "MC13783 ON buttons"
192 depends on MFD_MC13XXX
194 Support the ON buttons of MC13783 PMIC as an input device
195 reporting power button status.
197 To compile this driver as a module, choose M here: the module
198 will be called mc13783-pwrbutton.
201 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
205 Say Y here if you want to support Freescale's MMA8450 Accelerometer
206 through I2C interface.
208 To compile this driver as a module, choose M here: the
209 module will be called mma8450.
212 tristate "MPU3050 Triaxial gyroscope sensor"
215 Say Y here if you want to support InvenSense MPU3050
216 connected via an I2C bus.
218 To compile this driver as a module, choose M here: the
219 module will be called mpu3050.
222 tristate "Fujitsu Lifebook Application Panel buttons"
223 depends on X86 && I2C && LEDS_CLASS
225 select CHECK_SIGNATURE
227 Say Y here for support of the Application Panel buttons, used on
228 Fujitsu Lifebook. These are attached to the mainboard through
229 an SMBus interface managed by the I2C Intel ICH (i801) driver,
230 which you should also build for this kernel.
232 To compile this driver as a module, choose M here: the module will
236 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
240 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
241 hooked to an I2C bus.
243 To compile this driver as a module, choose M here: the
244 module will be called gp2ap002a00f.
246 config INPUT_GPIO_BEEPER
247 tristate "Generic GPIO Beeper support"
250 Say Y here if you have a beeper connected to a GPIO pin.
252 To compile this driver as a module, choose M here: the
253 module will be called gpio-beeper.
255 config INPUT_GPIO_TILT_POLLED
256 tristate "Polled GPIO tilt switch"
260 This driver implements support for tilt switches connected
261 to GPIO pins that are not capable of generating interrupts.
263 The list of gpios to use and the mapping of their states
264 to specific angles is done via platform data.
266 To compile this driver as a module, choose M here: the
267 module will be called gpio_tilt_polled.
269 config INPUT_IXP4XX_BEEPER
270 tristate "IXP4XX Beeper support"
271 depends on ARCH_IXP4XX
273 If you say yes here, you can connect a beeper to the
274 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
278 To compile this driver as a module, choose M here: the
279 module will be called ixp4xx-beeper.
281 config INPUT_COBALT_BTNS
282 tristate "Cobalt button interface"
283 depends on MIPS_COBALT
286 Say Y here if you want to support MIPS Cobalt button interface.
288 To compile this driver as a module, choose M here: the
289 module will be called cobalt_btns.
291 config INPUT_WISTRON_BTNS
292 tristate "x86 Wistron laptop button interface"
295 select INPUT_SPARSEKMAP
298 select CHECK_SIGNATURE
300 Say Y here for support of Wistron laptop button interfaces, used on
301 laptops of various brands, including Acer and Fujitsu-Siemens. If
302 available, mail and wifi LEDs will be controllable via /sys/class/leds.
304 To compile this driver as a module, choose M here: the module will
305 be called wistron_btns.
307 config INPUT_ATLAS_BTNS
308 tristate "x86 Atlas button interface"
309 depends on X86 && ACPI
311 Say Y here for support of Atlas wallmount touchscreen buttons.
312 The events will show up as scancodes F1 through F9 via evdev.
314 To compile this driver as a module, choose M here: the module will
315 be called atlas_btns.
317 config INPUT_ATI_REMOTE2
318 tristate "ATI / Philips USB RF remote control"
319 depends on USB_ARCH_HAS_HCD
322 Say Y here if you want to use an ATI or Philips USB RF remote control.
323 These are RF remotes with USB receivers.
324 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
325 and is also available as a separate product.
326 This driver provides mouse pointer, left and right mouse buttons,
327 and maps all the other remote buttons to keypress events.
329 To compile this driver as a module, choose M here: the module will be
332 config INPUT_KEYSPAN_REMOTE
333 tristate "Keyspan DMR USB remote control"
334 depends on USB_ARCH_HAS_HCD
337 Say Y here if you want to use a Keyspan DMR USB remote control.
338 Currently only the UIA-11 type of receiver has been tested. The tag
339 on the receiver that connects to the USB port should have a P/N that
340 will tell you what type of DMR you have. The UIA-10 type is not
341 supported at this time. This driver maps all buttons to keypress
344 To compile this driver as a module, choose M here: the module will
345 be called keyspan_remote.
348 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
351 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
354 To compile this driver as a module, choose M here: the module will
357 config INPUT_KXTJ9_POLLED_MODE
358 bool "Enable polling mode support"
359 depends on INPUT_KXTJ9
362 Say Y here if you need accelerometer to work in polling mode.
364 config INPUT_POWERMATE
365 tristate "Griffin PowerMate and Contour Jog support"
366 depends on USB_ARCH_HAS_HCD
369 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
370 These are aluminum dials which can measure clockwise and anticlockwise
371 rotation. The dial also acts as a pushbutton. The base contains an LED
372 which can be instructed to pulse or to switch to a particular intensity.
374 You can download userspace tools from
375 <http://sowerbutts.com/powermate/>.
377 To compile this driver as a module, choose M here: the
378 module will be called powermate.
381 tristate "Yealink usb-p1k voip phone"
382 depends on USB_ARCH_HAS_HCD
385 Say Y here if you want to enable keyboard and LCD functions of the
386 Yealink usb-p1k usb phones. The audio part is enabled by the generic
387 usb sound driver, so you might want to enable that as well.
389 For information about how to use these additional functions, see
390 <file:Documentation/input/yealink.txt>.
392 To compile this driver as a module, choose M here: the module will be
396 tristate "C-Media CM109 USB I/O Controller"
397 depends on USB_ARCH_HAS_HCD
400 Say Y here if you want to enable keyboard and buzzer functions of the
401 C-Media CM109 usb phones. The audio part is enabled by the generic
402 usb sound driver, so you might want to enable that as well.
404 To compile this driver as a module, choose M here: the module will be
407 config INPUT_REGULATOR_HAPTIC
408 tristate "Regulator haptics support"
410 select INPUT_FF_MEMLESS
412 This option enables device driver support for the haptic controlled
413 by a regulator. This driver supports ff-memless interface
414 from input framework.
416 To compile this driver as a module, choose M here: the
417 module will be called regulator-haptic.
419 config INPUT_RETU_PWRBUTTON
420 tristate "Retu Power button Driver"
423 Say Y here if you want to enable power key reporting via the
424 Retu chips found in Nokia Internet Tablets (770, N800, N810).
426 To compile this driver as a module, choose M here. The module will
427 be called retu-pwrbutton.
429 config INPUT_TPS65218_PWRBUTTON
430 tristate "TPS65218 Power button driver"
431 depends on MFD_TPS65218
433 Say Y here if you want to enable power buttong reporting for
434 the TPS65218 Power Management IC device.
436 To compile this driver as a module, choose M here. The module will
437 be called tps65218-pwrbutton.
439 config INPUT_AXP20X_PEK
440 tristate "X-Powers AXP20X power button driver"
441 depends on MFD_AXP20X
443 Say Y here if you want to enable power key reporting via the
446 To compile this driver as a module, choose M here. The module will
447 be called axp20x-pek.
450 config INPUT_TWL4030_PWRBUTTON
451 tristate "TWL4030 Power button Driver"
452 depends on TWL4030_CORE
454 Say Y here if you want to enable power key reporting via the
455 TWL4030 family of chips.
457 To compile this driver as a module, choose M here. The module will
458 be called twl4030_pwrbutton.
460 config INPUT_TWL4030_VIBRA
461 tristate "Support for TWL4030 Vibrator"
462 depends on TWL4030_CORE
463 select MFD_TWL4030_AUDIO
464 select INPUT_FF_MEMLESS
466 This option enables support for TWL4030 Vibrator Driver.
468 To compile this driver as a module, choose M here. The module will
469 be called twl4030_vibra.
471 config INPUT_TWL6040_VIBRA
472 tristate "Support for TWL6040 Vibrator"
473 depends on TWL6040_CORE
474 select INPUT_FF_MEMLESS
476 This option enables support for TWL6040 Vibrator Driver.
478 To compile this driver as a module, choose M here. The module will
479 be called twl6040_vibra.
482 tristate "User level driver support"
484 Say Y here if you want to support user level drivers for input
485 subsystem accessible under char device 10:223 - /dev/input/uinput.
487 To compile this driver as a module, choose M here: the
488 module will be called uinput.
490 config INPUT_SGI_BTNS
491 tristate "SGI Indy/O2 volume button interface"
492 depends on SGI_IP22 || SGI_IP32
495 Say Y here if you want to support SGI Indy/O2 volume button interface.
497 To compile this driver as a module, choose M here: the
498 module will be called sgi_btns.
501 tristate "HP SDC Real Time Clock"
502 depends on (GSC || HP300) && SERIO
505 Say Y here if you want to support the built-in real time clock
506 of the HP SDC controller.
508 config INPUT_PALMAS_PWRBUTTON
509 tristate "Palmas Power button Driver"
510 depends on MFD_PALMAS
512 Say Y here if you want to enable power key reporting via the
513 Palmas family of PMICs.
515 To compile this driver as a module, choose M here. The module will
516 be called palmas_pwrbutton.
518 config INPUT_PCF50633_PMU
519 tristate "PCF50633 PMU events"
520 depends on MFD_PCF50633
522 Say Y to include support for delivering PMU events via input
523 layer on NXP PCF50633.
526 tristate "PCF8574 Keypad input device"
529 Say Y here if you want to support a keypad connected via I2C
532 To compile this driver as a module, choose M here: the
533 module will be called pcf8574_keypad.
535 config INPUT_PWM_BEEPER
536 tristate "PWM beeper support"
539 Say Y here to get support for PWM based beeper devices.
543 To compile this driver as a module, choose M here: the module will be
546 config INPUT_GPIO_ROTARY_ENCODER
547 tristate "Rotary encoders connected to GPIO pins"
550 Say Y here to add support for rotary encoders connected to GPIO lines.
551 Check file:Documentation/input/rotary-encoder.txt for more
554 To compile this driver as a module, choose M here: the
555 module will be called rotary_encoder.
557 config INPUT_RB532_BUTTON
558 tristate "Mikrotik Routerboard 532 button interface"
559 depends on MIKROTIK_RB532
563 Say Y here if you want support for the S1 button built into
564 Mikrotik's Routerboard 532.
566 To compile this driver as a module, choose M here: the
567 module will be called rb532_button.
569 config INPUT_DA9052_ONKEY
570 tristate "Dialog DA9052/DA9053 Onkey"
571 depends on PMIC_DA9052
573 Support the ONKEY of Dialog DA9052 PMICs as an input device
574 reporting power button status.
576 To compile this driver as a module, choose M here: the
577 module will be called da9052_onkey.
579 config INPUT_DA9055_ONKEY
580 tristate "Dialog Semiconductor DA9055 ONKEY"
581 depends on MFD_DA9055
583 Support the ONKEY of DA9055 PMICs as an input device
584 reporting power button status.
586 To compile this driver as a module, choose M here: the module
587 will be called da9055_onkey.
589 config INPUT_DM355EVM
590 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
591 depends on MFD_DM355EVM_MSP
592 select INPUT_SPARSEKMAP
594 Supports the pushbuttons and IR remote used with
597 To compile this driver as a module, choose M here: the
598 module will be called dm355evm_keys.
600 config INPUT_BFIN_ROTARY
601 tristate "Blackfin Rotary support"
602 depends on BF54x || BF52x
604 Say Y here if you want to use the Blackfin Rotary.
606 To compile this driver as a module, choose M here: the
607 module will be called bfin-rotary.
609 config INPUT_WM831X_ON
610 tristate "WM831X ON pin"
611 depends on MFD_WM831X
613 Support the ON pin of WM831X PMICs as an input device
614 reporting power button status.
616 To compile this driver as a module, choose M here: the module
617 will be called wm831x_on.
620 tristate "Motorola EZX PCAP misc input events"
623 Say Y here if you want to use Power key and Headphone button
624 on Motorola EZX phones.
626 To compile this driver as a module, choose M here: the
627 module will be called pcap_keys.
630 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
633 Say Y here if you have a Accelerometer interface using the
634 ADXL345/6 controller, and your board-specific initialization
635 code includes that in its table of devices.
637 This driver can use either I2C or SPI communication to the
638 ADXL345/6 controller. Select the appropriate method for
641 If unsure, say N (but it's safe to say "Y").
643 To compile this driver as a module, choose M here: the
644 module will be called adxl34x.
646 config INPUT_ADXL34X_I2C
647 tristate "support I2C bus connection"
648 depends on INPUT_ADXL34X && I2C
651 Say Y here if you have ADXL345/6 hooked to an I2C bus.
653 To compile this driver as a module, choose M here: the
654 module will be called adxl34x-i2c.
656 config INPUT_ADXL34X_SPI
657 tristate "support SPI bus connection"
658 depends on INPUT_ADXL34X && SPI
661 Say Y here if you have ADXL345/6 hooked to a SPI bus.
663 To compile this driver as a module, choose M here: the
664 module will be called adxl34x-spi.
667 tristate "IMS Passenger Control Unit driver"
669 depends on LEDS_CLASS
671 Say Y here if you have system with IMS Rave Passenger Control Unit.
673 To compile this driver as a module, choose M here: the module will be
677 tristate "VTI CMA3000 Tri-axis accelerometer"
679 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
682 This driver currently only supports I2C interface to the
683 controller. Also select the I2C method.
687 To compile this driver as a module, choose M here: the
688 module will be called cma3000_d0x.
690 config INPUT_CMA3000_I2C
691 tristate "Support I2C bus connection"
692 depends on INPUT_CMA3000 && I2C
694 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
695 through I2C interface.
697 To compile this driver as a module, choose M here: the
698 module will be called cma3000_d0x_i2c.
700 config INPUT_XEN_KBDDEV_FRONTEND
701 tristate "Xen virtual keyboard and mouse support"
704 select XEN_XENBUS_FRONTEND
706 This driver implements the front-end of the Xen virtual
707 keyboard and mouse device driver. It communicates with a back-end
710 To compile this driver as a module, choose M here: the
711 module will be called xen-kbdfront.
713 config INPUT_SIRFSOC_ONKEY
714 bool "CSR SiRFSoC power on/off/suspend key support"
715 depends on ARCH_SIRF && OF
718 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
719 in Linux, after you press the onkey, system will suspend.
723 config INPUT_IDEAPAD_SLIDEBAR
724 tristate "IdeaPad Laptop Slidebar"
726 depends on SERIO_I8042
728 Say Y here if you have an IdeaPad laptop with a slidebar.
730 To compile this driver as a module, choose M here: the
731 module will be called ideapad_slidebar.
733 config INPUT_SOC_BUTTON_ARRAY
734 tristate "Windows-compatible SoC Button Array"
735 depends on KEYBOARD_GPIO
737 Say Y here if you have a SoC-based tablet that originally
740 To compile this driver as a module, choose M here: the
741 module will be called soc_button_array.
743 config INPUT_DRV260X_HAPTICS
744 tristate "TI DRV260X haptics support"
745 depends on INPUT && I2C && GPIOLIB
746 select INPUT_FF_MEMLESS
749 Say Y to enable support for the TI DRV260X haptics driver.
751 To compile this driver as a module, choose M here: the
752 module will be called drv260x-haptics.
754 config INPUT_DRV2667_HAPTICS
755 tristate "TI DRV2667 haptics support"
756 depends on INPUT && I2C
757 select INPUT_FF_MEMLESS
760 Say Y to enable support for the TI DRV2667 haptics driver.
762 To compile this driver as a module, choose M here: the
763 module will be called drv260x-haptics.