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 "PC Speaker support"
67 depends on PCSPKR_PLATFORM
69 Say Y here if you want the standard PC Speaker to be used for
74 To compile this driver as a module, choose M here: the
75 module will be called pcspkr.
77 config INPUT_SPARCSPKR
78 tristate "SPARC Speaker support"
79 depends on PCI && SPARC64
81 Say Y here if you want the standard Speaker on Sparc PCI systems
82 to be used for bells and whistles.
86 To compile this driver as a module, choose M here: the
87 module will be called sparcspkr.
89 config INPUT_M68K_BEEP
90 tristate "M68k Beeper support"
93 config INPUT_MAX8925_ONKEY
94 tristate "MAX8925 ONKEY support"
95 depends on MFD_MAX8925
97 Support the ONKEY of MAX8925 PMICs as an input device
98 reporting power button status.
100 To compile this driver as a module, choose M here: the module
101 will be called max8925_onkey.
104 tristate "Fujitsu Lifebook Application Panel buttons"
105 depends on X86 && I2C && LEDS_CLASS
107 select CHECK_SIGNATURE
109 Say Y here for support of the Application Panel buttons, used on
110 Fujitsu Lifebook. These are attached to the mainboard through
111 an SMBus interface managed by the I2C Intel ICH (i801) driver,
112 which you should also build for this kernel.
114 To compile this driver as a module, choose M here: the module will
117 config INPUT_IXP4XX_BEEPER
118 tristate "IXP4XX Beeper support"
119 depends on ARCH_IXP4XX
121 If you say yes here, you can connect a beeper to the
122 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
126 To compile this driver as a module, choose M here: the
127 module will be called ixp4xx-beeper.
129 config INPUT_COBALT_BTNS
130 tristate "Cobalt button interface"
131 depends on MIPS_COBALT
134 Say Y here if you want to support MIPS Cobalt button interface.
136 To compile this driver as a module, choose M here: the
137 module will be called cobalt_btns.
139 config INPUT_WISTRON_BTNS
140 tristate "x86 Wistron laptop button interface"
141 depends on X86 && !X86_64
143 select INPUT_SPARSEKMAP
146 select CHECK_SIGNATURE
148 Say Y here for support of Wistron laptop button interfaces, used on
149 laptops of various brands, including Acer and Fujitsu-Siemens. If
150 available, mail and wifi LEDs will be controllable via /sys/class/leds.
152 To compile this driver as a module, choose M here: the module will
153 be called wistron_btns.
155 config INPUT_ATLAS_BTNS
156 tristate "x86 Atlas button interface"
157 depends on X86 && ACPI
159 Say Y here for support of Atlas wallmount touchscreen buttons.
160 The events will show up as scancodes F1 through F9 via evdev.
162 To compile this driver as a module, choose M here: the module will
163 be called atlas_btns.
165 config INPUT_ATI_REMOTE
166 tristate "ATI / X10 USB RF remote control"
167 depends on USB_ARCH_HAS_HCD
170 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
171 These are RF remotes with USB receivers.
172 The ATI remote comes with many of ATI's All-In-Wonder video cards.
173 The X10 "Lola" remote is available at:
174 <http://www.x10.com/products/lola_sg1.htm>
175 This driver provides mouse pointer, left and right mouse buttons,
176 and maps all the other remote buttons to keypress events.
178 To compile this driver as a module, choose M here: the module will be
181 config INPUT_ATI_REMOTE2
182 tristate "ATI / Philips USB RF remote control"
183 depends on USB_ARCH_HAS_HCD
186 Say Y here if you want to use an ATI or Philips USB RF remote control.
187 These are RF remotes with USB receivers.
188 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
189 and is also available as a separate product.
190 This driver provides mouse pointer, left and right mouse buttons,
191 and maps all the other remote buttons to keypress events.
193 To compile this driver as a module, choose M here: the module will be
196 config INPUT_KEYSPAN_REMOTE
197 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
198 depends on EXPERIMENTAL
199 depends on USB_ARCH_HAS_HCD
202 Say Y here if you want to use a Keyspan DMR USB remote control.
203 Currently only the UIA-11 type of receiver has been tested. The tag
204 on the receiver that connects to the USB port should have a P/N that
205 will tell you what type of DMR you have. The UIA-10 type is not
206 supported at this time. This driver maps all buttons to keypress
209 To compile this driver as a module, choose M here: the module will
210 be called keyspan_remote.
212 config INPUT_POWERMATE
213 tristate "Griffin PowerMate and Contour Jog support"
214 depends on USB_ARCH_HAS_HCD
217 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
218 These are aluminum dials which can measure clockwise and anticlockwise
219 rotation. The dial also acts as a pushbutton. The base contains an LED
220 which can be instructed to pulse or to switch to a particular intensity.
222 You can download userspace tools from
223 <http://sowerbutts.com/powermate/>.
225 To compile this driver as a module, choose M here: the
226 module will be called powermate.
229 tristate "Yealink usb-p1k voip phone"
230 depends on EXPERIMENTAL
231 depends on USB_ARCH_HAS_HCD
234 Say Y here if you want to enable keyboard and LCD functions of the
235 Yealink usb-p1k usb phones. The audio part is enabled by the generic
236 usb sound driver, so you might want to enable that as well.
238 For information about how to use these additional functions, see
239 <file:Documentation/input/yealink.txt>.
241 To compile this driver as a module, choose M here: the module will be
245 tristate "C-Media CM109 USB I/O Controller"
246 depends on EXPERIMENTAL
247 depends on USB_ARCH_HAS_HCD
250 Say Y here if you want to enable keyboard and buzzer functions of the
251 C-Media CM109 usb phones. The audio part is enabled by the generic
252 usb sound driver, so you might want to enable that as well.
254 To compile this driver as a module, choose M here: the module will be
257 config INPUT_TWL4030_PWRBUTTON
258 tristate "TWL4030 Power button Driver"
259 depends on TWL4030_CORE
261 Say Y here if you want to enable power key reporting via the
262 TWL4030 family of chips.
264 To compile this driver as a module, choose M here. The module will
265 be called twl4030_pwrbutton.
267 config INPUT_TWL4030_VIBRA
268 tristate "Support for TWL4030 Vibrator"
269 depends on TWL4030_CORE
271 select INPUT_FF_MEMLESS
273 This option enables support for TWL4030 Vibrator Driver.
275 To compile this driver as a module, choose M here. The module will
276 be called twl4030_vibra.
279 tristate "User level driver support"
281 Say Y here if you want to support user level drivers for input
282 subsystem accessible under char device 10:223 - /dev/input/uinput.
284 To compile this driver as a module, choose M here: the
285 module will be called uinput.
287 config INPUT_SGI_BTNS
288 tristate "SGI Indy/O2 volume button interface"
289 depends on SGI_IP22 || SGI_IP32
292 Say Y here if you want to support SGI Indy/O2 volume button interface.
294 To compile this driver as a module, choose M here: the
295 module will be called sgi_btns.
298 tristate "HP SDC Real Time Clock"
299 depends on (GSC || HP300) && SERIO
302 Say Y here if you want to support the built-in real time clock
303 of the HP SDC controller.
305 config INPUT_PCF50633_PMU
306 tristate "PCF50633 PMU events"
307 depends on MFD_PCF50633
309 Say Y to include support for delivering PMU events via input
310 layer on NXP PCF50633.
313 tristate "PCF8574 Keypad input device"
314 depends on I2C && EXPERIMENTAL
316 Say Y here if you want to support a keypad connetced via I2C
319 To compile this driver as a module, choose M here: the
320 module will be called pcf8574_keypad.
322 config INPUT_PWM_BEEPER
323 tristate "PWM beeper support"
326 Say Y here to get support for PWM based beeper devices.
330 To compile this driver as a module, choose M here: the module will be
333 config INPUT_GPIO_ROTARY_ENCODER
334 tristate "Rotary encoders connected to GPIO pins"
335 depends on GPIOLIB && GENERIC_GPIO
337 Say Y here to add support for rotary encoders connected to GPIO lines.
338 Check file:Documentation/input/rotary-encoder.txt for more
341 To compile this driver as a module, choose M here: the
342 module will be called rotary_encoder.
344 config INPUT_RB532_BUTTON
345 tristate "Mikrotik Routerboard 532 button interface"
346 depends on MIKROTIK_RB532
347 depends on GPIOLIB && GENERIC_GPIO
350 Say Y here if you want support for the S1 button built into
351 Mikrotik's Routerboard 532.
353 To compile this driver as a module, choose M here: the
354 module will be called rb532_button.
356 config INPUT_DM355EVM
357 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
358 depends on MFD_DM355EVM_MSP
359 select INPUT_SPARSEKMAP
361 Supports the pushbuttons and IR remote used with
364 To compile this driver as a module, choose M here: the
365 module will be called dm355evm_keys.
367 config INPUT_BFIN_ROTARY
368 tristate "Blackfin Rotary support"
369 depends on BF54x || BF52x
371 Say Y here if you want to use the Blackfin Rotary.
373 To compile this driver as a module, choose M here: the
374 module will be called bfin-rotary.
376 config INPUT_WM831X_ON
377 tristate "WM831X ON pin"
378 depends on MFD_WM831X
380 Support the ON pin of WM831X PMICs as an input device
381 reporting power button status.
383 To compile this driver as a module, choose M here: the module
384 will be called wm831x_on.
387 tristate "Motorola EZX PCAP misc input events"
390 Say Y here if you want to use Power key and Headphone button
391 on Motorola EZX phones.
393 To compile this driver as a module, choose M here: the
394 module will be called pcap_keys.
397 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
400 Say Y here if you have a Accelerometer interface using the
401 ADXL345/6 controller, and your board-specific initialization
402 code includes that in its table of devices.
404 This driver can use either I2C or SPI communication to the
405 ADXL345/6 controller. Select the appropriate method for
408 If unsure, say N (but it's safe to say "Y").
410 To compile this driver as a module, choose M here: the
411 module will be called adxl34x.
413 config INPUT_ADXL34X_I2C
414 tristate "support I2C bus connection"
415 depends on INPUT_ADXL34X && I2C
418 Say Y here if you have ADXL345/6 hooked to an I2C bus.
420 To compile this driver as a module, choose M here: the
421 module will be called adxl34x-i2c.
423 config INPUT_ADXL34X_SPI
424 tristate "support SPI bus connection"
425 depends on INPUT_ADXL34X && SPI
428 Say Y here if you have ADXL345/6 hooked to a SPI bus.
430 To compile this driver as a module, choose M here: the
431 module will be called adxl34x-spi.
434 tristate "VTI CMA3000 Tri-axis accelerometer"
436 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
439 This driver currently only supports I2C interface to the
440 controller. Also select the I2C method.
444 To compile this driver as a module, choose M here: the
445 module will be called cma3000_d0x.
447 config INPUT_CMA3000_I2C
448 tristate "Support I2C bus connection"
449 depends on INPUT_CMA3000 && I2C
451 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
452 through I2C interface.
454 To compile this driver as a module, choose M here: the
455 module will be called cma3000_d0x_i2c.
457 config INPUT_XEN_KBDDEV_FRONTEND
458 tristate "Xen virtual keyboard and mouse support"
459 depends on XEN_FBDEV_FRONTEND
461 select XEN_XENBUS_FRONTEND
463 This driver implements the front-end of the Xen virtual
464 keyboard and mouse device driver. It communicates with a back-end
467 To compile this driver as a module, choose M here: the
468 module will be called xen-kbdfront.