blob: 4436ab1b9735d608821309eea92b486a1bc147e2 [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
Moritz Fischer846a7fc2015-01-10 14:04:14 -080096config INPUT_E3X0_BUTTON
97 tristate "NI Ettus Research USRP E3x0 Button support."
98 default n
99 help
100 Say Y here to enable support for the NI Ettus Research
101 USRP E3x0 Button.
102
103 To compile this driver as a module, choose M here: the
104 module will be called e3x0_button.
105
Linus Torvalds1da177e2005-04-16 15:20:36 -0700106config INPUT_PCSPKR
107 tristate "PC Speaker support"
Stas Sergeeve5e1d3c2008-05-07 12:39:56 +0200108 depends on PCSPKR_PLATFORM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109 help
110 Say Y here if you want the standard PC Speaker to be used for
111 bells and whistles.
112
113 If unsure, say Y.
114
115 To compile this driver as a module, choose M here: the
116 module will be called pcspkr.
117
Courtney Cavin68c581d2015-03-20 21:45:59 -0700118config INPUT_PM8941_PWRKEY
119 tristate "Qualcomm PM8941 power key support"
120 depends on MFD_SPMI_PMIC
121 help
122 Say Y here if you want support for the power key usually found
123 on boards using a Qualcomm PM8941 compatible PMIC.
124
125 If unsure, say Y.
126
127 To compile this driver as a module, choose M here: the module
128 will be called pm8941-pwrkey.
129
Amy Maloche11205bb2011-08-01 23:41:44 -0700130config INPUT_PM8XXX_VIBRATOR
131 tristate "Qualcomm PM8XXX vibrator support"
132 depends on MFD_PM8XXX
133 select INPUT_FF_MEMLESS
134 help
135 This option enables device driver support for the vibrator
136 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
137 from input framework.
138
139 To compile this driver as module, choose M here: the
140 module will be called pm8xxx-vibrator.
141
142config INPUT_PMIC8XXX_PWRKEY
143 tristate "PMIC8XXX power key support"
144 depends on MFD_PM8XXX
145 help
146 Say Y here if you want support for the PMIC8XXX power key.
147
148 If unsure, say N.
149
150 To compile this driver as a module, choose M here: the
151 module will be called pmic8xxx-pwrkey.
152
Linus Torvalds1da177e2005-04-16 15:20:36 -0700153config INPUT_SPARCSPKR
154 tristate "SPARC Speaker support"
David S. Millera2bd4fd2006-06-23 01:44:10 -0700155 depends on PCI && SPARC64
Linus Torvalds1da177e2005-04-16 15:20:36 -0700156 help
157 Say Y here if you want the standard Speaker on Sparc PCI systems
158 to be used for bells and whistles.
159
160 If unsure, say Y.
161
162 To compile this driver as a module, choose M here: the
163 module will be called sparcspkr.
164
165config INPUT_M68K_BEEP
166 tristate "M68k Beeper support"
167 depends on M68K
168
Jaewon Kima3b3ca72014-09-11 23:15:01 -0700169config INPUT_MAX77693_HAPTIC
170 tristate "MAXIM MAX77693 haptic controller support"
171 depends on MFD_MAX77693 && PWM
172 select INPUT_FF_MEMLESS
173 help
174 This option enables support for the haptic controller on
175 MAXIM MAX77693 chip.
176
177 To compile this driver as module, choose M here: the
178 module will be called max77693-haptic.
179
Jaewon Kime5abff12015-03-04 14:43:40 -0800180config INPUT_MAX77843_HAPTIC
181 tristate "MAXIM MAX77843 haptic controller support"
182 depends on MFD_MAX77843 && REGULATOR
183 select INPUT_FF_MEMLESS
184 help
185 This option enables support for the haptic controller on
186 MAXIM MAX77843 chip. The driver supports ff-memless interface
187 from input framework.
188
189 To compile this driver as module, choose M here: the
190 module will be called max77843-haptic.
191
Haojian Zhuang37345742010-05-22 00:57:26 -0700192config INPUT_MAX8925_ONKEY
193 tristate "MAX8925 ONKEY support"
194 depends on MFD_MAX8925
195 help
196 Support the ONKEY of MAX8925 PMICs as an input device
197 reporting power button status.
198
199 To compile this driver as a module, choose M here: the module
200 will be called max8925_onkey.
201
Donggeun Kim104594b02012-03-16 12:28:22 -0700202config INPUT_MAX8997_HAPTIC
203 tristate "MAXIM MAX8997 haptic controller support"
Sascha Hauer557fe992014-01-24 08:54:16 +0100204 depends on PWM && MFD_MAX8997
Donggeun Kim104594b02012-03-16 12:28:22 -0700205 select INPUT_FF_MEMLESS
206 help
207 This option enables device driver support for the haptic controller
208 on MAXIM MAX8997 chip. This driver supports ff-memless interface
209 from input framework.
210
211 To compile this driver as module, choose M here: the
212 module will be called max8997-haptic.
213
Philippe Rétornaz30fc7ac2011-09-18 18:10:53 +0200214config INPUT_MC13783_PWRBUTTON
215 tristate "MC13783 ON buttons"
Alexander Shiyane5a3da22013-12-14 17:03:10 +0400216 depends on MFD_MC13XXX
Philippe Rétornaz30fc7ac2011-09-18 18:10:53 +0200217 help
218 Support the ON buttons of MC13783 PMIC as an input device
219 reporting power button status.
220
221 To compile this driver as a module, choose M here: the module
222 will be called mc13783-pwrbutton.
223
Eric Miao3ead8b52011-06-22 01:02:50 -0700224config INPUT_MMA8450
225 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
226 depends on I2C
227 select INPUT_POLLDEV
228 help
229 Say Y here if you want to support Freescale's MMA8450 Accelerometer
230 through I2C interface.
231
232 To compile this driver as a module, choose M here: the
233 module will be called mma8450.
234
Joseph Lai631b16e2011-06-27 13:26:53 -0700235config INPUT_MPU3050
236 tristate "MPU3050 Triaxial gyroscope sensor"
237 depends on I2C
238 help
239 Say Y here if you want to support InvenSense MPU3050
240 connected via an I2C bus.
241
242 To compile this driver as a module, choose M here: the
243 module will be called mpu3050.
244
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500245config INPUT_APANEL
246 tristate "Fujitsu Lifebook Application Panel buttons"
Randy Dunlap19131302008-03-04 14:29:43 -0800247 depends on X86 && I2C && LEDS_CLASS
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500248 select INPUT_POLLDEV
249 select CHECK_SIGNATURE
250 help
251 Say Y here for support of the Application Panel buttons, used on
252 Fujitsu Lifebook. These are attached to the mainboard through
Randy Dunlap19131302008-03-04 14:29:43 -0800253 an SMBus interface managed by the I2C Intel ICH (i801) driver,
254 which you should also build for this kernel.
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500255
256 To compile this driver as a module, choose M here: the module will
257 be called apanel.
258
Courtney Cavinff803ed2011-12-11 23:38:27 -0800259config INPUT_GP2A
260 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
261 depends on I2C
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700262 depends on GPIOLIB
Courtney Cavinff803ed2011-12-11 23:38:27 -0800263 help
264 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
265 hooked to an I2C bus.
266
267 To compile this driver as a module, choose M here: the
268 module will be called gp2ap002a00f.
269
Alexander Shiyan976358e2013-11-25 19:17:09 -0800270config INPUT_GPIO_BEEPER
271 tristate "Generic GPIO Beeper support"
Alexander Shiyanc95dc012014-04-25 23:45:05 -0700272 depends on GPIOLIB
Alexander Shiyan976358e2013-11-25 19:17:09 -0800273 help
274 Say Y here if you have a beeper connected to a GPIO pin.
275
276 To compile this driver as a module, choose M here: the
277 module will be called gpio-beeper.
278
Heiko Stübner3bfd5c52011-11-29 11:04:09 -0800279config INPUT_GPIO_TILT_POLLED
280 tristate "Polled GPIO tilt switch"
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700281 depends on GPIOLIB
Heiko Stübner3bfd5c52011-11-29 11:04:09 -0800282 select INPUT_POLLDEV
283 help
284 This driver implements support for tilt switches connected
285 to GPIO pins that are not capable of generating interrupts.
286
287 The list of gpios to use and the mapping of their states
288 to specific angles is done via platform data.
289
290 To compile this driver as a module, choose M here: the
291 module will be called gpio_tilt_polled.
292
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400293config INPUT_IXP4XX_BEEPER
294 tristate "IXP4XX Beeper support"
295 depends on ARCH_IXP4XX
296 help
297 If you say yes here, you can connect a beeper to the
298 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
299
300 If unsure, say Y.
301
302 To compile this driver as a module, choose M here: the
303 module will be called ixp4xx-beeper.
304
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500305config INPUT_COBALT_BTNS
306 tristate "Cobalt button interface"
307 depends on MIPS_COBALT
Dmitry Torokhov3d29cdf2007-04-29 23:43:06 -0400308 select INPUT_POLLDEV
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500309 help
310 Say Y here if you want to support MIPS Cobalt button interface.
311
312 To compile this driver as a module, choose M here: the
313 module will be called cobalt_btns.
314
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500315config INPUT_WISTRON_BTNS
316 tristate "x86 Wistron laptop button interface"
Jean Delvare86234eb2014-03-11 23:09:08 -0700317 depends on X86_32
Dmitry Torokhovc2554c92007-05-22 23:48:39 -0400318 select INPUT_POLLDEV
Dmitry Torokhove97af4c2009-12-04 10:22:24 -0800319 select INPUT_SPARSEKMAP
Eric Piel389679d2007-05-21 00:46:31 -0400320 select NEW_LEDS
321 select LEDS_CLASS
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700322 select CHECK_SIGNATURE
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500323 help
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200324 Say Y here for support of Wistron laptop button interfaces, used on
Eric Piel389679d2007-05-21 00:46:31 -0400325 laptops of various brands, including Acer and Fujitsu-Siemens. If
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200326 available, mail and wifi LEDs will be controllable via /sys/class/leds.
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500327
328 To compile this driver as a module, choose M here: the module will
329 be called wistron_btns.
330
Jaya Kumar31ea7ff2007-02-10 01:29:00 -0500331config INPUT_ATLAS_BTNS
332 tristate "x86 Atlas button interface"
333 depends on X86 && ACPI
334 help
335 Say Y here for support of Atlas wallmount touchscreen buttons.
336 The events will show up as scancodes F1 through F9 via evdev.
337
338 To compile this driver as a module, choose M here: the module will
339 be called atlas_btns.
340
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400341config INPUT_ATI_REMOTE2
342 tristate "ATI / Philips USB RF remote control"
Al Viro7a86ede2007-05-15 20:36:20 +0100343 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400344 select USB
345 help
346 Say Y here if you want to use an ATI or Philips USB RF remote control.
347 These are RF remotes with USB receivers.
348 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
349 and is also available as a separate product.
350 This driver provides mouse pointer, left and right mouse buttons,
351 and maps all the other remote buttons to keypress events.
352
353 To compile this driver as a module, choose M here: the module will be
354 called ati_remote2.
355
356config INPUT_KEYSPAN_REMOTE
Kees Cooke52278a2012-10-24 23:53:02 -0700357 tristate "Keyspan DMR USB remote control"
Al Viro7a86ede2007-05-15 20:36:20 +0100358 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400359 select USB
360 help
361 Say Y here if you want to use a Keyspan DMR USB remote control.
362 Currently only the UIA-11 type of receiver has been tested. The tag
363 on the receiver that connects to the USB port should have a P/N that
364 will tell you what type of DMR you have. The UIA-10 type is not
365 supported at this time. This driver maps all buttons to keypress
366 events.
367
368 To compile this driver as a module, choose M here: the module will
369 be called keyspan_remote.
370
Chris Hudsone8e70d82011-07-06 18:36:51 -0700371config INPUT_KXTJ9
372 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
373 depends on I2C
374 help
375 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
376 accelerometer.
377
378 To compile this driver as a module, choose M here: the module will
379 be called kxtj9.
380
381config INPUT_KXTJ9_POLLED_MODE
382 bool "Enable polling mode support"
383 depends on INPUT_KXTJ9
384 select INPUT_POLLDEV
385 help
386 Say Y here if you need accelerometer to work in polling mode.
387
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400388config INPUT_POWERMATE
389 tristate "Griffin PowerMate and Contour Jog support"
Al Viro7a86ede2007-05-15 20:36:20 +0100390 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400391 select USB
392 help
393 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
394 These are aluminum dials which can measure clockwise and anticlockwise
395 rotation. The dial also acts as a pushbutton. The base contains an LED
396 which can be instructed to pulse or to switch to a particular intensity.
397
398 You can download userspace tools from
399 <http://sowerbutts.com/powermate/>.
Alessandro Zummo01387952006-01-29 21:50:40 -0500400
401 To compile this driver as a module, choose M here: the
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400402 module will be called powermate.
403
404config INPUT_YEALINK
405 tristate "Yealink usb-p1k voip phone"
Al Viro7a86ede2007-05-15 20:36:20 +0100406 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400407 select USB
408 help
409 Say Y here if you want to enable keyboard and LCD functions of the
410 Yealink usb-p1k usb phones. The audio part is enabled by the generic
411 usb sound driver, so you might want to enable that as well.
412
413 For information about how to use these additional functions, see
414 <file:Documentation/input/yealink.txt>.
415
416 To compile this driver as a module, choose M here: the module will be
417 called yealink.
Alessandro Zummo01387952006-01-29 21:50:40 -0500418
Alfred E. Heggestadc04148f2008-08-08 11:49:08 -0400419config INPUT_CM109
420 tristate "C-Media CM109 USB I/O Controller"
Alfred E. Heggestadc04148f2008-08-08 11:49:08 -0400421 depends on USB_ARCH_HAS_HCD
422 select USB
423 help
424 Say Y here if you want to enable keyboard and buzzer functions of the
425 C-Media CM109 usb phones. The audio part is enabled by the generic
426 usb sound driver, so you might want to enable that as well.
427
428 To compile this driver as a module, choose M here: the module will be
429 called cm109.
430
Jaewon Kimd64cb712014-12-17 10:31:08 -0800431config INPUT_REGULATOR_HAPTIC
432 tristate "Regulator haptics support"
433 depends on REGULATOR
434 select INPUT_FF_MEMLESS
435 help
436 This option enables device driver support for the haptic controlled
437 by a regulator. This driver supports ff-memless interface
438 from input framework.
439
440 To compile this driver as a module, choose M here: the
441 module will be called regulator-haptic.
442
Aaro Koskinen544a46c2012-11-10 00:50:25 -0800443config INPUT_RETU_PWRBUTTON
444 tristate "Retu Power button Driver"
445 depends on MFD_RETU
446 help
447 Say Y here if you want to enable power key reporting via the
448 Retu chips found in Nokia Internet Tablets (770, N800, N810).
449
450 To compile this driver as a module, choose M here. The module will
451 be called retu-pwrbutton.
452
Felipe Balbi5fafed32014-12-27 20:37:37 -0800453config INPUT_TPS65218_PWRBUTTON
454 tristate "TPS65218 Power button driver"
455 depends on MFD_TPS65218
456 help
457 Say Y here if you want to enable power buttong reporting for
458 the TPS65218 Power Management IC device.
459
460 To compile this driver as a module, choose M here. The module will
461 be called tps65218-pwrbutton.
462
Carlo Caione5b6c26a2014-12-29 11:20:54 -0800463config INPUT_AXP20X_PEK
464 tristate "X-Powers AXP20X power button driver"
465 depends on MFD_AXP20X
466 help
467 Say Y here if you want to enable power key reporting via the
468 AXP20X PMIC.
469
470 To compile this driver as a module, choose M here. The module will
471 be called axp20x-pek.
472
473
Felipe Balbi68d8bf02009-04-19 23:07:50 -0700474config INPUT_TWL4030_PWRBUTTON
475 tristate "TWL4030 Power button Driver"
476 depends on TWL4030_CORE
477 help
478 Say Y here if you want to enable power key reporting via the
479 TWL4030 family of chips.
480
481 To compile this driver as a module, choose M here. The module will
482 be called twl4030_pwrbutton.
483
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800484config INPUT_TWL4030_VIBRA
485 tristate "Support for TWL4030 Vibrator"
486 depends on TWL4030_CORE
Peter Ujfalusi57fe7252011-05-31 12:02:49 +0300487 select MFD_TWL4030_AUDIO
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800488 select INPUT_FF_MEMLESS
489 help
490 This option enables support for TWL4030 Vibrator Driver.
491
492 To compile this driver as a module, choose M here. The module will
493 be called twl4030_vibra.
494
Misael Lopez Cruzcc697d382011-05-01 03:51:24 -0500495config INPUT_TWL6040_VIBRA
496 tristate "Support for TWL6040 Vibrator"
Peter Ujfalusi8eaeb932012-04-03 11:56:51 +0300497 depends on TWL6040_CORE
Misael Lopez Cruzcc697d382011-05-01 03:51:24 -0500498 select INPUT_FF_MEMLESS
499 help
500 This option enables support for TWL6040 Vibrator Driver.
501
502 To compile this driver as a module, choose M here. The module will
503 be called twl6040_vibra.
504
Linus Torvalds1da177e2005-04-16 15:20:36 -0700505config INPUT_UINPUT
506 tristate "User level driver support"
507 help
508 Say Y here if you want to support user level drivers for input
509 subsystem accessible under char device 10:223 - /dev/input/uinput.
510
511 To compile this driver as a module, choose M here: the
512 module will be called uinput.
513
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400514config INPUT_SGI_BTNS
515 tristate "SGI Indy/O2 volume button interface"
516 depends on SGI_IP22 || SGI_IP32
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400517 select INPUT_POLLDEV
518 help
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400519 Say Y here if you want to support SGI Indy/O2 volume button interface.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400520
521 To compile this driver as a module, choose M here: the
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400522 module will be called sgi_btns.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400523
Linus Torvalds1da177e2005-04-16 15:20:36 -0700524config HP_SDC_RTC
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500525 tristate "HP SDC Real Time Clock"
Alexander Beregalovd061ebd2009-04-11 16:55:41 -0700526 depends on (GSC || HP300) && SERIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700527 select HP_SDC
528 help
529 Say Y here if you want to support the built-in real time clock
530 of the HP SDC controller.
531
Nishanth Menonadff5962014-08-26 15:57:47 -0700532config INPUT_PALMAS_PWRBUTTON
533 tristate "Palmas Power button Driver"
534 depends on MFD_PALMAS
535 help
536 Say Y here if you want to enable power key reporting via the
537 Palmas family of PMICs.
538
539 To compile this driver as a module, choose M here. The module will
540 be called palmas_pwrbutton.
541
Balaji Rao1851b062009-01-09 01:50:58 +0100542config INPUT_PCF50633_PMU
543 tristate "PCF50633 PMU events"
544 depends on MFD_PCF50633
545 help
546 Say Y to include support for delivering PMU events via input
547 layer on NXP PCF50633.
548
Bryan Wub91c4be2010-03-19 22:18:15 -0700549config INPUT_PCF8574
550 tristate "PCF8574 Keypad input device"
Kees Cooke52278a2012-10-24 23:53:02 -0700551 depends on I2C
Bryan Wub91c4be2010-03-19 22:18:15 -0700552 help
Masanari Iida393f9ff2012-01-31 00:07:33 -0800553 Say Y here if you want to support a keypad connected via I2C
Bryan Wub91c4be2010-03-19 22:18:15 -0700554 with a PCF8574.
555
556 To compile this driver as a module, choose M here: the
557 module will be called pcf8574_keypad.
558
Lars-Peter Clausene22739d2010-07-14 00:25:21 -0700559config INPUT_PWM_BEEPER
560 tristate "PWM beeper support"
Sascha Hauer557fe992014-01-24 08:54:16 +0100561 depends on PWM
Lars-Peter Clausene22739d2010-07-14 00:25:21 -0700562 help
563 Say Y here to get support for PWM based beeper devices.
564
565 If unsure, say N.
566
567 To compile this driver as a module, choose M here: the module will be
568 called pwm-beeper.
569
Daniel Mack73969ff2009-03-04 23:27:14 -0800570config INPUT_GPIO_ROTARY_ENCODER
571 tristate "Rotary encoders connected to GPIO pins"
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700572 depends on GPIOLIB
Daniel Mack73969ff2009-03-04 23:27:14 -0800573 help
574 Say Y here to add support for rotary encoders connected to GPIO lines.
Alessio Igor Bogani492d0f92009-05-21 19:54:33 +0200575 Check file:Documentation/input/rotary-encoder.txt for more
Daniel Mack73969ff2009-03-04 23:27:14 -0800576 information.
577
578 To compile this driver as a module, choose M here: the
579 module will be called rotary_encoder.
580
Phil Sutterd9bdffd2009-03-04 23:27:15 -0800581config INPUT_RB532_BUTTON
582 tristate "Mikrotik Routerboard 532 button interface"
583 depends on MIKROTIK_RB532
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700584 depends on GPIOLIB
Phil Sutterd9bdffd2009-03-04 23:27:15 -0800585 select INPUT_POLLDEV
586 help
587 Say Y here if you want support for the S1 button built into
588 Mikrotik's Routerboard 532.
589
590 To compile this driver as a module, choose M here: the
591 module will be called rb532_button.
592
Ashish Jangamf0c5f652012-03-04 08:40:58 -0800593config INPUT_DA9052_ONKEY
594 tristate "Dialog DA9052/DA9053 Onkey"
595 depends on PMIC_DA9052
596 help
597 Support the ONKEY of Dialog DA9052 PMICs as an input device
598 reporting power button status.
599
600 To compile this driver as a module, choose M here: the
601 module will be called da9052_onkey.
602
Ashish Jangam8ed27572012-10-30 00:27:25 -0700603config INPUT_DA9055_ONKEY
604 tristate "Dialog Semiconductor DA9055 ONKEY"
605 depends on MFD_DA9055
606 help
607 Support the ONKEY of DA9055 PMICs as an input device
608 reporting power button status.
609
610 To compile this driver as a module, choose M here: the module
611 will be called da9055_onkey.
612
David Brownelleb990b52009-04-23 19:25:29 -0700613config INPUT_DM355EVM
614 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
615 depends on MFD_DM355EVM_MSP
Dmitry Torokhov66040722009-12-04 10:22:25 -0800616 select INPUT_SPARSEKMAP
David Brownelleb990b52009-04-23 19:25:29 -0700617 help
618 Supports the pushbuttons and IR remote used with
619 the DM355 EVM board.
620
621 To compile this driver as a module, choose M here: the
622 module will be called dm355evm_keys.
Michael Hennerich48329582009-07-22 21:51:34 -0700623
624config INPUT_BFIN_ROTARY
625 tristate "Blackfin Rotary support"
626 depends on BF54x || BF52x
627 help
628 Say Y here if you want to use the Blackfin Rotary.
629
630 To compile this driver as a module, choose M here: the
631 module will be called bfin-rotary.
632
Mark Brown0c73b992009-09-15 12:07:12 +0200633config INPUT_WM831X_ON
634 tristate "WM831X ON pin"
635 depends on MFD_WM831X
636 help
637 Support the ON pin of WM831X PMICs as an input device
638 reporting power button status.
639
640 To compile this driver as a module, choose M here: the module
641 will be called wm831x_on.
642
Daniel Ribeirod0a82132009-08-10 20:27:48 +0200643config INPUT_PCAP
644 tristate "Motorola EZX PCAP misc input events"
645 depends on EZX_PCAP
646 help
647 Say Y here if you want to use Power key and Headphone button
648 on Motorola EZX phones.
649
650 To compile this driver as a module, choose M here: the
651 module will be called pcap_keys.
652
Michael Henneriche27c7292010-06-25 08:44:10 -0700653config INPUT_ADXL34X
654 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
655 default n
656 help
657 Say Y here if you have a Accelerometer interface using the
658 ADXL345/6 controller, and your board-specific initialization
659 code includes that in its table of devices.
660
661 This driver can use either I2C or SPI communication to the
662 ADXL345/6 controller. Select the appropriate method for
663 your system.
664
665 If unsure, say N (but it's safe to say "Y").
666
667 To compile this driver as a module, choose M here: the
668 module will be called adxl34x.
669
670config INPUT_ADXL34X_I2C
671 tristate "support I2C bus connection"
672 depends on INPUT_ADXL34X && I2C
673 default y
674 help
675 Say Y here if you have ADXL345/6 hooked to an I2C bus.
676
677 To compile this driver as a module, choose M here: the
678 module will be called adxl34x-i2c.
679
680config INPUT_ADXL34X_SPI
681 tristate "support SPI bus connection"
682 depends on INPUT_ADXL34X && SPI
683 default y
684 help
685 Say Y here if you have ADXL345/6 hooked to a SPI bus.
686
687 To compile this driver as a module, choose M here: the
688 module will be called adxl34x-spi.
689
Dmitry Torokhov628329d2013-02-02 11:26:13 -0800690config INPUT_IMS_PCU
691 tristate "IMS Passenger Control Unit driver"
692 depends on USB
693 depends on LEDS_CLASS
694 help
695 Say Y here if you have system with IMS Rave Passenger Control Unit.
696
697 To compile this driver as a module, choose M here: the module will be
698 called ims_pcu.
699
Hemanth Vb029ffa2010-11-30 23:03:54 -0800700config INPUT_CMA3000
701 tristate "VTI CMA3000 Tri-axis accelerometer"
702 help
703 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
704 driver
705
706 This driver currently only supports I2C interface to the
707 controller. Also select the I2C method.
708
709 If unsure, say N
710
711 To compile this driver as a module, choose M here: the
712 module will be called cma3000_d0x.
713
714config INPUT_CMA3000_I2C
715 tristate "Support I2C bus connection"
716 depends on INPUT_CMA3000 && I2C
717 help
718 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
719 through I2C interface.
720
721 To compile this driver as a module, choose M here: the
722 module will be called cma3000_d0x_i2c.
723
Dmitry Torokhov49851ca2011-03-16 22:56:03 -0700724config INPUT_XEN_KBDDEV_FRONTEND
725 tristate "Xen virtual keyboard and mouse support"
Andrew Jones4bc25af2012-01-06 10:43:09 +0100726 depends on XEN
Dmitry Torokhov49851ca2011-03-16 22:56:03 -0700727 default y
728 select XEN_XENBUS_FRONTEND
729 help
730 This driver implements the front-end of the Xen virtual
731 keyboard and mouse device driver. It communicates with a back-end
732 in another domain.
733
734 To compile this driver as a module, choose M here: the
735 module will be called xen-kbdfront.
736
Binghua Duan9b5f9532013-06-02 23:38:46 -0700737config INPUT_SIRFSOC_ONKEY
738 bool "CSR SiRFSoC power on/off/suspend key support"
739 depends on ARCH_SIRF && OF
740 default y
741 help
742 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
743 in Linux, after you press the onkey, system will suspend.
744
745 If unsure, say N.
746
Andrey Moiseev1ea4c162013-08-25 22:51:15 -0700747config INPUT_IDEAPAD_SLIDEBAR
748 tristate "IdeaPad Laptop Slidebar"
749 depends on INPUT
750 depends on SERIO_I8042
751 help
752 Say Y here if you have an IdeaPad laptop with a slidebar.
753
754 To compile this driver as a module, choose M here: the
755 module will be called ideapad_slidebar.
756
Lejun Zhu61cd4822014-03-30 23:12:00 -0700757config INPUT_SOC_BUTTON_ARRAY
758 tristate "Windows-compatible SoC Button Array"
759 depends on KEYBOARD_GPIO
760 help
761 Say Y here if you have a SoC-based tablet that originally
762 runs Windows 8.
763
764 To compile this driver as a module, choose M here: the
765 module will be called soc_button_array.
766
Dan Murphy7132fe42014-08-17 09:24:26 -0700767config INPUT_DRV260X_HAPTICS
768 tristate "TI DRV260X haptics support"
769 depends on INPUT && I2C && GPIOLIB
770 select INPUT_FF_MEMLESS
771 select REGMAP_I2C
772 help
773 Say Y to enable support for the TI DRV260X haptics driver.
774
775 To compile this driver as a module, choose M here: the
776 module will be called drv260x-haptics.
777
Dan Murphy1c246222014-09-08 16:10:49 -0700778config INPUT_DRV2667_HAPTICS
779 tristate "TI DRV2667 haptics support"
780 depends on INPUT && I2C
781 select INPUT_FF_MEMLESS
782 select REGMAP_I2C
783 help
784 Say Y to enable support for the TI DRV2667 haptics driver.
785
786 To compile this driver as a module, choose M here: the
787 module will be called drv260x-haptics.
788
Linus Torvalds1da177e2005-04-16 15:20:36 -0700789endif