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.
11 If unsure, say Y.
13 if INPUT_MISC
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.
22 To compile this driver as a module, choose M here: the module
23 will be called 88pm860x_onkey.
25 config INPUT_88PM80X_ONKEY
26 tristate "88PM80x ONKEY support"
27 depends on MFD_88PM800
28 help
29 Support the ONKEY of Marvell 88PM80x PMICs as an input device
30 reporting power button status.
32 To compile this driver as a module, choose M here: the module
33 will be called 88pm80x_onkey.
35 config INPUT_AB8500_PONKEY
36 tristate "AB8500 Pon (PowerOn) Key"
37 depends on AB8500_CORE
38 help
39 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
40 Mix-Sig PMIC.
42 To compile this driver as a module, choose M here: the module
43 will be called ab8500-ponkey.
45 config INPUT_AD714X
46 tristate "Analog Devices AD714x Capacitance Touch Sensor"
47 help
48 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
50 You should select a bus connection too.
52 To compile this driver as a module, choose M here: the
53 module will be called ad714x.
55 config INPUT_AD714X_I2C
56 tristate "support I2C bus connection"
57 depends on INPUT_AD714X && I2C
58 default y
59 help
60 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
62 To compile this driver as a module, choose M here: the
63 module will be called ad714x-i2c.
65 config INPUT_AD714X_SPI
66 tristate "support SPI bus connection"
67 depends on INPUT_AD714X && SPI
68 default y
69 help
70 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
72 To compile this driver as a module, choose M here: the
73 module will be called ad714x-spi.
75 config INPUT_ARIZONA_HAPTICS
76 tristate "Arizona haptics support"
77 depends on MFD_ARIZONA && SND_SOC
78 select INPUT_FF_MEMLESS
79 help
80 Say Y to enable support for the haptics module in Arizona CODECs.
82 To compile this driver as a module, choose M here: the
83 module will be called arizona-haptics.
85 config INPUT_BMA150
86 tristate "BMA150/SMB380 acceleration sensor support"
87 depends on I2C
88 select INPUT_POLLDEV
89 help
90 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
91 acceleration sensor hooked to an I2C bus.
93 To compile this driver as a module, choose M here: the
94 module will be called bma150.
96 config INPUT_PCSPKR
97 tristate "PC Speaker support"
98 depends on PCSPKR_PLATFORM
99 help
100 Say Y here if you want the standard PC Speaker to be used for
101 bells and whistles.
103 If unsure, say Y.
105 To compile this driver as a module, choose M here: the
106 module will be called pcspkr.
108 config INPUT_PM8XXX_VIBRATOR
109 tristate "Qualcomm PM8XXX vibrator support"
110 depends on MFD_PM8XXX
111 select INPUT_FF_MEMLESS
112 help
113 This option enables device driver support for the vibrator
114 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
115 from input framework.
117 To compile this driver as module, choose M here: the
118 module will be called pm8xxx-vibrator.
120 config INPUT_PMIC8XXX_PWRKEY
121 tristate "PMIC8XXX power key support"
122 depends on MFD_PM8XXX
123 help
124 Say Y here if you want support for the PMIC8XXX power key.
126 If unsure, say N.
128 To compile this driver as a module, choose M here: the
129 module will be called pmic8xxx-pwrkey.
131 config INPUT_SPARCSPKR
132 tristate "SPARC Speaker support"
133 depends on PCI && SPARC64
134 help
135 Say Y here if you want the standard Speaker on Sparc PCI systems
136 to be used for bells and whistles.
138 If unsure, say Y.
140 To compile this driver as a module, choose M here: the
141 module will be called sparcspkr.
143 config INPUT_M68K_BEEP
144 tristate "M68k Beeper support"
145 depends on M68K
147 config INPUT_MAX8925_ONKEY
148 tristate "MAX8925 ONKEY support"
149 depends on MFD_MAX8925
150 help
151 Support the ONKEY of MAX8925 PMICs as an input device
152 reporting power button status.
154 To compile this driver as a module, choose M here: the module
155 will be called max8925_onkey.
157 config INPUT_MAX8997_HAPTIC
158 tristate "MAXIM MAX8997 haptic controller support"
159 depends on PWM && HAVE_PWM && MFD_MAX8997
160 select INPUT_FF_MEMLESS
161 help
162 This option enables device driver support for the haptic controller
163 on MAXIM MAX8997 chip. This driver supports ff-memless interface
164 from input framework.
166 To compile this driver as module, choose M here: the
167 module will be called max8997-haptic.
169 config INPUT_MC13783_PWRBUTTON
170 tristate "MC13783 ON buttons"
171 depends on MFD_MC13XXX
172 help
173 Support the ON buttons of MC13783 PMIC as an input device
174 reporting power button status.
176 To compile this driver as a module, choose M here: the module
177 will be called mc13783-pwrbutton.
179 config INPUT_MMA8450
180 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
181 depends on I2C
182 select INPUT_POLLDEV
183 help
184 Say Y here if you want to support Freescale's MMA8450 Accelerometer
185 through I2C interface.
187 To compile this driver as a module, choose M here: the
188 module will be called mma8450.
190 config INPUT_MPU3050
191 tristate "MPU3050 Triaxial gyroscope sensor"
192 depends on I2C
193 help
194 Say Y here if you want to support InvenSense MPU3050
195 connected via an I2C bus.
197 To compile this driver as a module, choose M here: the
198 module will be called mpu3050.
200 config INPUT_APANEL
201 tristate "Fujitsu Lifebook Application Panel buttons"
202 depends on X86 && I2C && LEDS_CLASS
203 select INPUT_POLLDEV
204 select CHECK_SIGNATURE
205 help
206 Say Y here for support of the Application Panel buttons, used on
207 Fujitsu Lifebook. These are attached to the mainboard through
208 an SMBus interface managed by the I2C Intel ICH (i801) driver,
209 which you should also build for this kernel.
211 To compile this driver as a module, choose M here: the module will
212 be called apanel.
214 config INPUT_GP2A
215 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
216 depends on I2C
217 depends on GPIOLIB
218 help
219 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
220 hooked to an I2C bus.
222 To compile this driver as a module, choose M here: the
223 module will be called gp2ap002a00f.
225 config INPUT_GPIO_BEEPER
226 tristate "Generic GPIO Beeper support"
227 depends on OF_GPIO
228 help
229 Say Y here if you have a beeper connected to a GPIO pin.
231 To compile this driver as a module, choose M here: the
232 module will be called gpio-beeper.
234 config INPUT_GPIO_TILT_POLLED
235 tristate "Polled GPIO tilt switch"
236 depends on GPIOLIB
237 select INPUT_POLLDEV
238 help
239 This driver implements support for tilt switches connected
240 to GPIO pins that are not capable of generating interrupts.
242 The list of gpios to use and the mapping of their states
243 to specific angles is done via platform data.
245 To compile this driver as a module, choose M here: the
246 module will be called gpio_tilt_polled.
248 config INPUT_IXP4XX_BEEPER
249 tristate "IXP4XX Beeper support"
250 depends on ARCH_IXP4XX
251 help
252 If you say yes here, you can connect a beeper to the
253 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
255 If unsure, say Y.
257 To compile this driver as a module, choose M here: the
258 module will be called ixp4xx-beeper.
260 config INPUT_COBALT_BTNS
261 tristate "Cobalt button interface"
262 depends on MIPS_COBALT
263 select INPUT_POLLDEV
264 help
265 Say Y here if you want to support MIPS Cobalt button interface.
267 To compile this driver as a module, choose M here: the
268 module will be called cobalt_btns.
270 config INPUT_WISTRON_BTNS
271 tristate "x86 Wistron laptop button interface"
272 depends on X86 && !X86_64
273 select INPUT_POLLDEV
274 select INPUT_SPARSEKMAP
275 select NEW_LEDS
276 select LEDS_CLASS
277 select CHECK_SIGNATURE
278 help
279 Say Y here for support of Wistron laptop button interfaces, used on
280 laptops of various brands, including Acer and Fujitsu-Siemens. If
281 available, mail and wifi LEDs will be controllable via /sys/class/leds.
283 To compile this driver as a module, choose M here: the module will
284 be called wistron_btns.
286 config INPUT_ATLAS_BTNS
287 tristate "x86 Atlas button interface"
288 depends on X86 && ACPI
289 help
290 Say Y here for support of Atlas wallmount touchscreen buttons.
291 The events will show up as scancodes F1 through F9 via evdev.
293 To compile this driver as a module, choose M here: the module will
294 be called atlas_btns.
296 config INPUT_ATI_REMOTE2
297 tristate "ATI / Philips USB RF remote control"
298 depends on USB_ARCH_HAS_HCD
299 select USB
300 help
301 Say Y here if you want to use an ATI or Philips USB RF remote control.
302 These are RF remotes with USB receivers.
303 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
304 and is also available as a separate product.
305 This driver provides mouse pointer, left and right mouse buttons,
306 and maps all the other remote buttons to keypress events.
308 To compile this driver as a module, choose M here: the module will be
309 called ati_remote2.
311 config INPUT_KEYCHORD
312 tristate "Key chord input driver support"
313 help
314 Say Y here if you want to enable the key chord driver
315 accessible at /dev/keychord. This driver can be used
316 for receiving notifications when client specified key
317 combinations are pressed.
319 To compile this driver as a module, choose M here: the
320 module will be called keychord.
322 config INPUT_KEYSPAN_REMOTE
323 tristate "Keyspan DMR USB remote control"
324 depends on USB_ARCH_HAS_HCD
325 select USB
326 help
327 Say Y here if you want to use a Keyspan DMR USB remote control.
328 Currently only the UIA-11 type of receiver has been tested. The tag
329 on the receiver that connects to the USB port should have a P/N that
330 will tell you what type of DMR you have. The UIA-10 type is not
331 supported at this time. This driver maps all buttons to keypress
332 events.
334 To compile this driver as a module, choose M here: the module will
335 be called keyspan_remote.
337 config INPUT_KXTJ9
338 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
339 depends on I2C
340 help
341 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
342 accelerometer.
344 To compile this driver as a module, choose M here: the module will
345 be called kxtj9.
347 config INPUT_KXTJ9_POLLED_MODE
348 bool "Enable polling mode support"
349 depends on INPUT_KXTJ9
350 select INPUT_POLLDEV
351 help
352 Say Y here if you need accelerometer to work in polling mode.
354 config INPUT_POWERMATE
355 tristate "Griffin PowerMate and Contour Jog support"
356 depends on USB_ARCH_HAS_HCD
357 select USB
358 help
359 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
360 These are aluminum dials which can measure clockwise and anticlockwise
361 rotation. The dial also acts as a pushbutton. The base contains an LED
362 which can be instructed to pulse or to switch to a particular intensity.
364 You can download userspace tools from
365 <http://sowerbutts.com/powermate/>.
367 To compile this driver as a module, choose M here: the
368 module will be called powermate.
370 config INPUT_YEALINK
371 tristate "Yealink usb-p1k voip phone"
372 depends on USB_ARCH_HAS_HCD
373 select USB
374 help
375 Say Y here if you want to enable keyboard and LCD functions of the
376 Yealink usb-p1k usb phones. The audio part is enabled by the generic
377 usb sound driver, so you might want to enable that as well.
379 For information about how to use these additional functions, see
380 <file:Documentation/input/yealink.txt>.
382 To compile this driver as a module, choose M here: the module will be
383 called yealink.
385 config INPUT_CM109
386 tristate "C-Media CM109 USB I/O Controller"
387 depends on USB_ARCH_HAS_HCD
388 select USB
389 help
390 Say Y here if you want to enable keyboard and buzzer functions of the
391 C-Media CM109 usb phones. The audio part is enabled by the generic
392 usb sound driver, so you might want to enable that as well.
394 To compile this driver as a module, choose M here: the module will be
395 called cm109.
397 config INPUT_RETU_PWRBUTTON
398 tristate "Retu Power button Driver"
399 depends on MFD_RETU
400 help
401 Say Y here if you want to enable power key reporting via the
402 Retu chips found in Nokia Internet Tablets (770, N800, N810).
404 To compile this driver as a module, choose M here. The module will
405 be called retu-pwrbutton.
407 config INPUT_TWL4030_PWRBUTTON
408 tristate "TWL4030 Power button Driver"
409 depends on TWL4030_CORE
410 help
411 Say Y here if you want to enable power key reporting via the
412 TWL4030 family of chips.
414 To compile this driver as a module, choose M here. The module will
415 be called twl4030_pwrbutton.
417 config INPUT_TWL4030_VIBRA
418 tristate "Support for TWL4030 Vibrator"
419 depends on TWL4030_CORE
420 select MFD_TWL4030_AUDIO
421 select INPUT_FF_MEMLESS
422 help
423 This option enables support for TWL4030 Vibrator Driver.
425 To compile this driver as a module, choose M here. The module will
426 be called twl4030_vibra.
428 config INPUT_TWL6040_VIBRA
429 tristate "Support for TWL6040 Vibrator"
430 depends on TWL6040_CORE
431 select INPUT_FF_MEMLESS
432 help
433 This option enables support for TWL6040 Vibrator Driver.
435 To compile this driver as a module, choose M here. The module will
436 be called twl6040_vibra.
438 config INPUT_UINPUT
439 tristate "User level driver support"
440 help
441 Say Y here if you want to support user level drivers for input
442 subsystem accessible under char device 10:223 - /dev/input/uinput.
444 To compile this driver as a module, choose M here: the
445 module will be called uinput.
447 config INPUT_SGI_BTNS
448 tristate "SGI Indy/O2 volume button interface"
449 depends on SGI_IP22 || SGI_IP32
450 select INPUT_POLLDEV
451 help
452 Say Y here if you want to support SGI Indy/O2 volume button interface.
454 To compile this driver as a module, choose M here: the
455 module will be called sgi_btns.
457 config INPUT_GPIO
458 tristate "GPIO driver support"
459 help
460 Say Y here if you want to support gpio based keys, wheels etc...
462 config HP_SDC_RTC
463 tristate "HP SDC Real Time Clock"
464 depends on (GSC || HP300) && SERIO
465 select HP_SDC
466 help
467 Say Y here if you want to support the built-in real time clock
468 of the HP SDC controller.
470 config INPUT_PALMAS_PWRBUTTON
471 tristate "Palmas Power button Driver"
472 depends on MFD_PALMAS
473 help
474 Say Y here if you want to enable power key reporting via the
475 Palmas family of PMICs.
477 To compile this driver as a module, choose M here. The module will
478 be called palmas_pwrbutton.
480 config INPUT_PCF50633_PMU
481 tristate "PCF50633 PMU events"
482 depends on MFD_PCF50633
483 help
484 Say Y to include support for delivering PMU events via input
485 layer on NXP PCF50633.
487 config INPUT_PCF8574
488 tristate "PCF8574 Keypad input device"
489 depends on I2C
490 help
491 Say Y here if you want to support a keypad connected via I2C
492 with a PCF8574.
494 To compile this driver as a module, choose M here: the
495 module will be called pcf8574_keypad.
497 config INPUT_PWM_BEEPER
498 tristate "PWM beeper support"
499 depends on PWM && HAVE_PWM
500 help
501 Say Y here to get support for PWM based beeper devices.
503 If unsure, say N.
505 To compile this driver as a module, choose M here: the module will be
506 called pwm-beeper.
508 config INPUT_GPIO_ROTARY_ENCODER
509 tristate "Rotary encoders connected to GPIO pins"
510 depends on GPIOLIB
511 help
512 Say Y here to add support for rotary encoders connected to GPIO lines.
513 Check file:Documentation/input/rotary-encoder.txt for more
514 information.
516 To compile this driver as a module, choose M here: the
517 module will be called rotary_encoder.
519 config INPUT_RB532_BUTTON
520 tristate "Mikrotik Routerboard 532 button interface"
521 depends on MIKROTIK_RB532
522 depends on GPIOLIB
523 select INPUT_POLLDEV
524 help
525 Say Y here if you want support for the S1 button built into
526 Mikrotik's Routerboard 532.
528 To compile this driver as a module, choose M here: the
529 module will be called rb532_button.
531 config INPUT_DA9052_ONKEY
532 tristate "Dialog DA9052/DA9053 Onkey"
533 depends on PMIC_DA9052
534 help
535 Support the ONKEY of Dialog DA9052 PMICs as an input device
536 reporting power button status.
538 To compile this driver as a module, choose M here: the
539 module will be called da9052_onkey.
541 config INPUT_DA9055_ONKEY
542 tristate "Dialog Semiconductor DA9055 ONKEY"
543 depends on MFD_DA9055
544 help
545 Support the ONKEY of DA9055 PMICs as an input device
546 reporting power button status.
548 To compile this driver as a module, choose M here: the module
549 will be called da9055_onkey.
551 config INPUT_DM355EVM
552 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
553 depends on MFD_DM355EVM_MSP
554 select INPUT_SPARSEKMAP
555 help
556 Supports the pushbuttons and IR remote used with
557 the DM355 EVM board.
559 To compile this driver as a module, choose M here: the
560 module will be called dm355evm_keys.
562 config INPUT_BFIN_ROTARY
563 tristate "Blackfin Rotary support"
564 depends on BF54x || BF52x
565 help
566 Say Y here if you want to use the Blackfin Rotary.
568 To compile this driver as a module, choose M here: the
569 module will be called bfin-rotary.
571 config INPUT_WM831X_ON
572 tristate "WM831X ON pin"
573 depends on MFD_WM831X
574 help
575 Support the ON pin of WM831X PMICs as an input device
576 reporting power button status.
578 To compile this driver as a module, choose M here: the module
579 will be called wm831x_on.
581 config INPUT_PCAP
582 tristate "Motorola EZX PCAP misc input events"
583 depends on EZX_PCAP
584 help
585 Say Y here if you want to use Power key and Headphone button
586 on Motorola EZX phones.
588 To compile this driver as a module, choose M here: the
589 module will be called pcap_keys.
591 config INPUT_ADXL34X
592 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
593 default n
594 help
595 Say Y here if you have a Accelerometer interface using the
596 ADXL345/6 controller, and your board-specific initialization
597 code includes that in its table of devices.
599 This driver can use either I2C or SPI communication to the
600 ADXL345/6 controller. Select the appropriate method for
601 your system.
603 If unsure, say N (but it's safe to say "Y").
605 To compile this driver as a module, choose M here: the
606 module will be called adxl34x.
608 config INPUT_ADXL34X_I2C
609 tristate "support I2C bus connection"
610 depends on INPUT_ADXL34X && I2C
611 default y
612 help
613 Say Y here if you have ADXL345/6 hooked to an I2C bus.
615 To compile this driver as a module, choose M here: the
616 module will be called adxl34x-i2c.
618 config INPUT_ADXL34X_SPI
619 tristate "support SPI bus connection"
620 depends on INPUT_ADXL34X && SPI
621 default y
622 help
623 Say Y here if you have ADXL345/6 hooked to a SPI bus.
625 To compile this driver as a module, choose M here: the
626 module will be called adxl34x-spi.
628 config INPUT_IMS_PCU
629 tristate "IMS Passenger Control Unit driver"
630 depends on USB
631 depends on LEDS_CLASS
632 help
633 Say Y here if you have system with IMS Rave Passenger Control Unit.
635 To compile this driver as a module, choose M here: the module will be
636 called ims_pcu.
638 config INPUT_CMA3000
639 tristate "VTI CMA3000 Tri-axis accelerometer"
640 help
641 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
642 driver
644 This driver currently only supports I2C interface to the
645 controller. Also select the I2C method.
647 If unsure, say N
649 To compile this driver as a module, choose M here: the
650 module will be called cma3000_d0x.
652 config INPUT_CMA3000_I2C
653 tristate "Support I2C bus connection"
654 depends on INPUT_CMA3000 && I2C
655 help
656 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
657 through I2C interface.
659 To compile this driver as a module, choose M here: the
660 module will be called cma3000_d0x_i2c.
662 config INPUT_XEN_KBDDEV_FRONTEND
663 tristate "Xen virtual keyboard and mouse support"
664 depends on XEN
665 default y
666 select XEN_XENBUS_FRONTEND
667 help
668 This driver implements the front-end of the Xen virtual
669 keyboard and mouse device driver. It communicates with a back-end
670 in another domain.
672 To compile this driver as a module, choose M here: the
673 module will be called xen-kbdfront.
675 config INPUT_SIRFSOC_ONKEY
676 bool "CSR SiRFSoC power on/off/suspend key support"
677 depends on ARCH_SIRF && OF
678 default y
679 help
680 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
681 in Linux, after you press the onkey, system will suspend.
683 If unsure, say N.
685 config INPUT_IDEAPAD_SLIDEBAR
686 tristate "IdeaPad Laptop Slidebar"
687 depends on INPUT
688 depends on SERIO_I8042
689 help
690 Say Y here if you have an IdeaPad laptop with a slidebar.
692 To compile this driver as a module, choose M here: the
693 module will be called ideapad_slidebar.
695 endif