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"
84 tristate "Fujitsu Lifebook Application Panel buttons"
85 depends on X86 && I2C && LEDS_CLASS
87 select CHECK_SIGNATURE
89 Say Y here for support of the Application Panel buttons, used on
90 Fujitsu Lifebook. These are attached to the mainboard through
91 an SMBus interface managed by the I2C Intel ICH (i801) driver,
92 which you should also build for this kernel.
94 To compile this driver as a module, choose M here: the module will
97 config INPUT_IXP4XX_BEEPER
98 tristate "IXP4XX Beeper support"
99 depends on ARCH_IXP4XX
101 If you say yes here, you can connect a beeper to the
102 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
106 To compile this driver as a module, choose M here: the
107 module will be called ixp4xx-beeper.
109 config INPUT_COBALT_BTNS
110 tristate "Cobalt button interface"
111 depends on MIPS_COBALT
114 Say Y here if you want to support MIPS Cobalt button interface.
116 To compile this driver as a module, choose M here: the
117 module will be called cobalt_btns.
119 config INPUT_WISTRON_BTNS
120 tristate "x86 Wistron laptop button interface"
121 depends on X86 && !X86_64
123 select INPUT_SPARSEKMAP
126 select CHECK_SIGNATURE
128 Say Y here for support of Wistron laptop button interfaces, used on
129 laptops of various brands, including Acer and Fujitsu-Siemens. If
130 available, mail and wifi LEDs will be controllable via /sys/class/leds.
132 To compile this driver as a module, choose M here: the module will
133 be called wistron_btns.
135 config INPUT_ATLAS_BTNS
136 tristate "x86 Atlas button interface"
137 depends on X86 && ACPI
139 Say Y here for support of Atlas wallmount touchscreen buttons.
140 The events will show up as scancodes F1 through F9 via evdev.
142 To compile this driver as a module, choose M here: the module will
143 be called atlas_btns.
145 config INPUT_ATI_REMOTE
146 tristate "ATI / X10 USB RF remote control"
147 depends on USB_ARCH_HAS_HCD
150 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
151 These are RF remotes with USB receivers.
152 The ATI remote comes with many of ATI's All-In-Wonder video cards.
153 The X10 "Lola" remote is available at:
154 <http://www.x10.com/products/lola_sg1.htm>
155 This driver provides mouse pointer, left and right mouse buttons,
156 and maps all the other remote buttons to keypress events.
158 To compile this driver as a module, choose M here: the module will be
161 config INPUT_ATI_REMOTE2
162 tristate "ATI / Philips USB RF remote control"
163 depends on USB_ARCH_HAS_HCD
166 Say Y here if you want to use an ATI or Philips USB RF remote control.
167 These are RF remotes with USB receivers.
168 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
169 and is also available as a separate product.
170 This driver provides mouse pointer, left and right mouse buttons,
171 and maps all the other remote buttons to keypress events.
173 To compile this driver as a module, choose M here: the module will be
176 config INPUT_KEYSPAN_REMOTE
177 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
178 depends on EXPERIMENTAL
179 depends on USB_ARCH_HAS_HCD
182 Say Y here if you want to use a Keyspan DMR USB remote control.
183 Currently only the UIA-11 type of receiver has been tested. The tag
184 on the receiver that connects to the USB port should have a P/N that
185 will tell you what type of DMR you have. The UIA-10 type is not
186 supported at this time. This driver maps all buttons to keypress
189 To compile this driver as a module, choose M here: the module will
190 be called keyspan_remote.
192 config INPUT_POWERMATE
193 tristate "Griffin PowerMate and Contour Jog support"
194 depends on USB_ARCH_HAS_HCD
197 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
198 These are aluminum dials which can measure clockwise and anticlockwise
199 rotation. The dial also acts as a pushbutton. The base contains an LED
200 which can be instructed to pulse or to switch to a particular intensity.
202 You can download userspace tools from
203 <http://sowerbutts.com/powermate/>.
205 To compile this driver as a module, choose M here: the
206 module will be called powermate.
209 tristate "Yealink usb-p1k voip phone"
210 depends on EXPERIMENTAL
211 depends on USB_ARCH_HAS_HCD
214 Say Y here if you want to enable keyboard and LCD functions of the
215 Yealink usb-p1k usb phones. The audio part is enabled by the generic
216 usb sound driver, so you might want to enable that as well.
218 For information about how to use these additional functions, see
219 <file:Documentation/input/yealink.txt>.
221 To compile this driver as a module, choose M here: the module will be
225 tristate "C-Media CM109 USB I/O Controller"
226 depends on EXPERIMENTAL
227 depends on USB_ARCH_HAS_HCD
230 Say Y here if you want to enable keyboard and buzzer functions of the
231 C-Media CM109 usb phones. The audio part is enabled by the generic
232 usb sound driver, so you might want to enable that as well.
234 To compile this driver as a module, choose M here: the module will be
237 config INPUT_TWL4030_PWRBUTTON
238 tristate "TWL4030 Power button Driver"
239 depends on TWL4030_CORE
241 Say Y here if you want to enable power key reporting via the
242 TWL4030 family of chips.
244 To compile this driver as a module, choose M here. The module will
245 be called twl4030_pwrbutton.
247 config INPUT_TWL4030_VIBRA
248 tristate "Support for TWL4030 Vibrator"
249 depends on TWL4030_CORE
251 select INPUT_FF_MEMLESS
253 This option enables support for TWL4030 Vibrator Driver.
255 To compile this driver as a module, choose M here. The module will
256 be called twl4030_vibra.
259 tristate "User level driver support"
261 Say Y here if you want to support user level drivers for input
262 subsystem accessible under char device 10:223 - /dev/input/uinput.
264 To compile this driver as a module, choose M here: the
265 module will be called uinput.
267 config INPUT_SGI_BTNS
268 tristate "SGI Indy/O2 volume button interface"
269 depends on SGI_IP22 || SGI_IP32
272 Say Y here if you want to support SGI Indy/O2 volume button interface.
274 To compile this driver as a module, choose M here: the
275 module will be called sgi_btns.
277 config INPUT_WINBOND_CIR
278 tristate "Winbond IR remote control"
279 depends on X86 && PNP
285 Say Y here if you want to use the IR remote functionality found
286 in some Winbond SuperI/O chips. Currently only the WPCD376I
287 chip is supported (included in some Intel Media series motherboards).
289 IR Receive and wake-on-IR from suspend and power-off is currently
292 To compile this driver as a module, choose M here: the module will be
296 tristate "HP SDC Real Time Clock"
297 depends on (GSC || HP300) && SERIO
300 Say Y here if you want to support the built-in real time clock
301 of the HP SDC controller.
303 config INPUT_PCF50633_PMU
304 tristate "PCF50633 PMU events"
305 depends on MFD_PCF50633
307 Say Y to include support for delivering PMU events via input
308 layer on NXP PCF50633.
311 tristate "PCF8574 Keypad input device"
312 depends on I2C && EXPERIMENTAL
314 Say Y here if you want to support a keypad connetced via I2C
317 To compile this driver as a module, choose M here: the
318 module will be called pcf8574_keypad.
320 config INPUT_GPIO_ROTARY_ENCODER
321 tristate "Rotary encoders connected to GPIO pins"
322 depends on GPIOLIB && GENERIC_GPIO
324 Say Y here to add support for rotary encoders connected to GPIO lines.
325 Check file:Documentation/input/rotary-encoder.txt for more
328 To compile this driver as a module, choose M here: the
329 module will be called rotary_encoder.
331 config INPUT_RB532_BUTTON
332 tristate "Mikrotik Routerboard 532 button interface"
333 depends on MIKROTIK_RB532
334 depends on GPIOLIB && GENERIC_GPIO
337 Say Y here if you want support for the S1 button built into
338 Mikrotik's Routerboard 532.
340 To compile this driver as a module, choose M here: the
341 module will be called rb532_button.
343 config INPUT_DM355EVM
344 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
345 depends on MFD_DM355EVM_MSP
346 select INPUT_SPARSEKMAP
348 Supports the pushbuttons and IR remote used with
351 To compile this driver as a module, choose M here: the
352 module will be called dm355evm_keys.
354 config INPUT_BFIN_ROTARY
355 tristate "Blackfin Rotary support"
356 depends on BF54x || BF52x
358 Say Y here if you want to use the Blackfin Rotary.
360 To compile this driver as a module, choose M here: the
361 module will be called bfin-rotary.
363 config INPUT_WM831X_ON
364 tristate "WM831X ON pin"
365 depends on MFD_WM831X
367 Support the ON pin of WM831X PMICs as an input device
368 reporting power button status.
370 To compile this driver as a module, choose M here: the module
371 will be called wm831x_on.
374 tristate "Motorola EZX PCAP misc input events"
377 Say Y here if you want to use Power key and Headphone button
378 on Motorola EZX phones.
380 To compile this driver as a module, choose M here: the
381 module will be called pcap_keys.