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.
26 tristate "Analog Devices AD714x Capacitance Touch Sensor"
28 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
30 You should select a bus connection too.
32 To compile this driver as a module, choose M here: the
33 module will be called ad714x.
35 config INPUT_AD714X_I2C
36 tristate "support I2C bus connection"
37 depends on INPUT_AD714X && I2C
40 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
42 To compile this driver as a module, choose M here: the
43 module will be called ad714x-i2c.
45 config INPUT_AD714X_SPI
46 tristate "support SPI bus connection"
47 depends on INPUT_AD714X && SPI
50 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
52 To compile this driver as a module, choose M here: the
53 module will be called ad714x-spi.
56 tristate "PC Speaker support"
57 depends on PCSPKR_PLATFORM
59 Say Y here if you want the standard PC Speaker to be used for
64 To compile this driver as a module, choose M here: the
65 module will be called pcspkr.
67 config INPUT_SPARCSPKR
68 tristate "SPARC Speaker support"
69 depends on PCI && SPARC64
71 Say Y here if you want the standard Speaker on Sparc PCI systems
72 to be used for bells and whistles.
76 To compile this driver as a module, choose M here: the
77 module will be called sparcspkr.
79 config INPUT_M68K_BEEP
80 tristate "M68k Beeper support"
83 config INPUT_MAX8925_ONKEY
84 tristate "MAX8925 ONKEY support"
85 depends on MFD_MAX8925
87 Support the ONKEY of MAX8925 PMICs as an input device
88 reporting power button status.
90 To compile this driver as a module, choose M here: the module
91 will be called max8925_onkey.
94 tristate "Fujitsu Lifebook Application Panel buttons"
95 depends on X86 && I2C && LEDS_CLASS
97 select CHECK_SIGNATURE
99 Say Y here for support of the Application Panel buttons, used on
100 Fujitsu Lifebook. These are attached to the mainboard through
101 an SMBus interface managed by the I2C Intel ICH (i801) driver,
102 which you should also build for this kernel.
104 To compile this driver as a module, choose M here: the module will
107 config INPUT_IXP4XX_BEEPER
108 tristate "IXP4XX Beeper support"
109 depends on ARCH_IXP4XX
111 If you say yes here, you can connect a beeper to the
112 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
116 To compile this driver as a module, choose M here: the
117 module will be called ixp4xx-beeper.
119 config INPUT_COBALT_BTNS
120 tristate "Cobalt button interface"
121 depends on MIPS_COBALT
124 Say Y here if you want to support MIPS Cobalt button interface.
126 To compile this driver as a module, choose M here: the
127 module will be called cobalt_btns.
129 config INPUT_WISTRON_BTNS
130 tristate "x86 Wistron laptop button interface"
131 depends on X86 && !X86_64
133 select INPUT_SPARSEKMAP
136 select CHECK_SIGNATURE
138 Say Y here for support of Wistron laptop button interfaces, used on
139 laptops of various brands, including Acer and Fujitsu-Siemens. If
140 available, mail and wifi LEDs will be controllable via /sys/class/leds.
142 To compile this driver as a module, choose M here: the module will
143 be called wistron_btns.
145 config INPUT_ATLAS_BTNS
146 tristate "x86 Atlas button interface"
147 depends on X86 && ACPI
149 Say Y here for support of Atlas wallmount touchscreen buttons.
150 The events will show up as scancodes F1 through F9 via evdev.
152 To compile this driver as a module, choose M here: the module will
153 be called atlas_btns.
155 config INPUT_ATI_REMOTE
156 tristate "ATI / X10 USB RF remote control"
157 depends on USB_ARCH_HAS_HCD
160 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
161 These are RF remotes with USB receivers.
162 The ATI remote comes with many of ATI's All-In-Wonder video cards.
163 The X10 "Lola" remote is available at:
164 <http://www.x10.com/products/lola_sg1.htm>
165 This driver provides mouse pointer, left and right mouse buttons,
166 and maps all the other remote buttons to keypress events.
168 To compile this driver as a module, choose M here: the module will be
171 config INPUT_ATI_REMOTE2
172 tristate "ATI / Philips USB RF remote control"
173 depends on USB_ARCH_HAS_HCD
176 Say Y here if you want to use an ATI or Philips USB RF remote control.
177 These are RF remotes with USB receivers.
178 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
179 and is also available as a separate product.
180 This driver provides mouse pointer, left and right mouse buttons,
181 and maps all the other remote buttons to keypress events.
183 To compile this driver as a module, choose M here: the module will be
186 config INPUT_KEYSPAN_REMOTE
187 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
188 depends on EXPERIMENTAL
189 depends on USB_ARCH_HAS_HCD
192 Say Y here if you want to use a Keyspan DMR USB remote control.
193 Currently only the UIA-11 type of receiver has been tested. The tag
194 on the receiver that connects to the USB port should have a P/N that
195 will tell you what type of DMR you have. The UIA-10 type is not
196 supported at this time. This driver maps all buttons to keypress
199 To compile this driver as a module, choose M here: the module will
200 be called keyspan_remote.
202 config INPUT_POWERMATE
203 tristate "Griffin PowerMate and Contour Jog support"
204 depends on USB_ARCH_HAS_HCD
207 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
208 These are aluminum dials which can measure clockwise and anticlockwise
209 rotation. The dial also acts as a pushbutton. The base contains an LED
210 which can be instructed to pulse or to switch to a particular intensity.
212 You can download userspace tools from
213 <http://sowerbutts.com/powermate/>.
215 To compile this driver as a module, choose M here: the
216 module will be called powermate.
219 tristate "Yealink usb-p1k voip phone"
220 depends on EXPERIMENTAL
221 depends on USB_ARCH_HAS_HCD
224 Say Y here if you want to enable keyboard and LCD functions of the
225 Yealink usb-p1k usb phones. The audio part is enabled by the generic
226 usb sound driver, so you might want to enable that as well.
228 For information about how to use these additional functions, see
229 <file:Documentation/input/yealink.txt>.
231 To compile this driver as a module, choose M here: the module will be
235 tristate "C-Media CM109 USB I/O Controller"
236 depends on EXPERIMENTAL
237 depends on USB_ARCH_HAS_HCD
240 Say Y here if you want to enable keyboard and buzzer functions of the
241 C-Media CM109 usb phones. The audio part is enabled by the generic
242 usb sound driver, so you might want to enable that as well.
244 To compile this driver as a module, choose M here: the module will be
247 config INPUT_TWL4030_PWRBUTTON
248 tristate "TWL4030 Power button Driver"
249 depends on TWL4030_CORE
251 Say Y here if you want to enable power key reporting via the
252 TWL4030 family of chips.
254 To compile this driver as a module, choose M here. The module will
255 be called twl4030_pwrbutton.
257 config INPUT_TWL4030_VIBRA
258 tristate "Support for TWL4030 Vibrator"
259 depends on TWL4030_CORE
261 select INPUT_FF_MEMLESS
263 This option enables support for TWL4030 Vibrator Driver.
265 To compile this driver as a module, choose M here. The module will
266 be called twl4030_vibra.
269 tristate "User level driver support"
271 Say Y here if you want to support user level drivers for input
272 subsystem accessible under char device 10:223 - /dev/input/uinput.
274 To compile this driver as a module, choose M here: the
275 module will be called uinput.
277 config INPUT_SGI_BTNS
278 tristate "SGI Indy/O2 volume button interface"
279 depends on SGI_IP22 || SGI_IP32
282 Say Y here if you want to support SGI Indy/O2 volume button interface.
284 To compile this driver as a module, choose M here: the
285 module will be called sgi_btns.
287 config INPUT_WINBOND_CIR
288 tristate "Winbond IR remote control"
289 depends on X86 && PNP
295 Say Y here if you want to use the IR remote functionality found
296 in some Winbond SuperI/O chips. Currently only the WPCD376I
297 chip is supported (included in some Intel Media series motherboards).
299 IR Receive and wake-on-IR from suspend and power-off is currently
302 To compile this driver as a module, choose M here: the module will be
306 tristate "HP SDC Real Time Clock"
307 depends on (GSC || HP300) && SERIO
310 Say Y here if you want to support the built-in real time clock
311 of the HP SDC controller.
313 config INPUT_PCF50633_PMU
314 tristate "PCF50633 PMU events"
315 depends on MFD_PCF50633
317 Say Y to include support for delivering PMU events via input
318 layer on NXP PCF50633.
321 tristate "PCF8574 Keypad input device"
322 depends on I2C && EXPERIMENTAL
324 Say Y here if you want to support a keypad connetced via I2C
327 To compile this driver as a module, choose M here: the
328 module will be called pcf8574_keypad.
330 config INPUT_PWM_BEEPER
331 tristate "PWM beeper support"
334 Say Y here to get support for PWM based beeper devices.
338 To compile this driver as a module, choose M here: the module will be
341 config INPUT_GPIO_ROTARY_ENCODER
342 tristate "Rotary encoders connected to GPIO pins"
343 depends on GPIOLIB && GENERIC_GPIO
345 Say Y here to add support for rotary encoders connected to GPIO lines.
346 Check file:Documentation/input/rotary-encoder.txt for more
349 To compile this driver as a module, choose M here: the
350 module will be called rotary_encoder.
352 config INPUT_RB532_BUTTON
353 tristate "Mikrotik Routerboard 532 button interface"
354 depends on MIKROTIK_RB532
355 depends on GPIOLIB && GENERIC_GPIO
358 Say Y here if you want support for the S1 button built into
359 Mikrotik's Routerboard 532.
361 To compile this driver as a module, choose M here: the
362 module will be called rb532_button.
364 config INPUT_DM355EVM
365 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
366 depends on MFD_DM355EVM_MSP
367 select INPUT_SPARSEKMAP
369 Supports the pushbuttons and IR remote used with
372 To compile this driver as a module, choose M here: the
373 module will be called dm355evm_keys.
375 config INPUT_BFIN_ROTARY
376 tristate "Blackfin Rotary support"
377 depends on BF54x || BF52x
379 Say Y here if you want to use the Blackfin Rotary.
381 To compile this driver as a module, choose M here: the
382 module will be called bfin-rotary.
384 config INPUT_WM831X_ON
385 tristate "WM831X ON pin"
386 depends on MFD_WM831X
388 Support the ON pin of WM831X PMICs as an input device
389 reporting power button status.
391 To compile this driver as a module, choose M here: the module
392 will be called wm831x_on.
395 tristate "Motorola EZX PCAP misc input events"
398 Say Y here if you want to use Power key and Headphone button
399 on Motorola EZX phones.
401 To compile this driver as a module, choose M here: the
402 module will be called pcap_keys.
405 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
408 Say Y here if you have a Accelerometer interface using the
409 ADXL345/6 controller, and your board-specific initialization
410 code includes that in its table of devices.
412 This driver can use either I2C or SPI communication to the
413 ADXL345/6 controller. Select the appropriate method for
416 If unsure, say N (but it's safe to say "Y").
418 To compile this driver as a module, choose M here: the
419 module will be called adxl34x.
421 config INPUT_ADXL34X_I2C
422 tristate "support I2C bus connection"
423 depends on INPUT_ADXL34X && I2C
426 Say Y here if you have ADXL345/6 hooked to an I2C bus.
428 To compile this driver as a module, choose M here: the
429 module will be called adxl34x-i2c.
431 config INPUT_ADXL34X_SPI
432 tristate "support SPI bus connection"
433 depends on INPUT_ADXL34X && SPI
436 Say Y here if you have ADXL345/6 hooked to a SPI bus.
438 To compile this driver as a module, choose M here: the
439 module will be called adxl34x-spi.