Commit | Line | Data |
---|---|---|
1da177e4 LT |
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 | ||
69854031 HZ |
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 | ||
77686517 SI |
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 | ||
31a62963 BW |
35 | config INPUT_AD714X |
36 | tristate "Analog Devices AD714x Capacitance Touch Sensor" | |
37 | help | |
6c04d7b3 | 38 | Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. |
31a62963 BW |
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 | ||
1da177e4 LT |
65 | config INPUT_PCSPKR |
66 | tristate "PC Speaker support" | |
e5e1d3cb | 67 | depends on PCSPKR_PLATFORM |
1da177e4 LT |
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 | ||
11205bb6 AM |
77 | config INPUT_PM8XXX_VIBRATOR |
78 | tristate "Qualcomm PM8XXX vibrator support" | |
79 | depends on MFD_PM8XXX | |
80 | select INPUT_FF_MEMLESS | |
81 | help | |
82 | This option enables device driver support for the vibrator | |
83 | on Qualcomm PM8xxx chip. This driver supports ff-memless interface | |
84 | from input framework. | |
85 | ||
86 | To compile this driver as module, choose M here: the | |
87 | module will be called pm8xxx-vibrator. | |
88 | ||
89 | config INPUT_PMIC8XXX_PWRKEY | |
90 | tristate "PMIC8XXX power key support" | |
91 | depends on MFD_PM8XXX | |
92 | help | |
93 | Say Y here if you want support for the PMIC8XXX power key. | |
94 | ||
95 | If unsure, say N. | |
96 | ||
97 | To compile this driver as a module, choose M here: the | |
98 | module will be called pmic8xxx-pwrkey. | |
99 | ||
1da177e4 LT |
100 | config INPUT_SPARCSPKR |
101 | tristate "SPARC Speaker support" | |
a2bd4fd1 | 102 | depends on PCI && SPARC64 |
1da177e4 LT |
103 | help |
104 | Say Y here if you want the standard Speaker on Sparc PCI systems | |
105 | to be used for bells and whistles. | |
106 | ||
107 | If unsure, say Y. | |
108 | ||
109 | To compile this driver as a module, choose M here: the | |
110 | module will be called sparcspkr. | |
111 | ||
112 | config INPUT_M68K_BEEP | |
113 | tristate "M68k Beeper support" | |
114 | depends on M68K | |
115 | ||
3734574c HZ |
116 | config INPUT_MAX8925_ONKEY |
117 | tristate "MAX8925 ONKEY support" | |
118 | depends on MFD_MAX8925 | |
119 | help | |
120 | Support the ONKEY of MAX8925 PMICs as an input device | |
121 | reporting power button status. | |
122 | ||
123 | To compile this driver as a module, choose M here: the module | |
124 | will be called max8925_onkey. | |
125 | ||
3ead8b5d EM |
126 | config INPUT_MMA8450 |
127 | tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" | |
128 | depends on I2C | |
129 | select INPUT_POLLDEV | |
130 | help | |
131 | Say Y here if you want to support Freescale's MMA8450 Accelerometer | |
132 | through I2C interface. | |
133 | ||
134 | To compile this driver as a module, choose M here: the | |
135 | module will be called mma8450. | |
136 | ||
631b16e8 JL |
137 | config INPUT_MPU3050 |
138 | tristate "MPU3050 Triaxial gyroscope sensor" | |
139 | depends on I2C | |
140 | help | |
141 | Say Y here if you want to support InvenSense MPU3050 | |
142 | connected via an I2C bus. | |
143 | ||
144 | To compile this driver as a module, choose M here: the | |
145 | module will be called mpu3050. | |
146 | ||
52fe0cdb SH |
147 | config INPUT_APANEL |
148 | tristate "Fujitsu Lifebook Application Panel buttons" | |
19131305 | 149 | depends on X86 && I2C && LEDS_CLASS |
52fe0cdb SH |
150 | select INPUT_POLLDEV |
151 | select CHECK_SIGNATURE | |
152 | help | |
153 | Say Y here for support of the Application Panel buttons, used on | |
154 | Fujitsu Lifebook. These are attached to the mainboard through | |
19131305 RD |
155 | an SMBus interface managed by the I2C Intel ICH (i801) driver, |
156 | which you should also build for this kernel. | |
52fe0cdb SH |
157 | |
158 | To compile this driver as a module, choose M here: the module will | |
159 | be called apanel. | |
160 | ||
ba0acb5e DT |
161 | config INPUT_IXP4XX_BEEPER |
162 | tristate "IXP4XX Beeper support" | |
163 | depends on ARCH_IXP4XX | |
164 | help | |
165 | If you say yes here, you can connect a beeper to the | |
166 | ixp4xx gpio pins. This is used by the LinkSys NSLU2. | |
167 | ||
168 | If unsure, say Y. | |
169 | ||
170 | To compile this driver as a module, choose M here: the | |
171 | module will be called ixp4xx-beeper. | |
172 | ||
bebb8a2b YY |
173 | config INPUT_COBALT_BTNS |
174 | tristate "Cobalt button interface" | |
175 | depends on MIPS_COBALT | |
3d29cdff | 176 | select INPUT_POLLDEV |
bebb8a2b YY |
177 | help |
178 | Say Y here if you want to support MIPS Cobalt button interface. | |
179 | ||
180 | To compile this driver as a module, choose M here: the | |
181 | module will be called cobalt_btns. | |
182 | ||
5fc14680 DT |
183 | config INPUT_WISTRON_BTNS |
184 | tristate "x86 Wistron laptop button interface" | |
e9fb028e | 185 | depends on X86 && !X86_64 |
c2554c91 | 186 | select INPUT_POLLDEV |
e97af4cb | 187 | select INPUT_SPARSEKMAP |
389679d8 EP |
188 | select NEW_LEDS |
189 | select LEDS_CLASS | |
928923c7 | 190 | select CHECK_SIGNATURE |
5fc14680 | 191 | help |
01dd2fbf | 192 | Say Y here for support of Wistron laptop button interfaces, used on |
389679d8 | 193 | laptops of various brands, including Acer and Fujitsu-Siemens. If |
01dd2fbf | 194 | available, mail and wifi LEDs will be controllable via /sys/class/leds. |
5fc14680 DT |
195 | |
196 | To compile this driver as a module, choose M here: the module will | |
197 | be called wistron_btns. | |
198 | ||
31ea7ff0 JK |
199 | config INPUT_ATLAS_BTNS |
200 | tristate "x86 Atlas button interface" | |
201 | depends on X86 && ACPI | |
202 | help | |
203 | Say Y here for support of Atlas wallmount touchscreen buttons. | |
204 | The events will show up as scancodes F1 through F9 via evdev. | |
205 | ||
206 | To compile this driver as a module, choose M here: the module will | |
207 | be called atlas_btns. | |
208 | ||
ba0acb5e DT |
209 | config INPUT_ATI_REMOTE |
210 | tristate "ATI / X10 USB RF remote control" | |
7a86edef | 211 | depends on USB_ARCH_HAS_HCD |
ba0acb5e | 212 | select USB |
01387959 | 213 | help |
ba0acb5e DT |
214 | Say Y here if you want to use an ATI or X10 "Lola" USB remote control. |
215 | These are RF remotes with USB receivers. | |
216 | The ATI remote comes with many of ATI's All-In-Wonder video cards. | |
217 | The X10 "Lola" remote is available at: | |
218 | <http://www.x10.com/products/lola_sg1.htm> | |
219 | This driver provides mouse pointer, left and right mouse buttons, | |
220 | and maps all the other remote buttons to keypress events. | |
221 | ||
222 | To compile this driver as a module, choose M here: the module will be | |
223 | called ati_remote. | |
224 | ||
225 | config INPUT_ATI_REMOTE2 | |
226 | tristate "ATI / Philips USB RF remote control" | |
7a86edef | 227 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
228 | select USB |
229 | help | |
230 | Say Y here if you want to use an ATI or Philips USB RF remote control. | |
231 | These are RF remotes with USB receivers. | |
232 | ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards | |
233 | and is also available as a separate product. | |
234 | This driver provides mouse pointer, left and right mouse buttons, | |
235 | and maps all the other remote buttons to keypress events. | |
236 | ||
237 | To compile this driver as a module, choose M here: the module will be | |
238 | called ati_remote2. | |
239 | ||
240 | config INPUT_KEYSPAN_REMOTE | |
241 | tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" | |
242 | depends on EXPERIMENTAL | |
7a86edef | 243 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
244 | select USB |
245 | help | |
246 | Say Y here if you want to use a Keyspan DMR USB remote control. | |
247 | Currently only the UIA-11 type of receiver has been tested. The tag | |
248 | on the receiver that connects to the USB port should have a P/N that | |
249 | will tell you what type of DMR you have. The UIA-10 type is not | |
250 | supported at this time. This driver maps all buttons to keypress | |
251 | events. | |
01387959 | 252 | |
ba0acb5e DT |
253 | To compile this driver as a module, choose M here: the module will |
254 | be called keyspan_remote. | |
255 | ||
e8e70d83 CH |
256 | config INPUT_KXTJ9 |
257 | tristate "Kionix KXTJ9 tri-axis digital accelerometer" | |
258 | depends on I2C | |
259 | help | |
260 | Say Y here to enable support for the Kionix KXTJ9 digital tri-axis | |
261 | accelerometer. | |
262 | ||
263 | To compile this driver as a module, choose M here: the module will | |
264 | be called kxtj9. | |
265 | ||
266 | config INPUT_KXTJ9_POLLED_MODE | |
267 | bool "Enable polling mode support" | |
268 | depends on INPUT_KXTJ9 | |
269 | select INPUT_POLLDEV | |
270 | help | |
271 | Say Y here if you need accelerometer to work in polling mode. | |
272 | ||
ba0acb5e DT |
273 | config INPUT_POWERMATE |
274 | tristate "Griffin PowerMate and Contour Jog support" | |
7a86edef | 275 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
276 | select USB |
277 | help | |
278 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | |
279 | These are aluminum dials which can measure clockwise and anticlockwise | |
280 | rotation. The dial also acts as a pushbutton. The base contains an LED | |
281 | which can be instructed to pulse or to switch to a particular intensity. | |
282 | ||
283 | You can download userspace tools from | |
284 | <http://sowerbutts.com/powermate/>. | |
01387959 AZ |
285 | |
286 | To compile this driver as a module, choose M here: the | |
ba0acb5e DT |
287 | module will be called powermate. |
288 | ||
289 | config INPUT_YEALINK | |
290 | tristate "Yealink usb-p1k voip phone" | |
247537b9 | 291 | depends on EXPERIMENTAL |
7a86edef | 292 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
293 | select USB |
294 | help | |
295 | Say Y here if you want to enable keyboard and LCD functions of the | |
296 | Yealink usb-p1k usb phones. The audio part is enabled by the generic | |
297 | usb sound driver, so you might want to enable that as well. | |
298 | ||
299 | For information about how to use these additional functions, see | |
300 | <file:Documentation/input/yealink.txt>. | |
301 | ||
302 | To compile this driver as a module, choose M here: the module will be | |
303 | called yealink. | |
01387959 | 304 | |
c04148f9 AH |
305 | config INPUT_CM109 |
306 | tristate "C-Media CM109 USB I/O Controller" | |
307 | depends on EXPERIMENTAL | |
308 | depends on USB_ARCH_HAS_HCD | |
309 | select USB | |
310 | help | |
311 | Say Y here if you want to enable keyboard and buzzer functions of the | |
312 | C-Media CM109 usb phones. The audio part is enabled by the generic | |
313 | usb sound driver, so you might want to enable that as well. | |
314 | ||
315 | To compile this driver as a module, choose M here: the module will be | |
316 | called cm109. | |
317 | ||
68d8bf04 FB |
318 | config INPUT_TWL4030_PWRBUTTON |
319 | tristate "TWL4030 Power button Driver" | |
320 | depends on TWL4030_CORE | |
321 | help | |
322 | Say Y here if you want to enable power key reporting via the | |
323 | TWL4030 family of chips. | |
324 | ||
325 | To compile this driver as a module, choose M here. The module will | |
326 | be called twl4030_pwrbutton. | |
327 | ||
3dd1b394 JV |
328 | config INPUT_TWL4030_VIBRA |
329 | tristate "Support for TWL4030 Vibrator" | |
330 | depends on TWL4030_CORE | |
331 | select TWL4030_CODEC | |
332 | select INPUT_FF_MEMLESS | |
333 | help | |
334 | This option enables support for TWL4030 Vibrator Driver. | |
335 | ||
336 | To compile this driver as a module, choose M here. The module will | |
337 | be called twl4030_vibra. | |
338 | ||
1da177e4 LT |
339 | config INPUT_UINPUT |
340 | tristate "User level driver support" | |
341 | help | |
342 | Say Y here if you want to support user level drivers for input | |
343 | subsystem accessible under char device 10:223 - /dev/input/uinput. | |
344 | ||
345 | To compile this driver as a module, choose M here: the | |
346 | module will be called uinput. | |
347 | ||
48ad88b1 TB |
348 | config INPUT_SGI_BTNS |
349 | tristate "SGI Indy/O2 volume button interface" | |
350 | depends on SGI_IP22 || SGI_IP32 | |
3bee2a04 TB |
351 | select INPUT_POLLDEV |
352 | help | |
48ad88b1 | 353 | Say Y here if you want to support SGI Indy/O2 volume button interface. |
3bee2a04 TB |
354 | |
355 | To compile this driver as a module, choose M here: the | |
48ad88b1 | 356 | module will be called sgi_btns. |
3bee2a04 | 357 | |
1da177e4 | 358 | config HP_SDC_RTC |
bebb8a2b | 359 | tristate "HP SDC Real Time Clock" |
d061ebd5 | 360 | depends on (GSC || HP300) && SERIO |
1da177e4 LT |
361 | select HP_SDC |
362 | help | |
363 | Say Y here if you want to support the built-in real time clock | |
364 | of the HP SDC controller. | |
365 | ||
1851b06a BR |
366 | config INPUT_PCF50633_PMU |
367 | tristate "PCF50633 PMU events" | |
368 | depends on MFD_PCF50633 | |
369 | help | |
370 | Say Y to include support for delivering PMU events via input | |
371 | layer on NXP PCF50633. | |
372 | ||
b91c4be7 BW |
373 | config INPUT_PCF8574 |
374 | tristate "PCF8574 Keypad input device" | |
375 | depends on I2C && EXPERIMENTAL | |
376 | help | |
377 | Say Y here if you want to support a keypad connetced via I2C | |
378 | with a PCF8574. | |
379 | ||
380 | To compile this driver as a module, choose M here: the | |
381 | module will be called pcf8574_keypad. | |
382 | ||
e22739d0 LPC |
383 | config INPUT_PWM_BEEPER |
384 | tristate "PWM beeper support" | |
385 | depends on HAVE_PWM | |
386 | help | |
387 | Say Y here to get support for PWM based beeper devices. | |
388 | ||
389 | If unsure, say N. | |
390 | ||
391 | To compile this driver as a module, choose M here: the module will be | |
392 | called pwm-beeper. | |
393 | ||
73969ff0 DM |
394 | config INPUT_GPIO_ROTARY_ENCODER |
395 | tristate "Rotary encoders connected to GPIO pins" | |
396 | depends on GPIOLIB && GENERIC_GPIO | |
397 | help | |
398 | Say Y here to add support for rotary encoders connected to GPIO lines. | |
492d0f95 | 399 | Check file:Documentation/input/rotary-encoder.txt for more |
73969ff0 DM |
400 | information. |
401 | ||
402 | To compile this driver as a module, choose M here: the | |
403 | module will be called rotary_encoder. | |
404 | ||
d9bdffd2 PS |
405 | config INPUT_RB532_BUTTON |
406 | tristate "Mikrotik Routerboard 532 button interface" | |
407 | depends on MIKROTIK_RB532 | |
408 | depends on GPIOLIB && GENERIC_GPIO | |
409 | select INPUT_POLLDEV | |
410 | help | |
411 | Say Y here if you want support for the S1 button built into | |
412 | Mikrotik's Routerboard 532. | |
413 | ||
414 | To compile this driver as a module, choose M here: the | |
415 | module will be called rb532_button. | |
416 | ||
eb990b55 DB |
417 | config INPUT_DM355EVM |
418 | tristate "TI DaVinci DM355 EVM Keypad and IR Remote" | |
419 | depends on MFD_DM355EVM_MSP | |
66040727 | 420 | select INPUT_SPARSEKMAP |
eb990b55 DB |
421 | help |
422 | Supports the pushbuttons and IR remote used with | |
423 | the DM355 EVM board. | |
424 | ||
425 | To compile this driver as a module, choose M here: the | |
426 | module will be called dm355evm_keys. | |
48329582 MH |
427 | |
428 | config INPUT_BFIN_ROTARY | |
429 | tristate "Blackfin Rotary support" | |
430 | depends on BF54x || BF52x | |
431 | help | |
432 | Say Y here if you want to use the Blackfin Rotary. | |
433 | ||
434 | To compile this driver as a module, choose M here: the | |
435 | module will be called bfin-rotary. | |
436 | ||
0c73b992 MB |
437 | config INPUT_WM831X_ON |
438 | tristate "WM831X ON pin" | |
439 | depends on MFD_WM831X | |
440 | help | |
441 | Support the ON pin of WM831X PMICs as an input device | |
442 | reporting power button status. | |
443 | ||
444 | To compile this driver as a module, choose M here: the module | |
445 | will be called wm831x_on. | |
446 | ||
d0a82132 DR |
447 | config INPUT_PCAP |
448 | tristate "Motorola EZX PCAP misc input events" | |
449 | depends on EZX_PCAP | |
450 | help | |
451 | Say Y here if you want to use Power key and Headphone button | |
452 | on Motorola EZX phones. | |
453 | ||
454 | To compile this driver as a module, choose M here: the | |
455 | module will be called pcap_keys. | |
456 | ||
e27c7292 MH |
457 | config INPUT_ADXL34X |
458 | tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" | |
459 | default n | |
460 | help | |
461 | Say Y here if you have a Accelerometer interface using the | |
462 | ADXL345/6 controller, and your board-specific initialization | |
463 | code includes that in its table of devices. | |
464 | ||
465 | This driver can use either I2C or SPI communication to the | |
466 | ADXL345/6 controller. Select the appropriate method for | |
467 | your system. | |
468 | ||
469 | If unsure, say N (but it's safe to say "Y"). | |
470 | ||
471 | To compile this driver as a module, choose M here: the | |
472 | module will be called adxl34x. | |
473 | ||
474 | config INPUT_ADXL34X_I2C | |
475 | tristate "support I2C bus connection" | |
476 | depends on INPUT_ADXL34X && I2C | |
477 | default y | |
478 | help | |
479 | Say Y here if you have ADXL345/6 hooked to an I2C bus. | |
480 | ||
481 | To compile this driver as a module, choose M here: the | |
482 | module will be called adxl34x-i2c. | |
483 | ||
484 | config INPUT_ADXL34X_SPI | |
485 | tristate "support SPI bus connection" | |
486 | depends on INPUT_ADXL34X && SPI | |
487 | default y | |
488 | help | |
489 | Say Y here if you have ADXL345/6 hooked to a SPI bus. | |
490 | ||
491 | To compile this driver as a module, choose M here: the | |
492 | module will be called adxl34x-spi. | |
493 | ||
b029ffaf H |
494 | config INPUT_CMA3000 |
495 | tristate "VTI CMA3000 Tri-axis accelerometer" | |
496 | help | |
497 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
498 | driver | |
499 | ||
500 | This driver currently only supports I2C interface to the | |
501 | controller. Also select the I2C method. | |
502 | ||
503 | If unsure, say N | |
504 | ||
505 | To compile this driver as a module, choose M here: the | |
506 | module will be called cma3000_d0x. | |
507 | ||
508 | config INPUT_CMA3000_I2C | |
509 | tristate "Support I2C bus connection" | |
510 | depends on INPUT_CMA3000 && I2C | |
511 | help | |
512 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
513 | through I2C interface. | |
514 | ||
515 | To compile this driver as a module, choose M here: the | |
516 | module will be called cma3000_d0x_i2c. | |
517 | ||
49851ca0 DT |
518 | config INPUT_XEN_KBDDEV_FRONTEND |
519 | tristate "Xen virtual keyboard and mouse support" | |
520 | depends on XEN_FBDEV_FRONTEND | |
521 | default y | |
522 | select XEN_XENBUS_FRONTEND | |
523 | help | |
524 | This driver implements the front-end of the Xen virtual | |
525 | keyboard and mouse device driver. It communicates with a back-end | |
526 | in another domain. | |
527 | ||
528 | To compile this driver as a module, choose M here: the | |
529 | module will be called xen-kbdfront. | |
530 | ||
1da177e4 | 531 | endif |