]>
Commit | Line | Data |
---|---|---|
1 | # | |
2 | # Input misc drivers configuration | |
3 | # | |
4 | menuconfig INPUT_MISC | |
5 | bool "Miscellaneous devices" | |
6 | help | |
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. | |
10 | ||
11 | If unsure, say Y. | |
12 | ||
13 | if INPUT_MISC | |
14 | ||
15 | config INPUT_88PM860X_ONKEY | |
16 | tristate "88PM860x ONKEY support" | |
17 | depends on MFD_88PM860X | |
18 | help | |
19 | Support the ONKEY of Marvell 88PM860x PMICs as an input device | |
20 | reporting power button status. | |
21 | ||
22 | To compile this driver as a module, choose M here: the module | |
23 | will be called 88pm860x_onkey. | |
24 | ||
25 | config INPUT_AB8500_PONKEY | |
26 | tristate "AB8500 Pon (PowerOn) Key" | |
27 | depends on AB8500_CORE | |
28 | help | |
29 | Say Y here to use the PowerOn Key for ST-Ericsson's AB8500 | |
30 | Mix-Sig PMIC. | |
31 | ||
32 | To compile this driver as a module, choose M here: the module | |
33 | will be called ab8500-ponkey. | |
34 | ||
35 | config INPUT_AD714X | |
36 | tristate "Analog Devices AD714x Capacitance Touch Sensor" | |
37 | help | |
38 | Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. | |
39 | ||
40 | You should select a bus connection too. | |
41 | ||
42 | To compile this driver as a module, choose M here: the | |
43 | module will be called ad714x. | |
44 | ||
45 | config INPUT_AD714X_I2C | |
46 | tristate "support I2C bus connection" | |
47 | depends on INPUT_AD714X && I2C | |
48 | default y | |
49 | help | |
50 | Say Y here if you have AD7142/AD7147 hooked to an I2C bus. | |
51 | ||
52 | To compile this driver as a module, choose M here: the | |
53 | module will be called ad714x-i2c. | |
54 | ||
55 | config INPUT_AD714X_SPI | |
56 | tristate "support SPI bus connection" | |
57 | depends on INPUT_AD714X && SPI | |
58 | default y | |
59 | help | |
60 | Say Y here if you have AD7142/AD7147 hooked to a SPI bus. | |
61 | ||
62 | To compile this driver as a module, choose M here: the | |
63 | module will be called ad714x-spi. | |
64 | ||
65 | config INPUT_PCSPKR | |
66 | tristate "PC Speaker support" | |
67 | depends on PCSPKR_PLATFORM | |
68 | help | |
69 | Say Y here if you want the standard PC Speaker to be used for | |
70 | bells and whistles. | |
71 | ||
72 | If unsure, say Y. | |
73 | ||
74 | To compile this driver as a module, choose M here: the | |
75 | module will be called pcspkr. | |
76 | ||
77 | config INPUT_SPARCSPKR | |
78 | tristate "SPARC Speaker support" | |
79 | depends on PCI && SPARC64 | |
80 | help | |
81 | Say Y here if you want the standard Speaker on Sparc PCI systems | |
82 | to be used for bells and whistles. | |
83 | ||
84 | If unsure, say Y. | |
85 | ||
86 | To compile this driver as a module, choose M here: the | |
87 | module will be called sparcspkr. | |
88 | ||
89 | config INPUT_M68K_BEEP | |
90 | tristate "M68k Beeper support" | |
91 | depends on M68K | |
92 | ||
93 | config INPUT_MAX8925_ONKEY | |
94 | tristate "MAX8925 ONKEY support" | |
95 | depends on MFD_MAX8925 | |
96 | help | |
97 | Support the ONKEY of MAX8925 PMICs as an input device | |
98 | reporting power button status. | |
99 | ||
100 | To compile this driver as a module, choose M here: the module | |
101 | will be called max8925_onkey. | |
102 | ||
103 | config INPUT_APANEL | |
104 | tristate "Fujitsu Lifebook Application Panel buttons" | |
105 | depends on X86 && I2C && LEDS_CLASS | |
106 | select INPUT_POLLDEV | |
107 | select CHECK_SIGNATURE | |
108 | help | |
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. | |
113 | ||
114 | To compile this driver as a module, choose M here: the module will | |
115 | be called apanel. | |
116 | ||
117 | config INPUT_IXP4XX_BEEPER | |
118 | tristate "IXP4XX Beeper support" | |
119 | depends on ARCH_IXP4XX | |
120 | help | |
121 | If you say yes here, you can connect a beeper to the | |
122 | ixp4xx gpio pins. This is used by the LinkSys NSLU2. | |
123 | ||
124 | If unsure, say Y. | |
125 | ||
126 | To compile this driver as a module, choose M here: the | |
127 | module will be called ixp4xx-beeper. | |
128 | ||
129 | config INPUT_COBALT_BTNS | |
130 | tristate "Cobalt button interface" | |
131 | depends on MIPS_COBALT | |
132 | select INPUT_POLLDEV | |
133 | help | |
134 | Say Y here if you want to support MIPS Cobalt button interface. | |
135 | ||
136 | To compile this driver as a module, choose M here: the | |
137 | module will be called cobalt_btns. | |
138 | ||
139 | config INPUT_WISTRON_BTNS | |
140 | tristate "x86 Wistron laptop button interface" | |
141 | depends on X86 && !X86_64 | |
142 | select INPUT_POLLDEV | |
143 | select INPUT_SPARSEKMAP | |
144 | select NEW_LEDS | |
145 | select LEDS_CLASS | |
146 | select CHECK_SIGNATURE | |
147 | help | |
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. | |
151 | ||
152 | To compile this driver as a module, choose M here: the module will | |
153 | be called wistron_btns. | |
154 | ||
155 | config INPUT_ATLAS_BTNS | |
156 | tristate "x86 Atlas button interface" | |
157 | depends on X86 && ACPI | |
158 | help | |
159 | Say Y here for support of Atlas wallmount touchscreen buttons. | |
160 | The events will show up as scancodes F1 through F9 via evdev. | |
161 | ||
162 | To compile this driver as a module, choose M here: the module will | |
163 | be called atlas_btns. | |
164 | ||
165 | config INPUT_ATI_REMOTE | |
166 | tristate "ATI / X10 USB RF remote control" | |
167 | depends on USB_ARCH_HAS_HCD | |
168 | select USB | |
169 | help | |
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. | |
177 | ||
178 | To compile this driver as a module, choose M here: the module will be | |
179 | called ati_remote. | |
180 | ||
181 | config INPUT_ATI_REMOTE2 | |
182 | tristate "ATI / Philips USB RF remote control" | |
183 | depends on USB_ARCH_HAS_HCD | |
184 | select USB | |
185 | help | |
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. | |
192 | ||
193 | To compile this driver as a module, choose M here: the module will be | |
194 | called ati_remote2. | |
195 | ||
196 | config INPUT_KEYSPAN_REMOTE | |
197 | tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" | |
198 | depends on EXPERIMENTAL | |
199 | depends on USB_ARCH_HAS_HCD | |
200 | select USB | |
201 | help | |
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 | |
207 | events. | |
208 | ||
209 | To compile this driver as a module, choose M here: the module will | |
210 | be called keyspan_remote. | |
211 | ||
212 | config INPUT_POWERMATE | |
213 | tristate "Griffin PowerMate and Contour Jog support" | |
214 | depends on USB_ARCH_HAS_HCD | |
215 | select USB | |
216 | help | |
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. | |
221 | ||
222 | You can download userspace tools from | |
223 | <http://sowerbutts.com/powermate/>. | |
224 | ||
225 | To compile this driver as a module, choose M here: the | |
226 | module will be called powermate. | |
227 | ||
228 | config INPUT_YEALINK | |
229 | tristate "Yealink usb-p1k voip phone" | |
230 | depends on EXPERIMENTAL | |
231 | depends on USB_ARCH_HAS_HCD | |
232 | select USB | |
233 | help | |
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. | |
237 | ||
238 | For information about how to use these additional functions, see | |
239 | <file:Documentation/input/yealink.txt>. | |
240 | ||
241 | To compile this driver as a module, choose M here: the module will be | |
242 | called yealink. | |
243 | ||
244 | config INPUT_CM109 | |
245 | tristate "C-Media CM109 USB I/O Controller" | |
246 | depends on EXPERIMENTAL | |
247 | depends on USB_ARCH_HAS_HCD | |
248 | select USB | |
249 | help | |
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. | |
253 | ||
254 | To compile this driver as a module, choose M here: the module will be | |
255 | called cm109. | |
256 | ||
257 | config INPUT_TWL4030_PWRBUTTON | |
258 | tristate "TWL4030 Power button Driver" | |
259 | depends on TWL4030_CORE | |
260 | help | |
261 | Say Y here if you want to enable power key reporting via the | |
262 | TWL4030 family of chips. | |
263 | ||
264 | To compile this driver as a module, choose M here. The module will | |
265 | be called twl4030_pwrbutton. | |
266 | ||
267 | config INPUT_TWL4030_VIBRA | |
268 | tristate "Support for TWL4030 Vibrator" | |
269 | depends on TWL4030_CORE | |
270 | select TWL4030_CODEC | |
271 | select INPUT_FF_MEMLESS | |
272 | help | |
273 | This option enables support for TWL4030 Vibrator Driver. | |
274 | ||
275 | To compile this driver as a module, choose M here. The module will | |
276 | be called twl4030_vibra. | |
277 | ||
278 | config INPUT_UINPUT | |
279 | tristate "User level driver support" | |
280 | help | |
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. | |
283 | ||
284 | To compile this driver as a module, choose M here: the | |
285 | module will be called uinput. | |
286 | ||
287 | config INPUT_SGI_BTNS | |
288 | tristate "SGI Indy/O2 volume button interface" | |
289 | depends on SGI_IP22 || SGI_IP32 | |
290 | select INPUT_POLLDEV | |
291 | help | |
292 | Say Y here if you want to support SGI Indy/O2 volume button interface. | |
293 | ||
294 | To compile this driver as a module, choose M here: the | |
295 | module will be called sgi_btns. | |
296 | ||
297 | config HP_SDC_RTC | |
298 | tristate "HP SDC Real Time Clock" | |
299 | depends on (GSC || HP300) && SERIO | |
300 | select HP_SDC | |
301 | help | |
302 | Say Y here if you want to support the built-in real time clock | |
303 | of the HP SDC controller. | |
304 | ||
305 | config INPUT_PCF50633_PMU | |
306 | tristate "PCF50633 PMU events" | |
307 | depends on MFD_PCF50633 | |
308 | help | |
309 | Say Y to include support for delivering PMU events via input | |
310 | layer on NXP PCF50633. | |
311 | ||
312 | config INPUT_PCF8574 | |
313 | tristate "PCF8574 Keypad input device" | |
314 | depends on I2C && EXPERIMENTAL | |
315 | help | |
316 | Say Y here if you want to support a keypad connetced via I2C | |
317 | with a PCF8574. | |
318 | ||
319 | To compile this driver as a module, choose M here: the | |
320 | module will be called pcf8574_keypad. | |
321 | ||
322 | config INPUT_PWM_BEEPER | |
323 | tristate "PWM beeper support" | |
324 | depends on HAVE_PWM | |
325 | help | |
326 | Say Y here to get support for PWM based beeper devices. | |
327 | ||
328 | If unsure, say N. | |
329 | ||
330 | To compile this driver as a module, choose M here: the module will be | |
331 | called pwm-beeper. | |
332 | ||
333 | config INPUT_PMIC8XXX_PWRKEY | |
334 | tristate "PMIC8XXX power key support" | |
335 | depends on MFD_PM8XXX | |
336 | help | |
337 | Say Y here if you want support for the PMIC8XXX power key. | |
338 | ||
339 | If unsure, say N. | |
340 | ||
341 | To compile this driver as a module, choose M here: the | |
342 | module will be called pmic8xxx-pwrkey. | |
343 | ||
344 | config INPUT_GPIO_ROTARY_ENCODER | |
345 | tristate "Rotary encoders connected to GPIO pins" | |
346 | depends on GPIOLIB && GENERIC_GPIO | |
347 | help | |
348 | Say Y here to add support for rotary encoders connected to GPIO lines. | |
349 | Check file:Documentation/input/rotary-encoder.txt for more | |
350 | information. | |
351 | ||
352 | To compile this driver as a module, choose M here: the | |
353 | module will be called rotary_encoder. | |
354 | ||
355 | config INPUT_RB532_BUTTON | |
356 | tristate "Mikrotik Routerboard 532 button interface" | |
357 | depends on MIKROTIK_RB532 | |
358 | depends on GPIOLIB && GENERIC_GPIO | |
359 | select INPUT_POLLDEV | |
360 | help | |
361 | Say Y here if you want support for the S1 button built into | |
362 | Mikrotik's Routerboard 532. | |
363 | ||
364 | To compile this driver as a module, choose M here: the | |
365 | module will be called rb532_button. | |
366 | ||
367 | config INPUT_DM355EVM | |
368 | tristate "TI DaVinci DM355 EVM Keypad and IR Remote" | |
369 | depends on MFD_DM355EVM_MSP | |
370 | select INPUT_SPARSEKMAP | |
371 | help | |
372 | Supports the pushbuttons and IR remote used with | |
373 | the DM355 EVM board. | |
374 | ||
375 | To compile this driver as a module, choose M here: the | |
376 | module will be called dm355evm_keys. | |
377 | ||
378 | config INPUT_BFIN_ROTARY | |
379 | tristate "Blackfin Rotary support" | |
380 | depends on BF54x || BF52x | |
381 | help | |
382 | Say Y here if you want to use the Blackfin Rotary. | |
383 | ||
384 | To compile this driver as a module, choose M here: the | |
385 | module will be called bfin-rotary. | |
386 | ||
387 | config INPUT_WM831X_ON | |
388 | tristate "WM831X ON pin" | |
389 | depends on MFD_WM831X | |
390 | help | |
391 | Support the ON pin of WM831X PMICs as an input device | |
392 | reporting power button status. | |
393 | ||
394 | To compile this driver as a module, choose M here: the module | |
395 | will be called wm831x_on. | |
396 | ||
397 | config INPUT_PCAP | |
398 | tristate "Motorola EZX PCAP misc input events" | |
399 | depends on EZX_PCAP | |
400 | help | |
401 | Say Y here if you want to use Power key and Headphone button | |
402 | on Motorola EZX phones. | |
403 | ||
404 | To compile this driver as a module, choose M here: the | |
405 | module will be called pcap_keys. | |
406 | ||
407 | config INPUT_ADXL34X | |
408 | tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" | |
409 | default n | |
410 | help | |
411 | Say Y here if you have a Accelerometer interface using the | |
412 | ADXL345/6 controller, and your board-specific initialization | |
413 | code includes that in its table of devices. | |
414 | ||
415 | This driver can use either I2C or SPI communication to the | |
416 | ADXL345/6 controller. Select the appropriate method for | |
417 | your system. | |
418 | ||
419 | If unsure, say N (but it's safe to say "Y"). | |
420 | ||
421 | To compile this driver as a module, choose M here: the | |
422 | module will be called adxl34x. | |
423 | ||
424 | config INPUT_ADXL34X_I2C | |
425 | tristate "support I2C bus connection" | |
426 | depends on INPUT_ADXL34X && I2C | |
427 | default y | |
428 | help | |
429 | Say Y here if you have ADXL345/6 hooked to an I2C bus. | |
430 | ||
431 | To compile this driver as a module, choose M here: the | |
432 | module will be called adxl34x-i2c. | |
433 | ||
434 | config INPUT_ADXL34X_SPI | |
435 | tristate "support SPI bus connection" | |
436 | depends on INPUT_ADXL34X && SPI | |
437 | default y | |
438 | help | |
439 | Say Y here if you have ADXL345/6 hooked to a SPI bus. | |
440 | ||
441 | To compile this driver as a module, choose M here: the | |
442 | module will be called adxl34x-spi. | |
443 | ||
444 | config INPUT_CMA3000 | |
445 | tristate "VTI CMA3000 Tri-axis accelerometer" | |
446 | help | |
447 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
448 | driver | |
449 | ||
450 | This driver currently only supports I2C interface to the | |
451 | controller. Also select the I2C method. | |
452 | ||
453 | If unsure, say N | |
454 | ||
455 | To compile this driver as a module, choose M here: the | |
456 | module will be called cma3000_d0x. | |
457 | ||
458 | config INPUT_CMA3000_I2C | |
459 | tristate "Support I2C bus connection" | |
460 | depends on INPUT_CMA3000 && I2C | |
461 | help | |
462 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
463 | through I2C interface. | |
464 | ||
465 | To compile this driver as a module, choose M here: the | |
466 | module will be called cma3000_d0x_i2c. | |
467 | ||
468 | config INPUT_XEN_KBDDEV_FRONTEND | |
469 | tristate "Xen virtual keyboard and mouse support" | |
470 | depends on XEN_FBDEV_FRONTEND | |
471 | default y | |
472 | select XEN_XENBUS_FRONTEND | |
473 | help | |
474 | This driver implements the front-end of the Xen virtual | |
475 | keyboard and mouse device driver. It communicates with a back-end | |
476 | in another domain. | |
477 | ||
478 | To compile this driver as a module, choose M here: the | |
479 | module will be called xen-kbdfront. | |
480 | ||
481 | endif |