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_AB8500_PONKEY
26 tristate "AB8500 Pon (PowerOn) Key"
27 depends on AB8500_CORE
29 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
32 To compile this driver as a module, choose M here: the module
33 will be called ab8500-ponkey.
36 tristate "Analog Devices AD714x Capacitance Touch Sensor"
38 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
40 You should select a bus connection too.
42 To compile this driver as a module, choose M here: the
43 module will be called ad714x.
45 config INPUT_AD714X_I2C
46 tristate "support I2C bus connection"
47 depends on INPUT_AD714X && I2C
50 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
52 To compile this driver as a module, choose M here: the
53 module will be called ad714x-i2c.
55 config INPUT_AD714X_SPI
56 tristate "support SPI bus connection"
57 depends on INPUT_AD714X && SPI
60 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
62 To compile this driver as a module, choose M here: the
63 module will be called ad714x-spi.
66 tristate "BMA150/SMB380 acceleration sensor support"
70 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
71 acceleration sensor hooked to an I2C bus.
73 To compile this driver as a module, choose M here: the
74 module will be called bma150.
77 tristate "PC Speaker support"
78 depends on PCSPKR_PLATFORM
80 Say Y here if you want the standard PC Speaker to be used for
85 To compile this driver as a module, choose M here: the
86 module will be called pcspkr.
88 config INPUT_PM8XXX_VIBRATOR
89 tristate "Qualcomm PM8XXX vibrator support"
91 select INPUT_FF_MEMLESS
93 This option enables device driver support for the vibrator
94 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
97 To compile this driver as module, choose M here: the
98 module will be called pm8xxx-vibrator.
100 config INPUT_PMIC8XXX_PWRKEY
101 tristate "PMIC8XXX power key support"
102 depends on MFD_PM8XXX
104 Say Y here if you want support for the PMIC8XXX power key.
108 To compile this driver as a module, choose M here: the
109 module will be called pmic8xxx-pwrkey.
111 config INPUT_SPARCSPKR
112 tristate "SPARC Speaker support"
113 depends on PCI && SPARC64
115 Say Y here if you want the standard Speaker on Sparc PCI systems
116 to be used for bells and whistles.
120 To compile this driver as a module, choose M here: the
121 module will be called sparcspkr.
123 config INPUT_M68K_BEEP
124 tristate "M68k Beeper support"
127 config INPUT_MAX8925_ONKEY
128 tristate "MAX8925 ONKEY support"
129 depends on MFD_MAX8925
131 Support the ONKEY of MAX8925 PMICs as an input device
132 reporting power button status.
134 To compile this driver as a module, choose M here: the module
135 will be called max8925_onkey.
137 config INPUT_MC13783_PWRBUTTON
138 tristate "MC13783 ON buttons"
139 depends on MFD_MC13783
141 Support the ON buttons of MC13783 PMIC as an input device
142 reporting power button status.
144 To compile this driver as a module, choose M here: the module
145 will be called mc13783-pwrbutton.
148 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
152 Say Y here if you want to support Freescale's MMA8450 Accelerometer
153 through I2C interface.
155 To compile this driver as a module, choose M here: the
156 module will be called mma8450.
159 tristate "MPU3050 Triaxial gyroscope sensor"
162 Say Y here if you want to support InvenSense MPU3050
163 connected via an I2C bus.
165 To compile this driver as a module, choose M here: the
166 module will be called mpu3050.
169 tristate "Fujitsu Lifebook Application Panel buttons"
170 depends on X86 && I2C && LEDS_CLASS
172 select CHECK_SIGNATURE
174 Say Y here for support of the Application Panel buttons, used on
175 Fujitsu Lifebook. These are attached to the mainboard through
176 an SMBus interface managed by the I2C Intel ICH (i801) driver,
177 which you should also build for this kernel.
179 To compile this driver as a module, choose M here: the module will
182 config INPUT_IXP4XX_BEEPER
183 tristate "IXP4XX Beeper support"
184 depends on ARCH_IXP4XX
186 If you say yes here, you can connect a beeper to the
187 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
191 To compile this driver as a module, choose M here: the
192 module will be called ixp4xx-beeper.
194 config INPUT_COBALT_BTNS
195 tristate "Cobalt button interface"
196 depends on MIPS_COBALT
199 Say Y here if you want to support MIPS Cobalt button interface.
201 To compile this driver as a module, choose M here: the
202 module will be called cobalt_btns.
204 config INPUT_WISTRON_BTNS
205 tristate "x86 Wistron laptop button interface"
206 depends on X86 && !X86_64
208 select INPUT_SPARSEKMAP
211 select CHECK_SIGNATURE
213 Say Y here for support of Wistron laptop button interfaces, used on
214 laptops of various brands, including Acer and Fujitsu-Siemens. If
215 available, mail and wifi LEDs will be controllable via /sys/class/leds.
217 To compile this driver as a module, choose M here: the module will
218 be called wistron_btns.
220 config INPUT_ATLAS_BTNS
221 tristate "x86 Atlas button interface"
222 depends on X86 && ACPI
224 Say Y here for support of Atlas wallmount touchscreen buttons.
225 The events will show up as scancodes F1 through F9 via evdev.
227 To compile this driver as a module, choose M here: the module will
228 be called atlas_btns.
230 config INPUT_ATI_REMOTE2
231 tristate "ATI / Philips USB RF remote control"
232 depends on USB_ARCH_HAS_HCD
235 Say Y here if you want to use an ATI or Philips USB RF remote control.
236 These are RF remotes with USB receivers.
237 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
238 and is also available as a separate product.
239 This driver provides mouse pointer, left and right mouse buttons,
240 and maps all the other remote buttons to keypress events.
242 To compile this driver as a module, choose M here: the module will be
245 config INPUT_KEYSPAN_REMOTE
246 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
247 depends on EXPERIMENTAL
248 depends on USB_ARCH_HAS_HCD
251 Say Y here if you want to use a Keyspan DMR USB remote control.
252 Currently only the UIA-11 type of receiver has been tested. The tag
253 on the receiver that connects to the USB port should have a P/N that
254 will tell you what type of DMR you have. The UIA-10 type is not
255 supported at this time. This driver maps all buttons to keypress
258 To compile this driver as a module, choose M here: the module will
259 be called keyspan_remote.
262 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
265 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
268 To compile this driver as a module, choose M here: the module will
271 config INPUT_KXTJ9_POLLED_MODE
272 bool "Enable polling mode support"
273 depends on INPUT_KXTJ9
276 Say Y here if you need accelerometer to work in polling mode.
278 config INPUT_POWERMATE
279 tristate "Griffin PowerMate and Contour Jog support"
280 depends on USB_ARCH_HAS_HCD
283 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
284 These are aluminum dials which can measure clockwise and anticlockwise
285 rotation. The dial also acts as a pushbutton. The base contains an LED
286 which can be instructed to pulse or to switch to a particular intensity.
288 You can download userspace tools from
289 <http://sowerbutts.com/powermate/>.
291 To compile this driver as a module, choose M here: the
292 module will be called powermate.
295 tristate "Yealink usb-p1k voip phone"
296 depends on EXPERIMENTAL
297 depends on USB_ARCH_HAS_HCD
300 Say Y here if you want to enable keyboard and LCD functions of the
301 Yealink usb-p1k usb phones. The audio part is enabled by the generic
302 usb sound driver, so you might want to enable that as well.
304 For information about how to use these additional functions, see
305 <file:Documentation/input/yealink.txt>.
307 To compile this driver as a module, choose M here: the module will be
311 tristate "C-Media CM109 USB I/O Controller"
312 depends on EXPERIMENTAL
313 depends on USB_ARCH_HAS_HCD
316 Say Y here if you want to enable keyboard and buzzer functions of the
317 C-Media CM109 usb phones. The audio part is enabled by the generic
318 usb sound driver, so you might want to enable that as well.
320 To compile this driver as a module, choose M here: the module will be
323 config INPUT_TWL4030_PWRBUTTON
324 tristate "TWL4030 Power button Driver"
325 depends on TWL4030_CORE
327 Say Y here if you want to enable power key reporting via the
328 TWL4030 family of chips.
330 To compile this driver as a module, choose M here. The module will
331 be called twl4030_pwrbutton.
333 config INPUT_TWL4030_VIBRA
334 tristate "Support for TWL4030 Vibrator"
335 depends on TWL4030_CORE
336 select MFD_TWL4030_AUDIO
337 select INPUT_FF_MEMLESS
339 This option enables support for TWL4030 Vibrator Driver.
341 To compile this driver as a module, choose M here. The module will
342 be called twl4030_vibra.
344 config INPUT_TWL6040_VIBRA
345 tristate "Support for TWL6040 Vibrator"
346 depends on TWL4030_CORE
348 select INPUT_FF_MEMLESS
350 This option enables support for TWL6040 Vibrator Driver.
352 To compile this driver as a module, choose M here. The module will
353 be called twl6040_vibra.
356 tristate "VSense Navigation Device"
359 Say Y here if you want to support VSense navigation device
360 (the analog nub on pandora handheld).
362 To compile this driver as a module, choose M here: the
363 module will be called vsense.
366 tristate "User level driver support"
368 Say Y here if you want to support user level drivers for input
369 subsystem accessible under char device 10:223 - /dev/input/uinput.
371 To compile this driver as a module, choose M here: the
372 module will be called uinput.
374 config INPUT_SGI_BTNS
375 tristate "SGI Indy/O2 volume button interface"
376 depends on SGI_IP22 || SGI_IP32
379 Say Y here if you want to support SGI Indy/O2 volume button interface.
381 To compile this driver as a module, choose M here: the
382 module will be called sgi_btns.
385 tristate "HP SDC Real Time Clock"
386 depends on (GSC || HP300) && SERIO
389 Say Y here if you want to support the built-in real time clock
390 of the HP SDC controller.
392 config INPUT_PCF50633_PMU
393 tristate "PCF50633 PMU events"
394 depends on MFD_PCF50633
396 Say Y to include support for delivering PMU events via input
397 layer on NXP PCF50633.
400 tristate "PCF8574 Keypad input device"
401 depends on I2C && EXPERIMENTAL
403 Say Y here if you want to support a keypad connetced via I2C
406 To compile this driver as a module, choose M here: the
407 module will be called pcf8574_keypad.
409 config INPUT_PWM_BEEPER
410 tristate "PWM beeper support"
413 Say Y here to get support for PWM based beeper devices.
417 To compile this driver as a module, choose M here: the module will be
420 config INPUT_GPIO_ROTARY_ENCODER
421 tristate "Rotary encoders connected to GPIO pins"
422 depends on GPIOLIB && GENERIC_GPIO
424 Say Y here to add support for rotary encoders connected to GPIO lines.
425 Check file:Documentation/input/rotary-encoder.txt for more
428 To compile this driver as a module, choose M here: the
429 module will be called rotary_encoder.
431 config INPUT_RB532_BUTTON
432 tristate "Mikrotik Routerboard 532 button interface"
433 depends on MIKROTIK_RB532
434 depends on GPIOLIB && GENERIC_GPIO
437 Say Y here if you want support for the S1 button built into
438 Mikrotik's Routerboard 532.
440 To compile this driver as a module, choose M here: the
441 module will be called rb532_button.
443 config INPUT_DM355EVM
444 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
445 depends on MFD_DM355EVM_MSP
446 select INPUT_SPARSEKMAP
448 Supports the pushbuttons and IR remote used with
451 To compile this driver as a module, choose M here: the
452 module will be called dm355evm_keys.
454 config INPUT_BFIN_ROTARY
455 tristate "Blackfin Rotary support"
456 depends on BF54x || BF52x
458 Say Y here if you want to use the Blackfin Rotary.
460 To compile this driver as a module, choose M here: the
461 module will be called bfin-rotary.
463 config INPUT_WM831X_ON
464 tristate "WM831X ON pin"
465 depends on MFD_WM831X
467 Support the ON pin of WM831X PMICs as an input device
468 reporting power button status.
470 To compile this driver as a module, choose M here: the module
471 will be called wm831x_on.
474 tristate "Motorola EZX PCAP misc input events"
477 Say Y here if you want to use Power key and Headphone button
478 on Motorola EZX phones.
480 To compile this driver as a module, choose M here: the
481 module will be called pcap_keys.
484 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
487 Say Y here if you have a Accelerometer interface using the
488 ADXL345/6 controller, and your board-specific initialization
489 code includes that in its table of devices.
491 This driver can use either I2C or SPI communication to the
492 ADXL345/6 controller. Select the appropriate method for
495 If unsure, say N (but it's safe to say "Y").
497 To compile this driver as a module, choose M here: the
498 module will be called adxl34x.
500 config INPUT_ADXL34X_I2C
501 tristate "support I2C bus connection"
502 depends on INPUT_ADXL34X && I2C
505 Say Y here if you have ADXL345/6 hooked to an I2C bus.
507 To compile this driver as a module, choose M here: the
508 module will be called adxl34x-i2c.
510 config INPUT_ADXL34X_SPI
511 tristate "support SPI bus connection"
512 depends on INPUT_ADXL34X && SPI
515 Say Y here if you have ADXL345/6 hooked to a SPI bus.
517 To compile this driver as a module, choose M here: the
518 module will be called adxl34x-spi.
521 tristate "VTI CMA3000 Tri-axis accelerometer"
523 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
526 This driver currently only supports I2C interface to the
527 controller. Also select the I2C method.
531 To compile this driver as a module, choose M here: the
532 module will be called cma3000_d0x.
534 config INPUT_CMA3000_I2C
535 tristate "Support I2C bus connection"
536 depends on INPUT_CMA3000 && I2C
538 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
539 through I2C interface.
541 To compile this driver as a module, choose M here: the
542 module will be called cma3000_d0x_i2c.
544 config INPUT_XEN_KBDDEV_FRONTEND
545 tristate "Xen virtual keyboard and mouse support"
546 depends on XEN_FBDEV_FRONTEND
548 select XEN_XENBUS_FRONTEND
550 This driver implements the front-end of the Xen virtual
551 keyboard and mouse device driver. It communicates with a back-end
554 To compile this driver as a module, choose M here: the
555 module will be called xen-kbdfront.