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.
138 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
142 Say Y here if you want to support Freescale's MMA8450 Accelerometer
143 through I2C interface.
145 To compile this driver as a module, choose M here: the
146 module will be called mma8450.
149 tristate "MPU3050 Triaxial gyroscope sensor"
152 Say Y here if you want to support InvenSense MPU3050
153 connected via an I2C bus.
155 To compile this driver as a module, choose M here: the
156 module will be called mpu3050.
159 tristate "Fujitsu Lifebook Application Panel buttons"
160 depends on X86 && I2C && LEDS_CLASS
162 select CHECK_SIGNATURE
164 Say Y here for support of the Application Panel buttons, used on
165 Fujitsu Lifebook. These are attached to the mainboard through
166 an SMBus interface managed by the I2C Intel ICH (i801) driver,
167 which you should also build for this kernel.
169 To compile this driver as a module, choose M here: the module will
172 config INPUT_IXP4XX_BEEPER
173 tristate "IXP4XX Beeper support"
174 depends on ARCH_IXP4XX
176 If you say yes here, you can connect a beeper to the
177 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
181 To compile this driver as a module, choose M here: the
182 module will be called ixp4xx-beeper.
184 config INPUT_COBALT_BTNS
185 tristate "Cobalt button interface"
186 depends on MIPS_COBALT
189 Say Y here if you want to support MIPS Cobalt button interface.
191 To compile this driver as a module, choose M here: the
192 module will be called cobalt_btns.
194 config INPUT_WISTRON_BTNS
195 tristate "x86 Wistron laptop button interface"
196 depends on X86 && !X86_64
198 select INPUT_SPARSEKMAP
201 select CHECK_SIGNATURE
203 Say Y here for support of Wistron laptop button interfaces, used on
204 laptops of various brands, including Acer and Fujitsu-Siemens. If
205 available, mail and wifi LEDs will be controllable via /sys/class/leds.
207 To compile this driver as a module, choose M here: the module will
208 be called wistron_btns.
210 config INPUT_ATLAS_BTNS
211 tristate "x86 Atlas button interface"
212 depends on X86 && ACPI
214 Say Y here for support of Atlas wallmount touchscreen buttons.
215 The events will show up as scancodes F1 through F9 via evdev.
217 To compile this driver as a module, choose M here: the module will
218 be called atlas_btns.
220 config INPUT_ATI_REMOTE2
221 tristate "ATI / Philips USB RF remote control"
222 depends on USB_ARCH_HAS_HCD
225 Say Y here if you want to use an ATI or Philips USB RF remote control.
226 These are RF remotes with USB receivers.
227 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
228 and is also available as a separate product.
229 This driver provides mouse pointer, left and right mouse buttons,
230 and maps all the other remote buttons to keypress events.
232 To compile this driver as a module, choose M here: the module will be
235 config INPUT_KEYSPAN_REMOTE
236 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
237 depends on EXPERIMENTAL
238 depends on USB_ARCH_HAS_HCD
241 Say Y here if you want to use a Keyspan DMR USB remote control.
242 Currently only the UIA-11 type of receiver has been tested. The tag
243 on the receiver that connects to the USB port should have a P/N that
244 will tell you what type of DMR you have. The UIA-10 type is not
245 supported at this time. This driver maps all buttons to keypress
248 To compile this driver as a module, choose M here: the module will
249 be called keyspan_remote.
252 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
255 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
258 To compile this driver as a module, choose M here: the module will
261 config INPUT_KXTJ9_POLLED_MODE
262 bool "Enable polling mode support"
263 depends on INPUT_KXTJ9
266 Say Y here if you need accelerometer to work in polling mode.
268 config INPUT_POWERMATE
269 tristate "Griffin PowerMate and Contour Jog support"
270 depends on USB_ARCH_HAS_HCD
273 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
274 These are aluminum dials which can measure clockwise and anticlockwise
275 rotation. The dial also acts as a pushbutton. The base contains an LED
276 which can be instructed to pulse or to switch to a particular intensity.
278 You can download userspace tools from
279 <http://sowerbutts.com/powermate/>.
281 To compile this driver as a module, choose M here: the
282 module will be called powermate.
285 tristate "Yealink usb-p1k voip phone"
286 depends on EXPERIMENTAL
287 depends on USB_ARCH_HAS_HCD
290 Say Y here if you want to enable keyboard and LCD functions of the
291 Yealink usb-p1k usb phones. The audio part is enabled by the generic
292 usb sound driver, so you might want to enable that as well.
294 For information about how to use these additional functions, see
295 <file:Documentation/input/yealink.txt>.
297 To compile this driver as a module, choose M here: the module will be
301 tristate "C-Media CM109 USB I/O Controller"
302 depends on EXPERIMENTAL
303 depends on USB_ARCH_HAS_HCD
306 Say Y here if you want to enable keyboard and buzzer functions of the
307 C-Media CM109 usb phones. The audio part is enabled by the generic
308 usb sound driver, so you might want to enable that as well.
310 To compile this driver as a module, choose M here: the module will be
313 config INPUT_TWL4030_PWRBUTTON
314 tristate "TWL4030 Power button Driver"
315 depends on TWL4030_CORE
317 Say Y here if you want to enable power key reporting via the
318 TWL4030 family of chips.
320 To compile this driver as a module, choose M here. The module will
321 be called twl4030_pwrbutton.
323 config INPUT_TWL4030_VIBRA
324 tristate "Support for TWL4030 Vibrator"
325 depends on TWL4030_CORE
326 select MFD_TWL4030_AUDIO
327 select INPUT_FF_MEMLESS
329 This option enables support for TWL4030 Vibrator Driver.
331 To compile this driver as a module, choose M here. The module will
332 be called twl4030_vibra.
334 config INPUT_TWL6040_VIBRA
335 tristate "Support for TWL6040 Vibrator"
336 depends on TWL4030_CORE
338 select INPUT_FF_MEMLESS
340 This option enables support for TWL6040 Vibrator Driver.
342 To compile this driver as a module, choose M here. The module will
343 be called twl6040_vibra.
346 tristate "User level driver support"
348 Say Y here if you want to support user level drivers for input
349 subsystem accessible under char device 10:223 - /dev/input/uinput.
351 To compile this driver as a module, choose M here: the
352 module will be called uinput.
354 config INPUT_SGI_BTNS
355 tristate "SGI Indy/O2 volume button interface"
356 depends on SGI_IP22 || SGI_IP32
359 Say Y here if you want to support SGI Indy/O2 volume button interface.
361 To compile this driver as a module, choose M here: the
362 module will be called sgi_btns.
365 tristate "HP SDC Real Time Clock"
366 depends on (GSC || HP300) && SERIO
369 Say Y here if you want to support the built-in real time clock
370 of the HP SDC controller.
372 config INPUT_PCF50633_PMU
373 tristate "PCF50633 PMU events"
374 depends on MFD_PCF50633
376 Say Y to include support for delivering PMU events via input
377 layer on NXP PCF50633.
380 tristate "PCF8574 Keypad input device"
381 depends on I2C && EXPERIMENTAL
383 Say Y here if you want to support a keypad connetced via I2C
386 To compile this driver as a module, choose M here: the
387 module will be called pcf8574_keypad.
389 config INPUT_PWM_BEEPER
390 tristate "PWM beeper support"
393 Say Y here to get support for PWM based beeper devices.
397 To compile this driver as a module, choose M here: the module will be
400 config INPUT_GPIO_ROTARY_ENCODER
401 tristate "Rotary encoders connected to GPIO pins"
402 depends on GPIOLIB && GENERIC_GPIO
404 Say Y here to add support for rotary encoders connected to GPIO lines.
405 Check file:Documentation/input/rotary-encoder.txt for more
408 To compile this driver as a module, choose M here: the
409 module will be called rotary_encoder.
411 config INPUT_RB532_BUTTON
412 tristate "Mikrotik Routerboard 532 button interface"
413 depends on MIKROTIK_RB532
414 depends on GPIOLIB && GENERIC_GPIO
417 Say Y here if you want support for the S1 button built into
418 Mikrotik's Routerboard 532.
420 To compile this driver as a module, choose M here: the
421 module will be called rb532_button.
423 config INPUT_DM355EVM
424 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
425 depends on MFD_DM355EVM_MSP
426 select INPUT_SPARSEKMAP
428 Supports the pushbuttons and IR remote used with
431 To compile this driver as a module, choose M here: the
432 module will be called dm355evm_keys.
434 config INPUT_BFIN_ROTARY
435 tristate "Blackfin Rotary support"
436 depends on BF54x || BF52x
438 Say Y here if you want to use the Blackfin Rotary.
440 To compile this driver as a module, choose M here: the
441 module will be called bfin-rotary.
443 config INPUT_WM831X_ON
444 tristate "WM831X ON pin"
445 depends on MFD_WM831X
447 Support the ON pin of WM831X PMICs as an input device
448 reporting power button status.
450 To compile this driver as a module, choose M here: the module
451 will be called wm831x_on.
454 tristate "Motorola EZX PCAP misc input events"
457 Say Y here if you want to use Power key and Headphone button
458 on Motorola EZX phones.
460 To compile this driver as a module, choose M here: the
461 module will be called pcap_keys.
464 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
467 Say Y here if you have a Accelerometer interface using the
468 ADXL345/6 controller, and your board-specific initialization
469 code includes that in its table of devices.
471 This driver can use either I2C or SPI communication to the
472 ADXL345/6 controller. Select the appropriate method for
475 If unsure, say N (but it's safe to say "Y").
477 To compile this driver as a module, choose M here: the
478 module will be called adxl34x.
480 config INPUT_ADXL34X_I2C
481 tristate "support I2C bus connection"
482 depends on INPUT_ADXL34X && I2C
485 Say Y here if you have ADXL345/6 hooked to an I2C bus.
487 To compile this driver as a module, choose M here: the
488 module will be called adxl34x-i2c.
490 config INPUT_ADXL34X_SPI
491 tristate "support SPI bus connection"
492 depends on INPUT_ADXL34X && SPI
495 Say Y here if you have ADXL345/6 hooked to a SPI bus.
497 To compile this driver as a module, choose M here: the
498 module will be called adxl34x-spi.
501 tristate "VTI CMA3000 Tri-axis accelerometer"
503 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
506 This driver currently only supports I2C interface to the
507 controller. Also select the I2C method.
511 To compile this driver as a module, choose M here: the
512 module will be called cma3000_d0x.
514 config INPUT_CMA3000_I2C
515 tristate "Support I2C bus connection"
516 depends on INPUT_CMA3000 && I2C
518 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
519 through I2C interface.
521 To compile this driver as a module, choose M here: the
522 module will be called cma3000_d0x_i2c.
524 config INPUT_XEN_KBDDEV_FRONTEND
525 tristate "Xen virtual keyboard and mouse support"
526 depends on XEN_FBDEV_FRONTEND
528 select XEN_XENBUS_FRONTEND
530 This driver implements the front-end of the Xen virtual
531 keyboard and mouse device driver. It communicates with a back-end
534 To compile this driver as a module, choose M here: the
535 module will be called xen-kbdfront.