blob: 1da0a20c42ead7fb62242cb474df393023543bce [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
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
Haojian Zhuang69854032010-02-03 15:40:59 -050015config 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
Qiao Zhou96c905f2012-07-17 15:17:39 +080025config 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.
31
32 To compile this driver as a module, choose M here: the module
33 will be called 88pm80x_onkey.
34
Sundar R Iyer77686512010-09-05 12:18:47 -070035config 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.
41
42 To compile this driver as a module, choose M here: the module
43 will be called ab8500-ponkey.
44
Bryan Wu31a62962010-03-21 23:23:24 -070045config INPUT_AD714X
46 tristate "Analog Devices AD714x Capacitance Touch Sensor"
47 help
Barry Song6c04d7b2010-03-21 23:23:29 -070048 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
Bryan Wu31a62962010-03-21 23:23:24 -070049
50 You should select a bus connection too.
51
52 To compile this driver as a module, choose M here: the
53 module will be called ad714x.
54
55config 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.
61
62 To compile this driver as a module, choose M here: the
63 module will be called ad714x-i2c.
64
65config 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.
71
72 To compile this driver as a module, choose M here: the
73 module will be called ad714x-spi.
74
Mark Brown9dd555e2012-11-26 21:17:21 +000075config 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.
81
82 To compile this driver as a module, choose M here: the
83 module will be called arizona-haptics.
84
Eric Anderssonc17ca3f2011-08-09 00:06:37 -070085config 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.
92
93 To compile this driver as a module, choose M here: the
94 module will be called bma150.
95
Linus Torvalds1da177e2005-04-16 15:20:36 -070096config INPUT_PCSPKR
97 tristate "PC Speaker support"
Stas Sergeeve5e1d3c2008-05-07 12:39:56 +020098 depends on PCSPKR_PLATFORM
Linus Torvalds1da177e2005-04-16 15:20:36 -070099 help
100 Say Y here if you want the standard PC Speaker to be used for
101 bells and whistles.
102
103 If unsure, say Y.
104
105 To compile this driver as a module, choose M here: the
106 module will be called pcspkr.
107
Amy Maloche11205bb2011-08-01 23:41:44 -0700108config 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.
116
117 To compile this driver as module, choose M here: the
118 module will be called pm8xxx-vibrator.
119
120config 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.
125
126 If unsure, say N.
127
128 To compile this driver as a module, choose M here: the
129 module will be called pmic8xxx-pwrkey.
130
Linus Torvalds1da177e2005-04-16 15:20:36 -0700131config INPUT_SPARCSPKR
132 tristate "SPARC Speaker support"
David S. Millera2bd4fd2006-06-23 01:44:10 -0700133 depends on PCI && SPARC64
Linus Torvalds1da177e2005-04-16 15:20:36 -0700134 help
135 Say Y here if you want the standard Speaker on Sparc PCI systems
136 to be used for bells and whistles.
137
138 If unsure, say Y.
139
140 To compile this driver as a module, choose M here: the
141 module will be called sparcspkr.
142
143config INPUT_M68K_BEEP
144 tristate "M68k Beeper support"
145 depends on M68K
146
Jaewon Kima3b3ca72014-09-11 23:15:01 -0700147config INPUT_MAX77693_HAPTIC
148 tristate "MAXIM MAX77693 haptic controller support"
149 depends on MFD_MAX77693 && PWM
150 select INPUT_FF_MEMLESS
151 help
152 This option enables support for the haptic controller on
153 MAXIM MAX77693 chip.
154
155 To compile this driver as module, choose M here: the
156 module will be called max77693-haptic.
157
Haojian Zhuang37345742010-05-22 00:57:26 -0700158config INPUT_MAX8925_ONKEY
159 tristate "MAX8925 ONKEY support"
160 depends on MFD_MAX8925
161 help
162 Support the ONKEY of MAX8925 PMICs as an input device
163 reporting power button status.
164
165 To compile this driver as a module, choose M here: the module
166 will be called max8925_onkey.
167
Donggeun Kim104594b02012-03-16 12:28:22 -0700168config INPUT_MAX8997_HAPTIC
169 tristate "MAXIM MAX8997 haptic controller support"
Sascha Hauer557fe992014-01-24 08:54:16 +0100170 depends on PWM && MFD_MAX8997
Donggeun Kim104594b02012-03-16 12:28:22 -0700171 select INPUT_FF_MEMLESS
172 help
173 This option enables device driver support for the haptic controller
174 on MAXIM MAX8997 chip. This driver supports ff-memless interface
175 from input framework.
176
177 To compile this driver as module, choose M here: the
178 module will be called max8997-haptic.
179
Philippe Rétornaz30fc7ac2011-09-18 18:10:53 +0200180config INPUT_MC13783_PWRBUTTON
181 tristate "MC13783 ON buttons"
Alexander Shiyane5a3da22013-12-14 17:03:10 +0400182 depends on MFD_MC13XXX
Philippe Rétornaz30fc7ac2011-09-18 18:10:53 +0200183 help
184 Support the ON buttons of MC13783 PMIC as an input device
185 reporting power button status.
186
187 To compile this driver as a module, choose M here: the module
188 will be called mc13783-pwrbutton.
189
Eric Miao3ead8b52011-06-22 01:02:50 -0700190config INPUT_MMA8450
191 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
192 depends on I2C
193 select INPUT_POLLDEV
194 help
195 Say Y here if you want to support Freescale's MMA8450 Accelerometer
196 through I2C interface.
197
198 To compile this driver as a module, choose M here: the
199 module will be called mma8450.
200
Joseph Lai631b16e2011-06-27 13:26:53 -0700201config INPUT_MPU3050
202 tristate "MPU3050 Triaxial gyroscope sensor"
203 depends on I2C
204 help
205 Say Y here if you want to support InvenSense MPU3050
206 connected via an I2C bus.
207
208 To compile this driver as a module, choose M here: the
209 module will be called mpu3050.
210
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500211config INPUT_APANEL
212 tristate "Fujitsu Lifebook Application Panel buttons"
Randy Dunlap19131302008-03-04 14:29:43 -0800213 depends on X86 && I2C && LEDS_CLASS
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500214 select INPUT_POLLDEV
215 select CHECK_SIGNATURE
216 help
217 Say Y here for support of the Application Panel buttons, used on
218 Fujitsu Lifebook. These are attached to the mainboard through
Randy Dunlap19131302008-03-04 14:29:43 -0800219 an SMBus interface managed by the I2C Intel ICH (i801) driver,
220 which you should also build for this kernel.
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500221
222 To compile this driver as a module, choose M here: the module will
223 be called apanel.
224
Courtney Cavinff803ed2011-12-11 23:38:27 -0800225config INPUT_GP2A
226 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
227 depends on I2C
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700228 depends on GPIOLIB
Courtney Cavinff803ed2011-12-11 23:38:27 -0800229 help
230 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
231 hooked to an I2C bus.
232
233 To compile this driver as a module, choose M here: the
234 module will be called gp2ap002a00f.
235
Alexander Shiyan976358e2013-11-25 19:17:09 -0800236config INPUT_GPIO_BEEPER
237 tristate "Generic GPIO Beeper support"
Alexander Shiyanc95dc012014-04-25 23:45:05 -0700238 depends on GPIOLIB
Alexander Shiyan976358e2013-11-25 19:17:09 -0800239 help
240 Say Y here if you have a beeper connected to a GPIO pin.
241
242 To compile this driver as a module, choose M here: the
243 module will be called gpio-beeper.
244
Heiko Stübner3bfd5c52011-11-29 11:04:09 -0800245config INPUT_GPIO_TILT_POLLED
246 tristate "Polled GPIO tilt switch"
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700247 depends on GPIOLIB
Heiko Stübner3bfd5c52011-11-29 11:04:09 -0800248 select INPUT_POLLDEV
249 help
250 This driver implements support for tilt switches connected
251 to GPIO pins that are not capable of generating interrupts.
252
253 The list of gpios to use and the mapping of their states
254 to specific angles is done via platform data.
255
256 To compile this driver as a module, choose M here: the
257 module will be called gpio_tilt_polled.
258
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400259config INPUT_IXP4XX_BEEPER
260 tristate "IXP4XX Beeper support"
261 depends on ARCH_IXP4XX
262 help
263 If you say yes here, you can connect a beeper to the
264 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
265
266 If unsure, say Y.
267
268 To compile this driver as a module, choose M here: the
269 module will be called ixp4xx-beeper.
270
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500271config INPUT_COBALT_BTNS
272 tristate "Cobalt button interface"
273 depends on MIPS_COBALT
Dmitry Torokhov3d29cdf2007-04-29 23:43:06 -0400274 select INPUT_POLLDEV
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500275 help
276 Say Y here if you want to support MIPS Cobalt button interface.
277
278 To compile this driver as a module, choose M here: the
279 module will be called cobalt_btns.
280
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500281config INPUT_WISTRON_BTNS
282 tristate "x86 Wistron laptop button interface"
Jean Delvare86234eb2014-03-11 23:09:08 -0700283 depends on X86_32
Dmitry Torokhovc2554c92007-05-22 23:48:39 -0400284 select INPUT_POLLDEV
Dmitry Torokhove97af4c2009-12-04 10:22:24 -0800285 select INPUT_SPARSEKMAP
Eric Piel389679d2007-05-21 00:46:31 -0400286 select NEW_LEDS
287 select LEDS_CLASS
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700288 select CHECK_SIGNATURE
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500289 help
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200290 Say Y here for support of Wistron laptop button interfaces, used on
Eric Piel389679d2007-05-21 00:46:31 -0400291 laptops of various brands, including Acer and Fujitsu-Siemens. If
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200292 available, mail and wifi LEDs will be controllable via /sys/class/leds.
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500293
294 To compile this driver as a module, choose M here: the module will
295 be called wistron_btns.
296
Jaya Kumar31ea7ff2007-02-10 01:29:00 -0500297config INPUT_ATLAS_BTNS
298 tristate "x86 Atlas button interface"
299 depends on X86 && ACPI
300 help
301 Say Y here for support of Atlas wallmount touchscreen buttons.
302 The events will show up as scancodes F1 through F9 via evdev.
303
304 To compile this driver as a module, choose M here: the module will
305 be called atlas_btns.
306
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400307config INPUT_ATI_REMOTE2
308 tristate "ATI / Philips USB RF remote control"
Al Viro7a86ede2007-05-15 20:36:20 +0100309 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400310 select USB
311 help
312 Say Y here if you want to use an ATI or Philips USB RF remote control.
313 These are RF remotes with USB receivers.
314 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
315 and is also available as a separate product.
316 This driver provides mouse pointer, left and right mouse buttons,
317 and maps all the other remote buttons to keypress events.
318
319 To compile this driver as a module, choose M here: the module will be
320 called ati_remote2.
321
322config INPUT_KEYSPAN_REMOTE
Kees Cooke52278a2012-10-24 23:53:02 -0700323 tristate "Keyspan DMR USB remote control"
Al Viro7a86ede2007-05-15 20:36:20 +0100324 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400325 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.
333
334 To compile this driver as a module, choose M here: the module will
335 be called keyspan_remote.
336
Chris Hudsone8e70d82011-07-06 18:36:51 -0700337config 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.
343
344 To compile this driver as a module, choose M here: the module will
345 be called kxtj9.
346
347config 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.
353
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400354config INPUT_POWERMATE
355 tristate "Griffin PowerMate and Contour Jog support"
Al Viro7a86ede2007-05-15 20:36:20 +0100356 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400357 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.
363
364 You can download userspace tools from
365 <http://sowerbutts.com/powermate/>.
Alessandro Zummo01387952006-01-29 21:50:40 -0500366
367 To compile this driver as a module, choose M here: the
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400368 module will be called powermate.
369
370config INPUT_YEALINK
371 tristate "Yealink usb-p1k voip phone"
Al Viro7a86ede2007-05-15 20:36:20 +0100372 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400373 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.
378
379 For information about how to use these additional functions, see
380 <file:Documentation/input/yealink.txt>.
381
382 To compile this driver as a module, choose M here: the module will be
383 called yealink.
Alessandro Zummo01387952006-01-29 21:50:40 -0500384
Alfred E. Heggestadc04148f2008-08-08 11:49:08 -0400385config INPUT_CM109
386 tristate "C-Media CM109 USB I/O Controller"
Alfred E. Heggestadc04148f2008-08-08 11:49:08 -0400387 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.
393
394 To compile this driver as a module, choose M here: the module will be
395 called cm109.
396
Jaewon Kimd64cb712014-12-17 10:31:08 -0800397config INPUT_REGULATOR_HAPTIC
398 tristate "Regulator haptics support"
399 depends on REGULATOR
400 select INPUT_FF_MEMLESS
401 help
402 This option enables device driver support for the haptic controlled
403 by a regulator. This driver supports ff-memless interface
404 from input framework.
405
406 To compile this driver as a module, choose M here: the
407 module will be called regulator-haptic.
408
Aaro Koskinen544a46c2012-11-10 00:50:25 -0800409config INPUT_RETU_PWRBUTTON
410 tristate "Retu Power button Driver"
411 depends on MFD_RETU
412 help
413 Say Y here if you want to enable power key reporting via the
414 Retu chips found in Nokia Internet Tablets (770, N800, N810).
415
416 To compile this driver as a module, choose M here. The module will
417 be called retu-pwrbutton.
418
Felipe Balbi68d8bf02009-04-19 23:07:50 -0700419config INPUT_TWL4030_PWRBUTTON
420 tristate "TWL4030 Power button Driver"
421 depends on TWL4030_CORE
422 help
423 Say Y here if you want to enable power key reporting via the
424 TWL4030 family of chips.
425
426 To compile this driver as a module, choose M here. The module will
427 be called twl4030_pwrbutton.
428
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800429config INPUT_TWL4030_VIBRA
430 tristate "Support for TWL4030 Vibrator"
431 depends on TWL4030_CORE
Peter Ujfalusi57fe7252011-05-31 12:02:49 +0300432 select MFD_TWL4030_AUDIO
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800433 select INPUT_FF_MEMLESS
434 help
435 This option enables support for TWL4030 Vibrator Driver.
436
437 To compile this driver as a module, choose M here. The module will
438 be called twl4030_vibra.
439
Misael Lopez Cruzcc697d382011-05-01 03:51:24 -0500440config INPUT_TWL6040_VIBRA
441 tristate "Support for TWL6040 Vibrator"
Peter Ujfalusi8eaeb932012-04-03 11:56:51 +0300442 depends on TWL6040_CORE
Misael Lopez Cruzcc697d382011-05-01 03:51:24 -0500443 select INPUT_FF_MEMLESS
444 help
445 This option enables support for TWL6040 Vibrator Driver.
446
447 To compile this driver as a module, choose M here. The module will
448 be called twl6040_vibra.
449
Linus Torvalds1da177e2005-04-16 15:20:36 -0700450config INPUT_UINPUT
451 tristate "User level driver support"
452 help
453 Say Y here if you want to support user level drivers for input
454 subsystem accessible under char device 10:223 - /dev/input/uinput.
455
456 To compile this driver as a module, choose M here: the
457 module will be called uinput.
458
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400459config INPUT_SGI_BTNS
460 tristate "SGI Indy/O2 volume button interface"
461 depends on SGI_IP22 || SGI_IP32
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400462 select INPUT_POLLDEV
463 help
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400464 Say Y here if you want to support SGI Indy/O2 volume button interface.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400465
466 To compile this driver as a module, choose M here: the
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400467 module will be called sgi_btns.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400468
Linus Torvalds1da177e2005-04-16 15:20:36 -0700469config HP_SDC_RTC
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500470 tristate "HP SDC Real Time Clock"
Alexander Beregalovd061ebd2009-04-11 16:55:41 -0700471 depends on (GSC || HP300) && SERIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700472 select HP_SDC
473 help
474 Say Y here if you want to support the built-in real time clock
475 of the HP SDC controller.
476
Nishanth Menonadff5962014-08-26 15:57:47 -0700477config INPUT_PALMAS_PWRBUTTON
478 tristate "Palmas Power button Driver"
479 depends on MFD_PALMAS
480 help
481 Say Y here if you want to enable power key reporting via the
482 Palmas family of PMICs.
483
484 To compile this driver as a module, choose M here. The module will
485 be called palmas_pwrbutton.
486
Balaji Rao1851b062009-01-09 01:50:58 +0100487config INPUT_PCF50633_PMU
488 tristate "PCF50633 PMU events"
489 depends on MFD_PCF50633
490 help
491 Say Y to include support for delivering PMU events via input
492 layer on NXP PCF50633.
493
Bryan Wub91c4be2010-03-19 22:18:15 -0700494config INPUT_PCF8574
495 tristate "PCF8574 Keypad input device"
Kees Cooke52278a2012-10-24 23:53:02 -0700496 depends on I2C
Bryan Wub91c4be2010-03-19 22:18:15 -0700497 help
Masanari Iida393f9ff2012-01-31 00:07:33 -0800498 Say Y here if you want to support a keypad connected via I2C
Bryan Wub91c4be2010-03-19 22:18:15 -0700499 with a PCF8574.
500
501 To compile this driver as a module, choose M here: the
502 module will be called pcf8574_keypad.
503
Lars-Peter Clausene22739d2010-07-14 00:25:21 -0700504config INPUT_PWM_BEEPER
505 tristate "PWM beeper support"
Sascha Hauer557fe992014-01-24 08:54:16 +0100506 depends on PWM
Lars-Peter Clausene22739d2010-07-14 00:25:21 -0700507 help
508 Say Y here to get support for PWM based beeper devices.
509
510 If unsure, say N.
511
512 To compile this driver as a module, choose M here: the module will be
513 called pwm-beeper.
514
Daniel Mack73969ff2009-03-04 23:27:14 -0800515config INPUT_GPIO_ROTARY_ENCODER
516 tristate "Rotary encoders connected to GPIO pins"
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700517 depends on GPIOLIB
Daniel Mack73969ff2009-03-04 23:27:14 -0800518 help
519 Say Y here to add support for rotary encoders connected to GPIO lines.
Alessio Igor Bogani492d0f92009-05-21 19:54:33 +0200520 Check file:Documentation/input/rotary-encoder.txt for more
Daniel Mack73969ff2009-03-04 23:27:14 -0800521 information.
522
523 To compile this driver as a module, choose M here: the
524 module will be called rotary_encoder.
525
Phil Sutterd9bdffd2009-03-04 23:27:15 -0800526config INPUT_RB532_BUTTON
527 tristate "Mikrotik Routerboard 532 button interface"
528 depends on MIKROTIK_RB532
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700529 depends on GPIOLIB
Phil Sutterd9bdffd2009-03-04 23:27:15 -0800530 select INPUT_POLLDEV
531 help
532 Say Y here if you want support for the S1 button built into
533 Mikrotik's Routerboard 532.
534
535 To compile this driver as a module, choose M here: the
536 module will be called rb532_button.
537
Ashish Jangamf0c5f652012-03-04 08:40:58 -0800538config INPUT_DA9052_ONKEY
539 tristate "Dialog DA9052/DA9053 Onkey"
540 depends on PMIC_DA9052
541 help
542 Support the ONKEY of Dialog DA9052 PMICs as an input device
543 reporting power button status.
544
545 To compile this driver as a module, choose M here: the
546 module will be called da9052_onkey.
547
Ashish Jangam8ed27572012-10-30 00:27:25 -0700548config INPUT_DA9055_ONKEY
549 tristate "Dialog Semiconductor DA9055 ONKEY"
550 depends on MFD_DA9055
551 help
552 Support the ONKEY of DA9055 PMICs as an input device
553 reporting power button status.
554
555 To compile this driver as a module, choose M here: the module
556 will be called da9055_onkey.
557
David Brownelleb990b52009-04-23 19:25:29 -0700558config INPUT_DM355EVM
559 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
560 depends on MFD_DM355EVM_MSP
Dmitry Torokhov66040722009-12-04 10:22:25 -0800561 select INPUT_SPARSEKMAP
David Brownelleb990b52009-04-23 19:25:29 -0700562 help
563 Supports the pushbuttons and IR remote used with
564 the DM355 EVM board.
565
566 To compile this driver as a module, choose M here: the
567 module will be called dm355evm_keys.
Michael Hennerich48329582009-07-22 21:51:34 -0700568
569config INPUT_BFIN_ROTARY
570 tristate "Blackfin Rotary support"
571 depends on BF54x || BF52x
572 help
573 Say Y here if you want to use the Blackfin Rotary.
574
575 To compile this driver as a module, choose M here: the
576 module will be called bfin-rotary.
577
Mark Brown0c73b992009-09-15 12:07:12 +0200578config INPUT_WM831X_ON
579 tristate "WM831X ON pin"
580 depends on MFD_WM831X
581 help
582 Support the ON pin of WM831X PMICs as an input device
583 reporting power button status.
584
585 To compile this driver as a module, choose M here: the module
586 will be called wm831x_on.
587
Daniel Ribeirod0a82132009-08-10 20:27:48 +0200588config INPUT_PCAP
589 tristate "Motorola EZX PCAP misc input events"
590 depends on EZX_PCAP
591 help
592 Say Y here if you want to use Power key and Headphone button
593 on Motorola EZX phones.
594
595 To compile this driver as a module, choose M here: the
596 module will be called pcap_keys.
597
Michael Henneriche27c7292010-06-25 08:44:10 -0700598config INPUT_ADXL34X
599 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
600 default n
601 help
602 Say Y here if you have a Accelerometer interface using the
603 ADXL345/6 controller, and your board-specific initialization
604 code includes that in its table of devices.
605
606 This driver can use either I2C or SPI communication to the
607 ADXL345/6 controller. Select the appropriate method for
608 your system.
609
610 If unsure, say N (but it's safe to say "Y").
611
612 To compile this driver as a module, choose M here: the
613 module will be called adxl34x.
614
615config INPUT_ADXL34X_I2C
616 tristate "support I2C bus connection"
617 depends on INPUT_ADXL34X && I2C
618 default y
619 help
620 Say Y here if you have ADXL345/6 hooked to an I2C bus.
621
622 To compile this driver as a module, choose M here: the
623 module will be called adxl34x-i2c.
624
625config INPUT_ADXL34X_SPI
626 tristate "support SPI bus connection"
627 depends on INPUT_ADXL34X && SPI
628 default y
629 help
630 Say Y here if you have ADXL345/6 hooked to a SPI bus.
631
632 To compile this driver as a module, choose M here: the
633 module will be called adxl34x-spi.
634
Dmitry Torokhov628329d2013-02-02 11:26:13 -0800635config INPUT_IMS_PCU
636 tristate "IMS Passenger Control Unit driver"
637 depends on USB
638 depends on LEDS_CLASS
639 help
640 Say Y here if you have system with IMS Rave Passenger Control Unit.
641
642 To compile this driver as a module, choose M here: the module will be
643 called ims_pcu.
644
Hemanth Vb029ffa2010-11-30 23:03:54 -0800645config INPUT_CMA3000
646 tristate "VTI CMA3000 Tri-axis accelerometer"
647 help
648 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
649 driver
650
651 This driver currently only supports I2C interface to the
652 controller. Also select the I2C method.
653
654 If unsure, say N
655
656 To compile this driver as a module, choose M here: the
657 module will be called cma3000_d0x.
658
659config INPUT_CMA3000_I2C
660 tristate "Support I2C bus connection"
661 depends on INPUT_CMA3000 && I2C
662 help
663 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
664 through I2C interface.
665
666 To compile this driver as a module, choose M here: the
667 module will be called cma3000_d0x_i2c.
668
Dmitry Torokhov49851ca2011-03-16 22:56:03 -0700669config INPUT_XEN_KBDDEV_FRONTEND
670 tristate "Xen virtual keyboard and mouse support"
Andrew Jones4bc25af2012-01-06 10:43:09 +0100671 depends on XEN
Dmitry Torokhov49851ca2011-03-16 22:56:03 -0700672 default y
673 select XEN_XENBUS_FRONTEND
674 help
675 This driver implements the front-end of the Xen virtual
676 keyboard and mouse device driver. It communicates with a back-end
677 in another domain.
678
679 To compile this driver as a module, choose M here: the
680 module will be called xen-kbdfront.
681
Binghua Duan9b5f9532013-06-02 23:38:46 -0700682config INPUT_SIRFSOC_ONKEY
683 bool "CSR SiRFSoC power on/off/suspend key support"
684 depends on ARCH_SIRF && OF
685 default y
686 help
687 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
688 in Linux, after you press the onkey, system will suspend.
689
690 If unsure, say N.
691
Andrey Moiseev1ea4c162013-08-25 22:51:15 -0700692config INPUT_IDEAPAD_SLIDEBAR
693 tristate "IdeaPad Laptop Slidebar"
694 depends on INPUT
695 depends on SERIO_I8042
696 help
697 Say Y here if you have an IdeaPad laptop with a slidebar.
698
699 To compile this driver as a module, choose M here: the
700 module will be called ideapad_slidebar.
701
Lejun Zhu61cd4822014-03-30 23:12:00 -0700702config INPUT_SOC_BUTTON_ARRAY
703 tristate "Windows-compatible SoC Button Array"
704 depends on KEYBOARD_GPIO
705 help
706 Say Y here if you have a SoC-based tablet that originally
707 runs Windows 8.
708
709 To compile this driver as a module, choose M here: the
710 module will be called soc_button_array.
711
Dan Murphy7132fe42014-08-17 09:24:26 -0700712config INPUT_DRV260X_HAPTICS
713 tristate "TI DRV260X haptics support"
714 depends on INPUT && I2C && GPIOLIB
715 select INPUT_FF_MEMLESS
716 select REGMAP_I2C
717 help
718 Say Y to enable support for the TI DRV260X haptics driver.
719
720 To compile this driver as a module, choose M here: the
721 module will be called drv260x-haptics.
722
Dan Murphy1c246222014-09-08 16:10:49 -0700723config INPUT_DRV2667_HAPTICS
724 tristate "TI DRV2667 haptics support"
725 depends on INPUT && I2C
726 select INPUT_FF_MEMLESS
727 select REGMAP_I2C
728 help
729 Say Y to enable support for the TI DRV2667 haptics driver.
730
731 To compile this driver as a module, choose M here: the
732 module will be called drv260x-haptics.
733
Linus Torvalds1da177e2005-04-16 15:20:36 -0700734endif