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