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_TWL4030_VIBRA
409 tristate "Support for TWL4030 Vibrator"
410 depends on TWL4030_CORE
411 select MFD_TWL4030_AUDIO
412 select INPUT_FF_MEMLESS
414 This option enables support for TWL4030 Vibrator Driver.
416 To compile this driver as a module, choose M here. The module will
417 be called twl4030_vibra.
419 config INPUT_TWL6040_VIBRA
420 tristate "Support for TWL6040 Vibrator"
421 depends on TWL6040_CORE
422 select INPUT_FF_MEMLESS
424 This option enables support for TWL6040 Vibrator Driver.
426 To compile this driver as a module, choose M here. The module will
427 be called twl6040_vibra.
430 tristate "User level driver support"
432 Say Y here if you want to support user level drivers for input
433 subsystem accessible under char device 10:223 - /dev/input/uinput.
435 To compile this driver as a module, choose M here: the
436 module will be called uinput.
438 config INPUT_SGI_BTNS
439 tristate "SGI Indy/O2 volume button interface"
440 depends on SGI_IP22 || SGI_IP32
443 Say Y here if you want to support SGI Indy/O2 volume button interface.
445 To compile this driver as a module, choose M here: the
446 module will be called sgi_btns.
449 tristate "GPIO driver support"
451 Say Y here if you want to support gpio based keys, wheels etc...
454 tristate "HP SDC Real Time Clock"
455 depends on (GSC || HP300) && SERIO
458 Say Y here if you want to support the built-in real time clock
459 of the HP SDC controller.
461 config INPUT_PCF50633_PMU
462 tristate "PCF50633 PMU events"
463 depends on MFD_PCF50633
465 Say Y to include support for delivering PMU events via input
466 layer on NXP PCF50633.
469 tristate "PCF8574 Keypad input device"
472 Say Y here if you want to support a keypad connected via I2C
475 To compile this driver as a module, choose M here: the
476 module will be called pcf8574_keypad.
478 config INPUT_PWM_BEEPER
479 tristate "PWM beeper support"
480 depends on HAVE_PWM || PWM
482 Say Y here to get support for PWM based beeper devices.
486 To compile this driver as a module, choose M here: the module will be
489 config INPUT_GPIO_ROTARY_ENCODER
490 tristate "Rotary encoders connected to GPIO pins"
493 Say Y here to add support for rotary encoders connected to GPIO lines.
494 Check file:Documentation/input/rotary-encoder.txt for more
497 To compile this driver as a module, choose M here: the
498 module will be called rotary_encoder.
500 config INPUT_RB532_BUTTON
501 tristate "Mikrotik Routerboard 532 button interface"
502 depends on MIKROTIK_RB532
506 Say Y here if you want support for the S1 button built into
507 Mikrotik's Routerboard 532.
509 To compile this driver as a module, choose M here: the
510 module will be called rb532_button.
512 config INPUT_DA9052_ONKEY
513 tristate "Dialog DA9052/DA9053 Onkey"
514 depends on PMIC_DA9052
516 Support the ONKEY of Dialog DA9052 PMICs as an input device
517 reporting power button status.
519 To compile this driver as a module, choose M here: the
520 module will be called da9052_onkey.
522 config INPUT_DA9055_ONKEY
523 tristate "Dialog Semiconductor DA9055 ONKEY"
524 depends on MFD_DA9055
526 Support the ONKEY of DA9055 PMICs as an input device
527 reporting power button status.
529 To compile this driver as a module, choose M here: the module
530 will be called da9055_onkey.
532 config INPUT_DM355EVM
533 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
534 depends on MFD_DM355EVM_MSP
535 select INPUT_SPARSEKMAP
537 Supports the pushbuttons and IR remote used with
540 To compile this driver as a module, choose M here: the
541 module will be called dm355evm_keys.
543 config INPUT_BFIN_ROTARY
544 tristate "Blackfin Rotary support"
545 depends on BF54x || BF52x
547 Say Y here if you want to use the Blackfin Rotary.
549 To compile this driver as a module, choose M here: the
550 module will be called bfin-rotary.
552 config INPUT_WM831X_ON
553 tristate "WM831X ON pin"
554 depends on MFD_WM831X
556 Support the ON pin of WM831X PMICs as an input device
557 reporting power button status.
559 To compile this driver as a module, choose M here: the module
560 will be called wm831x_on.
563 tristate "Motorola EZX PCAP misc input events"
566 Say Y here if you want to use Power key and Headphone button
567 on Motorola EZX phones.
569 To compile this driver as a module, choose M here: the
570 module will be called pcap_keys.
573 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
576 Say Y here if you have a Accelerometer interface using the
577 ADXL345/6 controller, and your board-specific initialization
578 code includes that in its table of devices.
580 This driver can use either I2C or SPI communication to the
581 ADXL345/6 controller. Select the appropriate method for
584 If unsure, say N (but it's safe to say "Y").
586 To compile this driver as a module, choose M here: the
587 module will be called adxl34x.
589 config INPUT_ADXL34X_I2C
590 tristate "support I2C bus connection"
591 depends on INPUT_ADXL34X && I2C
594 Say Y here if you have ADXL345/6 hooked to an I2C bus.
596 To compile this driver as a module, choose M here: the
597 module will be called adxl34x-i2c.
599 config INPUT_ADXL34X_SPI
600 tristate "support SPI bus connection"
601 depends on INPUT_ADXL34X && SPI
604 Say Y here if you have ADXL345/6 hooked to a SPI bus.
606 To compile this driver as a module, choose M here: the
607 module will be called adxl34x-spi.
610 tristate "IMS Passenger Control Unit driver"
612 depends on LEDS_CLASS
614 Say Y here if you have system with IMS Rave Passenger Control Unit.
616 To compile this driver as a module, choose M here: the module will be
620 tristate "VTI CMA3000 Tri-axis accelerometer"
622 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
625 This driver currently only supports I2C interface to the
626 controller. Also select the I2C method.
630 To compile this driver as a module, choose M here: the
631 module will be called cma3000_d0x.
633 config INPUT_CMA3000_I2C
634 tristate "Support I2C bus connection"
635 depends on INPUT_CMA3000 && I2C
637 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
638 through I2C interface.
640 To compile this driver as a module, choose M here: the
641 module will be called cma3000_d0x_i2c.
643 config INPUT_XEN_KBDDEV_FRONTEND
644 tristate "Xen virtual keyboard and mouse support"
647 select XEN_XENBUS_FRONTEND
649 This driver implements the front-end of the Xen virtual
650 keyboard and mouse device driver. It communicates with a back-end
653 To compile this driver as a module, choose M here: the
654 module will be called xen-kbdfront.