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_LPSENSOR_ISL29028
16 tristate "isl29028 l/p sensor input support"
18 config INPUT_LPSENSOR_CM3602
19 tristate "l/p sensor input support"
21 config INPUT_88PM860X_ONKEY
22 tristate "88PM860x ONKEY support"
23 depends on MFD_88PM860X
25 Support the ONKEY of Marvell 88PM860x PMICs as an input device
26 reporting power button status.
28 To compile this driver as a module, choose M here: the module
29 will be called 88pm860x_onkey.
32 tristate "Analog Devices AD714x Capacitance Touch Sensor"
34 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
36 You should select a bus connection too.
38 To compile this driver as a module, choose M here: the
39 module will be called ad714x.
41 config INPUT_AD714X_I2C
42 tristate "support I2C bus connection"
43 depends on INPUT_AD714X && I2C
46 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
48 To compile this driver as a module, choose M here: the
49 module will be called ad714x-i2c.
51 config INPUT_AD714X_SPI
52 tristate "support SPI bus connection"
53 depends on INPUT_AD714X && SPI
56 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
58 To compile this driver as a module, choose M here: the
59 module will be called ad714x-spi.
62 tristate "PC Speaker support"
63 depends on PCSPKR_PLATFORM
65 Say Y here if you want the standard PC Speaker to be used for
70 To compile this driver as a module, choose M here: the
71 module will be called pcspkr.
73 config INPUT_SPARCSPKR
74 tristate "SPARC Speaker support"
75 depends on PCI && SPARC64
77 Say Y here if you want the standard Speaker on Sparc PCI systems
78 to be used for bells and whistles.
82 To compile this driver as a module, choose M here: the
83 module will be called sparcspkr.
85 config INPUT_M68K_BEEP
86 tristate "M68k Beeper support"
89 config INPUT_MAX8925_ONKEY
90 tristate "MAX8925 ONKEY support"
91 depends on MFD_MAX8925
93 Support the ONKEY of MAX8925 PMICs as an input device
94 reporting power button status.
96 To compile this driver as a module, choose M here: the module
97 will be called max8925_onkey.
100 tristate "Fujitsu Lifebook Application Panel buttons"
101 depends on X86 && I2C && LEDS_CLASS
103 select CHECK_SIGNATURE
105 Say Y here for support of the Application Panel buttons, used on
106 Fujitsu Lifebook. These are attached to the mainboard through
107 an SMBus interface managed by the I2C Intel ICH (i801) driver,
108 which you should also build for this kernel.
110 To compile this driver as a module, choose M here: the module will
113 config INPUT_IXP4XX_BEEPER
114 tristate "IXP4XX Beeper support"
115 depends on ARCH_IXP4XX
117 If you say yes here, you can connect a beeper to the
118 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
122 To compile this driver as a module, choose M here: the
123 module will be called ixp4xx-beeper.
125 config INPUT_COBALT_BTNS
126 tristate "Cobalt button interface"
127 depends on MIPS_COBALT
130 Say Y here if you want to support MIPS Cobalt button interface.
132 To compile this driver as a module, choose M here: the
133 module will be called cobalt_btns.
135 config INPUT_WISTRON_BTNS
136 tristate "x86 Wistron laptop button interface"
137 depends on X86 && !X86_64
139 select INPUT_SPARSEKMAP
142 select CHECK_SIGNATURE
144 Say Y here for support of Wistron laptop button interfaces, used on
145 laptops of various brands, including Acer and Fujitsu-Siemens. If
146 available, mail and wifi LEDs will be controllable via /sys/class/leds.
148 To compile this driver as a module, choose M here: the module will
149 be called wistron_btns.
151 config INPUT_ATLAS_BTNS
152 tristate "x86 Atlas button interface"
153 depends on X86 && ACPI
155 Say Y here for support of Atlas wallmount touchscreen buttons.
156 The events will show up as scancodes F1 through F9 via evdev.
158 To compile this driver as a module, choose M here: the module will
159 be called atlas_btns.
161 config INPUT_ATI_REMOTE
162 tristate "ATI / X10 USB RF remote control"
163 depends on USB_ARCH_HAS_HCD
166 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
167 These are RF remotes with USB receivers.
168 The ATI remote comes with many of ATI's All-In-Wonder video cards.
169 The X10 "Lola" remote is available at:
170 <http://www.x10.com/products/lola_sg1.htm>
171 This driver provides mouse pointer, left and right mouse buttons,
172 and maps all the other remote buttons to keypress events.
174 To compile this driver as a module, choose M here: the module will be
177 config INPUT_ATI_REMOTE2
178 tristate "ATI / Philips USB RF remote control"
179 depends on USB_ARCH_HAS_HCD
182 Say Y here if you want to use an ATI or Philips USB RF remote control.
183 These are RF remotes with USB receivers.
184 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
185 and is also available as a separate product.
186 This driver provides mouse pointer, left and right mouse buttons,
187 and maps all the other remote buttons to keypress events.
189 To compile this driver as a module, choose M here: the module will be
192 config INPUT_KEYSPAN_REMOTE
193 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
194 depends on EXPERIMENTAL
195 depends on USB_ARCH_HAS_HCD
198 Say Y here if you want to use a Keyspan DMR USB remote control.
199 Currently only the UIA-11 type of receiver has been tested. The tag
200 on the receiver that connects to the USB port should have a P/N that
201 will tell you what type of DMR you have. The UIA-10 type is not
202 supported at this time. This driver maps all buttons to keypress
205 To compile this driver as a module, choose M here: the module will
206 be called keyspan_remote.
208 config INPUT_POWERMATE
209 tristate "Griffin PowerMate and Contour Jog support"
210 depends on USB_ARCH_HAS_HCD
213 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
214 These are aluminum dials which can measure clockwise and anticlockwise
215 rotation. The dial also acts as a pushbutton. The base contains an LED
216 which can be instructed to pulse or to switch to a particular intensity.
218 You can download userspace tools from
219 <http://sowerbutts.com/powermate/>.
221 To compile this driver as a module, choose M here: the
222 module will be called powermate.
225 tristate "Yealink usb-p1k voip phone"
226 depends on EXPERIMENTAL
227 depends on USB_ARCH_HAS_HCD
230 Say Y here if you want to enable keyboard and LCD functions of the
231 Yealink usb-p1k usb phones. The audio part is enabled by the generic
232 usb sound driver, so you might want to enable that as well.
234 For information about how to use these additional functions, see
235 <file:Documentation/input/yealink.txt>.
237 To compile this driver as a module, choose M here: the module will be
241 tristate "C-Media CM109 USB I/O Controller"
242 depends on EXPERIMENTAL
243 depends on USB_ARCH_HAS_HCD
246 Say Y here if you want to enable keyboard and buzzer functions of the
247 C-Media CM109 usb phones. The audio part is enabled by the generic
248 usb sound driver, so you might want to enable that as well.
250 To compile this driver as a module, choose M here: the module will be
253 config INPUT_TPS65910_PWRBUTTON
254 tristate "TPS65910 Power button Driver"
255 depends on TPS65910_CORE
257 Say Y here if you want to enable power key reporting via the
258 TPS65910 family of chips.
260 To compile this driver as a module, choose M here. The module will
261 be called tps65910_pwrbutton.
263 config INPUT_TWL4030_PWRBUTTON
264 tristate "TWL4030 Power button Driver"
265 depends on TWL4030_CORE
267 Say Y here if you want to enable power key reporting via the
268 TWL4030 family of chips.
270 To compile this driver as a module, choose M here. The module will
271 be called twl4030_pwrbutton.
273 config INPUT_TWL4030_VIBRA
274 tristate "Support for TWL4030 Vibrator"
275 depends on TWL4030_CORE
277 select INPUT_FF_MEMLESS
279 This option enables support for TWL4030 Vibrator Driver.
281 To compile this driver as a module, choose M here. The module will
282 be called twl4030_vibra.
285 tristate "User level driver support"
287 Say Y here if you want to support user level drivers for input
288 subsystem accessible under char device 10:223 - /dev/input/uinput.
290 To compile this driver as a module, choose M here: the
291 module will be called uinput.
293 config INPUT_SGI_BTNS
294 tristate "SGI Indy/O2 volume button interface"
295 depends on SGI_IP22 || SGI_IP32
298 Say Y here if you want to support SGI Indy/O2 volume button interface.
300 To compile this driver as a module, choose M here: the
301 module will be called sgi_btns.
303 config INPUT_WINBOND_CIR
304 tristate "Winbond IR remote control"
305 depends on X86 && PNP
311 Say Y here if you want to use the IR remote functionality found
312 in some Winbond SuperI/O chips. Currently only the WPCD376I
313 chip is supported (included in some Intel Media series motherboards).
315 IR Receive and wake-on-IR from suspend and power-off is currently
318 To compile this driver as a module, choose M here: the module will be
322 tristate "HP SDC Real Time Clock"
323 depends on (GSC || HP300) && SERIO
326 Say Y here if you want to support the built-in real time clock
327 of the HP SDC controller.
329 config INPUT_PCF50633_PMU
330 tristate "PCF50633 PMU events"
331 depends on MFD_PCF50633
333 Say Y to include support for delivering PMU events via input
334 layer on NXP PCF50633.
337 tristate "PCF8574 Keypad input device"
338 depends on I2C && EXPERIMENTAL
340 Say Y here if you want to support a keypad connetced via I2C
343 To compile this driver as a module, choose M here: the
344 module will be called pcf8574_keypad.
346 config INPUT_PWM_BEEPER
347 tristate "PWM beeper support"
350 Say Y here to get support for PWM based beeper devices.
354 To compile this driver as a module, choose M here: the module will be
357 config INPUT_GPIO_ROTARY_ENCODER
358 tristate "Rotary encoders connected to GPIO pins"
359 depends on GPIOLIB && GENERIC_GPIO
361 Say Y here to add support for rotary encoders connected to GPIO lines.
362 Check file:Documentation/input/rotary-encoder.txt for more
365 To compile this driver as a module, choose M here: the
366 module will be called rotary_encoder.
368 config INPUT_RB532_BUTTON
369 tristate "Mikrotik Routerboard 532 button interface"
370 depends on MIKROTIK_RB532
371 depends on GPIOLIB && GENERIC_GPIO
374 Say Y here if you want support for the S1 button built into
375 Mikrotik's Routerboard 532.
377 To compile this driver as a module, choose M here: the
378 module will be called rb532_button.
380 config INPUT_DM355EVM
381 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
382 depends on MFD_DM355EVM_MSP
383 select INPUT_SPARSEKMAP
385 Supports the pushbuttons and IR remote used with
388 To compile this driver as a module, choose M here: the
389 module will be called dm355evm_keys.
391 config INPUT_BFIN_ROTARY
392 tristate "Blackfin Rotary support"
393 depends on BF54x || BF52x
395 Say Y here if you want to use the Blackfin Rotary.
397 To compile this driver as a module, choose M here: the
398 module will be called bfin-rotary.
400 config INPUT_WM831X_ON
401 tristate "WM831X ON pin"
402 depends on MFD_WM831X
404 Support the ON pin of WM831X PMICs as an input device
405 reporting power button status.
407 To compile this driver as a module, choose M here: the module
408 will be called wm831x_on.
411 tristate "Motorola EZX PCAP misc input events"
414 Say Y here if you want to use Power key and Headphone button
415 on Motorola EZX phones.
417 To compile this driver as a module, choose M here: the
418 module will be called pcap_keys.
421 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
424 Say Y here if you have a Accelerometer interface using the
425 ADXL345/6 controller, and your board-specific initialization
426 code includes that in its table of devices.
428 This driver can use either I2C or SPI communication to the
429 ADXL345/6 controller. Select the appropriate method for
432 If unsure, say N (but it's safe to say "Y").
434 To compile this driver as a module, choose M here: the
435 module will be called adxl34x.
437 config INPUT_ADXL34X_I2C
438 tristate "support I2C bus connection"
439 depends on INPUT_ADXL34X && I2C
442 Say Y here if you have ADXL345/6 hooked to an I2C bus.
444 To compile this driver as a module, choose M here: the
445 module will be called adxl34x-i2c.
447 config INPUT_ADXL34X_SPI
448 tristate "support SPI bus connection"
449 depends on INPUT_ADXL34X && SPI
452 Say Y here if you have ADXL345/6 hooked to a SPI bus.
454 To compile this driver as a module, choose M here: the
455 module will be called adxl34x-spi.