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.
97 tristate "PC Speaker support"
98 depends on PCSPKR_PLATFORM
100 Say Y here if you want the standard PC Speaker to be used for
105 To compile this driver as a module, choose M here: the
106 module will be called pcspkr.
108 config INPUT_PM8XXX_VIBRATOR
109 tristate "Qualcomm PM8XXX vibrator support"
110 depends on MFD_PM8XXX
111 select INPUT_FF_MEMLESS
113 This option enables device driver support for the vibrator
114 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
115 from input framework.
117 To compile this driver as module, choose M here: the
118 module will be called pm8xxx-vibrator.
120 config INPUT_PMIC8XXX_PWRKEY
121 tristate "PMIC8XXX power key support"
122 depends on MFD_PM8XXX
124 Say Y here if you want support for the PMIC8XXX power key.
128 To compile this driver as a module, choose M here: the
129 module will be called pmic8xxx-pwrkey.
131 config INPUT_SPARCSPKR
132 tristate "SPARC Speaker support"
133 depends on PCI && SPARC64
135 Say Y here if you want the standard Speaker on Sparc PCI systems
136 to be used for bells and whistles.
140 To compile this driver as a module, choose M here: the
141 module will be called sparcspkr.
143 config INPUT_M68K_BEEP
144 tristate "M68k Beeper support"
147 config INPUT_MAX8925_ONKEY
148 tristate "MAX8925 ONKEY support"
149 depends on MFD_MAX8925
151 Support the ONKEY of MAX8925 PMICs as an input device
152 reporting power button status.
154 To compile this driver as a module, choose M here: the module
155 will be called max8925_onkey.
157 config INPUT_MAX8997_HAPTIC
158 tristate "MAXIM MAX8997 haptic controller support"
159 depends on HAVE_PWM && MFD_MAX8997
160 select INPUT_FF_MEMLESS
162 This option enables device driver support for the haptic controller
163 on MAXIM MAX8997 chip. This driver supports ff-memless interface
164 from input framework.
166 To compile this driver as module, choose M here: the
167 module will be called max8997-haptic.
169 config INPUT_MC13783_PWRBUTTON
170 tristate "MC13783 ON buttons"
171 depends on MFD_MC13783
173 Support the ON buttons of MC13783 PMIC as an input device
174 reporting power button status.
176 To compile this driver as a module, choose M here: the module
177 will be called mc13783-pwrbutton.
180 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
184 Say Y here if you want to support Freescale's MMA8450 Accelerometer
185 through I2C interface.
187 To compile this driver as a module, choose M here: the
188 module will be called mma8450.
191 tristate "MPU3050 Triaxial gyroscope sensor"
194 Say Y here if you want to support InvenSense MPU3050
195 connected via an I2C bus.
197 To compile this driver as a module, choose M here: the
198 module will be called mpu3050.
201 tristate "Fujitsu Lifebook Application Panel buttons"
202 depends on X86 && I2C && LEDS_CLASS
204 select CHECK_SIGNATURE
206 Say Y here for support of the Application Panel buttons, used on
207 Fujitsu Lifebook. These are attached to the mainboard through
208 an SMBus interface managed by the I2C Intel ICH (i801) driver,
209 which you should also build for this kernel.
211 To compile this driver as a module, choose M here: the module will
215 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
219 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
220 hooked to an I2C bus.
222 To compile this driver as a module, choose M here: the
223 module will be called gp2ap002a00f.
225 config INPUT_GPIO_TILT_POLLED
226 tristate "Polled GPIO tilt switch"
230 This driver implements support for tilt switches connected
231 to GPIO pins that are not capable of generating interrupts.
233 The list of gpios to use and the mapping of their states
234 to specific angles is done via platform data.
236 To compile this driver as a module, choose M here: the
237 module will be called gpio_tilt_polled.
239 config INPUT_IXP4XX_BEEPER
240 tristate "IXP4XX Beeper support"
241 depends on ARCH_IXP4XX
243 If you say yes here, you can connect a beeper to the
244 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
248 To compile this driver as a module, choose M here: the
249 module will be called ixp4xx-beeper.
251 config INPUT_COBALT_BTNS
252 tristate "Cobalt button interface"
253 depends on MIPS_COBALT
256 Say Y here if you want to support MIPS Cobalt button interface.
258 To compile this driver as a module, choose M here: the
259 module will be called cobalt_btns.
261 config INPUT_WISTRON_BTNS
262 tristate "x86 Wistron laptop button interface"
263 depends on X86 && !X86_64
265 select INPUT_SPARSEKMAP
268 select CHECK_SIGNATURE
270 Say Y here for support of Wistron laptop button interfaces, used on
271 laptops of various brands, including Acer and Fujitsu-Siemens. If
272 available, mail and wifi LEDs will be controllable via /sys/class/leds.
274 To compile this driver as a module, choose M here: the module will
275 be called wistron_btns.
277 config INPUT_ATLAS_BTNS
278 tristate "x86 Atlas button interface"
279 depends on X86 && ACPI
281 Say Y here for support of Atlas wallmount touchscreen buttons.
282 The events will show up as scancodes F1 through F9 via evdev.
284 To compile this driver as a module, choose M here: the module will
285 be called atlas_btns.
287 config INPUT_ATI_REMOTE2
288 tristate "ATI / Philips USB RF remote control"
289 depends on USB_ARCH_HAS_HCD
292 Say Y here if you want to use an ATI or Philips USB RF remote control.
293 These are RF remotes with USB receivers.
294 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
295 and is also available as a separate product.
296 This driver provides mouse pointer, left and right mouse buttons,
297 and maps all the other remote buttons to keypress events.
299 To compile this driver as a module, choose M here: the module will be
302 config INPUT_KEYCHORD
303 tristate "Key chord input driver support"
305 Say Y here if you want to enable the key chord driver
306 accessible at /dev/keychord. This driver can be used
307 for receiving notifications when client specified key
308 combinations are pressed.
310 To compile this driver as a module, choose M here: the
311 module will be called keychord.
313 config INPUT_KEYSPAN_REMOTE
314 tristate "Keyspan DMR USB remote control"
315 depends on USB_ARCH_HAS_HCD
318 Say Y here if you want to use a Keyspan DMR USB remote control.
319 Currently only the UIA-11 type of receiver has been tested. The tag
320 on the receiver that connects to the USB port should have a P/N that
321 will tell you what type of DMR you have. The UIA-10 type is not
322 supported at this time. This driver maps all buttons to keypress
325 To compile this driver as a module, choose M here: the module will
326 be called keyspan_remote.
329 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
332 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
335 To compile this driver as a module, choose M here: the module will
338 config INPUT_KXTJ9_POLLED_MODE
339 bool "Enable polling mode support"
340 depends on INPUT_KXTJ9
343 Say Y here if you need accelerometer to work in polling mode.
345 config INPUT_POWERMATE
346 tristate "Griffin PowerMate and Contour Jog support"
347 depends on USB_ARCH_HAS_HCD
350 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
351 These are aluminum dials which can measure clockwise and anticlockwise
352 rotation. The dial also acts as a pushbutton. The base contains an LED
353 which can be instructed to pulse or to switch to a particular intensity.
355 You can download userspace tools from
356 <http://sowerbutts.com/powermate/>.
358 To compile this driver as a module, choose M here: the
359 module will be called powermate.
362 tristate "Yealink usb-p1k voip phone"
363 depends on USB_ARCH_HAS_HCD
366 Say Y here if you want to enable keyboard and LCD functions of the
367 Yealink usb-p1k usb phones. The audio part is enabled by the generic
368 usb sound driver, so you might want to enable that as well.
370 For information about how to use these additional functions, see
371 <file:Documentation/input/yealink.txt>.
373 To compile this driver as a module, choose M here: the module will be
377 tristate "C-Media CM109 USB I/O Controller"
378 depends on USB_ARCH_HAS_HCD
381 Say Y here if you want to enable keyboard and buzzer functions of the
382 C-Media CM109 usb phones. The audio part is enabled by the generic
383 usb sound driver, so you might want to enable that as well.
385 To compile this driver as a module, choose M here: the module will be
388 config INPUT_RETU_PWRBUTTON
389 tristate "Retu Power button Driver"
392 Say Y here if you want to enable power key reporting via the
393 Retu chips found in Nokia Internet Tablets (770, N800, N810).
395 To compile this driver as a module, choose M here. The module will
396 be called retu-pwrbutton.
398 config INPUT_TWL4030_PWRBUTTON
399 tristate "TWL4030 Power button Driver"
400 depends on TWL4030_CORE
402 Say Y here if you want to enable power key reporting via the
403 TWL4030 family of chips.
405 To compile this driver as a module, choose M here. The module will
406 be called twl4030_pwrbutton.
408 config INPUT_RICOH619_PWRKEY
409 tristate "RICOH RC5T619 PMU PWRKEY driver"
410 depends on MFD_RICOH619
413 If you say yes here you get support for the RICOH RC5T619 PWRKEY module.
415 This driver can also be built as a module. If so, the module
416 will be called rc5t619-pwrkey.
417 config INPUT_TWL4030_VIBRA
418 tristate "Support for TWL4030 Vibrator"
419 depends on TWL4030_CORE
420 select MFD_TWL4030_AUDIO
421 select INPUT_FF_MEMLESS
423 This option enables support for TWL4030 Vibrator Driver.
425 To compile this driver as a module, choose M here. The module will
426 be called twl4030_vibra.
428 config INPUT_TWL6040_VIBRA
429 tristate "Support for TWL6040 Vibrator"
430 depends on TWL6040_CORE
431 select INPUT_FF_MEMLESS
433 This option enables support for TWL6040 Vibrator Driver.
435 To compile this driver as a module, choose M here. The module will
436 be called twl6040_vibra.
439 tristate "User level driver support"
441 Say Y here if you want to support user level drivers for input
442 subsystem accessible under char device 10:223 - /dev/input/uinput.
444 To compile this driver as a module, choose M here: the
445 module will be called uinput.
447 config INPUT_SGI_BTNS
448 tristate "SGI Indy/O2 volume button interface"
449 depends on SGI_IP22 || SGI_IP32
452 Say Y here if you want to support SGI Indy/O2 volume button interface.
454 To compile this driver as a module, choose M here: the
455 module will be called sgi_btns.
458 tristate "GPIO driver support"
460 Say Y here if you want to support gpio based keys, wheels etc...
463 tristate "HP SDC Real Time Clock"
464 depends on (GSC || HP300) && SERIO
467 Say Y here if you want to support the built-in real time clock
468 of the HP SDC controller.
470 config INPUT_PCF50633_PMU
471 tristate "PCF50633 PMU events"
472 depends on MFD_PCF50633
474 Say Y to include support for delivering PMU events via input
475 layer on NXP PCF50633.
478 tristate "PCF8574 Keypad input device"
481 Say Y here if you want to support a keypad connected via I2C
484 To compile this driver as a module, choose M here: the
485 module will be called pcf8574_keypad.
487 config INPUT_PWM_BEEPER
488 tristate "PWM beeper support"
489 depends on HAVE_PWM || PWM
491 Say Y here to get support for PWM based beeper devices.
495 To compile this driver as a module, choose M here: the module will be
498 config INPUT_GPIO_ROTARY_ENCODER
499 tristate "Rotary encoders connected to GPIO pins"
502 Say Y here to add support for rotary encoders connected to GPIO lines.
503 Check file:Documentation/input/rotary-encoder.txt for more
506 To compile this driver as a module, choose M here: the
507 module will be called rotary_encoder.
509 config INPUT_RB532_BUTTON
510 tristate "Mikrotik Routerboard 532 button interface"
511 depends on MIKROTIK_RB532
515 Say Y here if you want support for the S1 button built into
516 Mikrotik's Routerboard 532.
518 To compile this driver as a module, choose M here: the
519 module will be called rb532_button.
521 config INPUT_DA9052_ONKEY
522 tristate "Dialog DA9052/DA9053 Onkey"
523 depends on PMIC_DA9052
525 Support the ONKEY of Dialog DA9052 PMICs as an input device
526 reporting power button status.
528 To compile this driver as a module, choose M here: the
529 module will be called da9052_onkey.
531 config INPUT_DA9055_ONKEY
532 tristate "Dialog Semiconductor DA9055 ONKEY"
533 depends on MFD_DA9055
535 Support the ONKEY of DA9055 PMICs as an input device
536 reporting power button status.
538 To compile this driver as a module, choose M here: the module
539 will be called da9055_onkey.
541 config INPUT_DM355EVM
542 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
543 depends on MFD_DM355EVM_MSP
544 select INPUT_SPARSEKMAP
546 Supports the pushbuttons and IR remote used with
549 To compile this driver as a module, choose M here: the
550 module will be called dm355evm_keys.
552 config INPUT_BFIN_ROTARY
553 tristate "Blackfin Rotary support"
554 depends on BF54x || BF52x
556 Say Y here if you want to use the Blackfin Rotary.
558 To compile this driver as a module, choose M here: the
559 module will be called bfin-rotary.
561 config INPUT_WM831X_ON
562 tristate "WM831X ON pin"
563 depends on MFD_WM831X
565 Support the ON pin of WM831X PMICs as an input device
566 reporting power button status.
568 To compile this driver as a module, choose M here: the module
569 will be called wm831x_on.
572 tristate "Motorola EZX PCAP misc input events"
575 Say Y here if you want to use Power key and Headphone button
576 on Motorola EZX phones.
578 To compile this driver as a module, choose M here: the
579 module will be called pcap_keys.
582 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
585 Say Y here if you have a Accelerometer interface using the
586 ADXL345/6 controller, and your board-specific initialization
587 code includes that in its table of devices.
589 This driver can use either I2C or SPI communication to the
590 ADXL345/6 controller. Select the appropriate method for
593 If unsure, say N (but it's safe to say "Y").
595 To compile this driver as a module, choose M here: the
596 module will be called adxl34x.
598 config INPUT_ADXL34X_I2C
599 tristate "support I2C bus connection"
600 depends on INPUT_ADXL34X && I2C
603 Say Y here if you have ADXL345/6 hooked to an I2C bus.
605 To compile this driver as a module, choose M here: the
606 module will be called adxl34x-i2c.
608 config INPUT_ADXL34X_SPI
609 tristate "support SPI bus connection"
610 depends on INPUT_ADXL34X && SPI
613 Say Y here if you have ADXL345/6 hooked to a SPI bus.
615 To compile this driver as a module, choose M here: the
616 module will be called adxl34x-spi.
619 tristate "IMS Passenger Control Unit driver"
621 depends on LEDS_CLASS
623 Say Y here if you have system with IMS Rave Passenger Control Unit.
625 To compile this driver as a module, choose M here: the module will be
629 tristate "VTI CMA3000 Tri-axis accelerometer"
631 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
634 This driver currently only supports I2C interface to the
635 controller. Also select the I2C method.
639 To compile this driver as a module, choose M here: the
640 module will be called cma3000_d0x.
642 config INPUT_CMA3000_I2C
643 tristate "Support I2C bus connection"
644 depends on INPUT_CMA3000 && I2C
646 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
647 through I2C interface.
649 To compile this driver as a module, choose M here: the
650 module will be called cma3000_d0x_i2c.
652 config INPUT_XEN_KBDDEV_FRONTEND
653 tristate "Xen virtual keyboard and mouse support"
656 select XEN_XENBUS_FRONTEND
658 This driver implements the front-end of the Xen virtual
659 keyboard and mouse device driver. It communicates with a back-end
662 To compile this driver as a module, choose M here: the
663 module will be called xen-kbdfront.