blob: 36382e5b7703cfe75287cd0f92b8f63612b9b218 [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
Haojian Zhuang37345742010-05-22 00:57:26 -0700147config 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.
153
154 To compile this driver as a module, choose M here: the module
155 will be called max8925_onkey.
156
Donggeun Kim104594b02012-03-16 12:28:22 -0700157config INPUT_MAX8997_HAPTIC
158 tristate "MAXIM MAX8997 haptic controller support"
Sascha Hauer557fe992014-01-24 08:54:16 +0100159 depends on PWM && MFD_MAX8997
Donggeun Kim104594b02012-03-16 12:28:22 -0700160 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.
165
166 To compile this driver as module, choose M here: the
167 module will be called max8997-haptic.
168
Philippe Rétornaz30fc7ac2011-09-18 18:10:53 +0200169config INPUT_MC13783_PWRBUTTON
170 tristate "MC13783 ON buttons"
Alexander Shiyane5a3da22013-12-14 17:03:10 +0400171 depends on MFD_MC13XXX
Philippe Rétornaz30fc7ac2011-09-18 18:10:53 +0200172 help
173 Support the ON buttons of MC13783 PMIC as an input device
174 reporting power button status.
175
176 To compile this driver as a module, choose M here: the module
177 will be called mc13783-pwrbutton.
178
Eric Miao3ead8b52011-06-22 01:02:50 -0700179config 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.
186
187 To compile this driver as a module, choose M here: the
188 module will be called mma8450.
189
Joseph Lai631b16e2011-06-27 13:26:53 -0700190config 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.
196
197 To compile this driver as a module, choose M here: the
198 module will be called mpu3050.
199
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500200config INPUT_APANEL
201 tristate "Fujitsu Lifebook Application Panel buttons"
Randy Dunlap19131302008-03-04 14:29:43 -0800202 depends on X86 && I2C && LEDS_CLASS
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500203 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
Randy Dunlap19131302008-03-04 14:29:43 -0800208 an SMBus interface managed by the I2C Intel ICH (i801) driver,
209 which you should also build for this kernel.
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500210
211 To compile this driver as a module, choose M here: the module will
212 be called apanel.
213
Courtney Cavinff803ed2011-12-11 23:38:27 -0800214config INPUT_GP2A
215 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
216 depends on I2C
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700217 depends on GPIOLIB
Courtney Cavinff803ed2011-12-11 23:38:27 -0800218 help
219 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
220 hooked to an I2C bus.
221
222 To compile this driver as a module, choose M here: the
223 module will be called gp2ap002a00f.
224
Alexander Shiyan976358e2013-11-25 19:17:09 -0800225config INPUT_GPIO_BEEPER
226 tristate "Generic GPIO Beeper support"
Alexander Shiyanc95dc012014-04-25 23:45:05 -0700227 depends on GPIOLIB
Alexander Shiyan976358e2013-11-25 19:17:09 -0800228 help
229 Say Y here if you have a beeper connected to a GPIO pin.
230
231 To compile this driver as a module, choose M here: the
232 module will be called gpio-beeper.
233
Heiko Stübner3bfd5c52011-11-29 11:04:09 -0800234config INPUT_GPIO_TILT_POLLED
235 tristate "Polled GPIO tilt switch"
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700236 depends on GPIOLIB
Heiko Stübner3bfd5c52011-11-29 11:04:09 -0800237 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.
241
242 The list of gpios to use and the mapping of their states
243 to specific angles is done via platform data.
244
245 To compile this driver as a module, choose M here: the
246 module will be called gpio_tilt_polled.
247
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400248config 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.
254
255 If unsure, say Y.
256
257 To compile this driver as a module, choose M here: the
258 module will be called ixp4xx-beeper.
259
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500260config INPUT_COBALT_BTNS
261 tristate "Cobalt button interface"
262 depends on MIPS_COBALT
Dmitry Torokhov3d29cdf2007-04-29 23:43:06 -0400263 select INPUT_POLLDEV
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500264 help
265 Say Y here if you want to support MIPS Cobalt button interface.
266
267 To compile this driver as a module, choose M here: the
268 module will be called cobalt_btns.
269
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500270config INPUT_WISTRON_BTNS
271 tristate "x86 Wistron laptop button interface"
Jean Delvare86234eb2014-03-11 23:09:08 -0700272 depends on X86_32
Dmitry Torokhovc2554c92007-05-22 23:48:39 -0400273 select INPUT_POLLDEV
Dmitry Torokhove97af4c2009-12-04 10:22:24 -0800274 select INPUT_SPARSEKMAP
Eric Piel389679d2007-05-21 00:46:31 -0400275 select NEW_LEDS
276 select LEDS_CLASS
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700277 select CHECK_SIGNATURE
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500278 help
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200279 Say Y here for support of Wistron laptop button interfaces, used on
Eric Piel389679d2007-05-21 00:46:31 -0400280 laptops of various brands, including Acer and Fujitsu-Siemens. If
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200281 available, mail and wifi LEDs will be controllable via /sys/class/leds.
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500282
283 To compile this driver as a module, choose M here: the module will
284 be called wistron_btns.
285
Jaya Kumar31ea7ff2007-02-10 01:29:00 -0500286config 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.
292
293 To compile this driver as a module, choose M here: the module will
294 be called atlas_btns.
295
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400296config INPUT_ATI_REMOTE2
297 tristate "ATI / Philips USB RF remote control"
Al Viro7a86ede2007-05-15 20:36:20 +0100298 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400299 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.
307
308 To compile this driver as a module, choose M here: the module will be
309 called ati_remote2.
310
311config INPUT_KEYSPAN_REMOTE
Kees Cooke52278a2012-10-24 23:53:02 -0700312 tristate "Keyspan DMR USB remote control"
Al Viro7a86ede2007-05-15 20:36:20 +0100313 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400314 select USB
315 help
316 Say Y here if you want to use a Keyspan DMR USB remote control.
317 Currently only the UIA-11 type of receiver has been tested. The tag
318 on the receiver that connects to the USB port should have a P/N that
319 will tell you what type of DMR you have. The UIA-10 type is not
320 supported at this time. This driver maps all buttons to keypress
321 events.
322
323 To compile this driver as a module, choose M here: the module will
324 be called keyspan_remote.
325
Chris Hudsone8e70d82011-07-06 18:36:51 -0700326config INPUT_KXTJ9
327 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
328 depends on I2C
329 help
330 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
331 accelerometer.
332
333 To compile this driver as a module, choose M here: the module will
334 be called kxtj9.
335
336config INPUT_KXTJ9_POLLED_MODE
337 bool "Enable polling mode support"
338 depends on INPUT_KXTJ9
339 select INPUT_POLLDEV
340 help
341 Say Y here if you need accelerometer to work in polling mode.
342
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400343config INPUT_POWERMATE
344 tristate "Griffin PowerMate and Contour Jog support"
Al Viro7a86ede2007-05-15 20:36:20 +0100345 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400346 select USB
347 help
348 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
349 These are aluminum dials which can measure clockwise and anticlockwise
350 rotation. The dial also acts as a pushbutton. The base contains an LED
351 which can be instructed to pulse or to switch to a particular intensity.
352
353 You can download userspace tools from
354 <http://sowerbutts.com/powermate/>.
Alessandro Zummo01387952006-01-29 21:50:40 -0500355
356 To compile this driver as a module, choose M here: the
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400357 module will be called powermate.
358
359config INPUT_YEALINK
360 tristate "Yealink usb-p1k voip phone"
Al Viro7a86ede2007-05-15 20:36:20 +0100361 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400362 select USB
363 help
364 Say Y here if you want to enable keyboard and LCD functions of the
365 Yealink usb-p1k usb phones. The audio part is enabled by the generic
366 usb sound driver, so you might want to enable that as well.
367
368 For information about how to use these additional functions, see
369 <file:Documentation/input/yealink.txt>.
370
371 To compile this driver as a module, choose M here: the module will be
372 called yealink.
Alessandro Zummo01387952006-01-29 21:50:40 -0500373
Alfred E. Heggestadc04148f2008-08-08 11:49:08 -0400374config INPUT_CM109
375 tristate "C-Media CM109 USB I/O Controller"
Alfred E. Heggestadc04148f2008-08-08 11:49:08 -0400376 depends on USB_ARCH_HAS_HCD
377 select USB
378 help
379 Say Y here if you want to enable keyboard and buzzer functions of the
380 C-Media CM109 usb phones. The audio part is enabled by the generic
381 usb sound driver, so you might want to enable that as well.
382
383 To compile this driver as a module, choose M here: the module will be
384 called cm109.
385
Aaro Koskinen544a46c2012-11-10 00:50:25 -0800386config INPUT_RETU_PWRBUTTON
387 tristate "Retu Power button Driver"
388 depends on MFD_RETU
389 help
390 Say Y here if you want to enable power key reporting via the
391 Retu chips found in Nokia Internet Tablets (770, N800, N810).
392
393 To compile this driver as a module, choose M here. The module will
394 be called retu-pwrbutton.
395
Felipe Balbi68d8bf02009-04-19 23:07:50 -0700396config INPUT_TWL4030_PWRBUTTON
397 tristate "TWL4030 Power button Driver"
398 depends on TWL4030_CORE
399 help
400 Say Y here if you want to enable power key reporting via the
401 TWL4030 family of chips.
402
403 To compile this driver as a module, choose M here. The module will
404 be called twl4030_pwrbutton.
405
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800406config INPUT_TWL4030_VIBRA
407 tristate "Support for TWL4030 Vibrator"
408 depends on TWL4030_CORE
Peter Ujfalusi57fe7252011-05-31 12:02:49 +0300409 select MFD_TWL4030_AUDIO
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800410 select INPUT_FF_MEMLESS
411 help
412 This option enables support for TWL4030 Vibrator Driver.
413
414 To compile this driver as a module, choose M here. The module will
415 be called twl4030_vibra.
416
Misael Lopez Cruzcc697d382011-05-01 03:51:24 -0500417config INPUT_TWL6040_VIBRA
418 tristate "Support for TWL6040 Vibrator"
Peter Ujfalusi8eaeb932012-04-03 11:56:51 +0300419 depends on TWL6040_CORE
Misael Lopez Cruzcc697d382011-05-01 03:51:24 -0500420 select INPUT_FF_MEMLESS
421 help
422 This option enables support for TWL6040 Vibrator Driver.
423
424 To compile this driver as a module, choose M here. The module will
425 be called twl6040_vibra.
426
Linus Torvalds1da177e2005-04-16 15:20:36 -0700427config INPUT_UINPUT
428 tristate "User level driver support"
429 help
430 Say Y here if you want to support user level drivers for input
431 subsystem accessible under char device 10:223 - /dev/input/uinput.
432
433 To compile this driver as a module, choose M here: the
434 module will be called uinput.
435
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400436config INPUT_SGI_BTNS
437 tristate "SGI Indy/O2 volume button interface"
438 depends on SGI_IP22 || SGI_IP32
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400439 select INPUT_POLLDEV
440 help
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400441 Say Y here if you want to support SGI Indy/O2 volume button interface.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400442
443 To compile this driver as a module, choose M here: the
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400444 module will be called sgi_btns.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400445
Linus Torvalds1da177e2005-04-16 15:20:36 -0700446config HP_SDC_RTC
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500447 tristate "HP SDC Real Time Clock"
Alexander Beregalovd061ebd2009-04-11 16:55:41 -0700448 depends on (GSC || HP300) && SERIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700449 select HP_SDC
450 help
451 Say Y here if you want to support the built-in real time clock
452 of the HP SDC controller.
453
Nishanth Menonadff5962014-08-26 15:57:47 -0700454config INPUT_PALMAS_PWRBUTTON
455 tristate "Palmas Power button Driver"
456 depends on MFD_PALMAS
457 help
458 Say Y here if you want to enable power key reporting via the
459 Palmas family of PMICs.
460
461 To compile this driver as a module, choose M here. The module will
462 be called palmas_pwrbutton.
463
Balaji Rao1851b062009-01-09 01:50:58 +0100464config INPUT_PCF50633_PMU
465 tristate "PCF50633 PMU events"
466 depends on MFD_PCF50633
467 help
468 Say Y to include support for delivering PMU events via input
469 layer on NXP PCF50633.
470
Bryan Wub91c4be2010-03-19 22:18:15 -0700471config INPUT_PCF8574
472 tristate "PCF8574 Keypad input device"
Kees Cooke52278a2012-10-24 23:53:02 -0700473 depends on I2C
Bryan Wub91c4be2010-03-19 22:18:15 -0700474 help
Masanari Iida393f9ff2012-01-31 00:07:33 -0800475 Say Y here if you want to support a keypad connected via I2C
Bryan Wub91c4be2010-03-19 22:18:15 -0700476 with a PCF8574.
477
478 To compile this driver as a module, choose M here: the
479 module will be called pcf8574_keypad.
480
Lars-Peter Clausene22739d2010-07-14 00:25:21 -0700481config INPUT_PWM_BEEPER
482 tristate "PWM beeper support"
Sascha Hauer557fe992014-01-24 08:54:16 +0100483 depends on PWM
Lars-Peter Clausene22739d2010-07-14 00:25:21 -0700484 help
485 Say Y here to get support for PWM based beeper devices.
486
487 If unsure, say N.
488
489 To compile this driver as a module, choose M here: the module will be
490 called pwm-beeper.
491
Daniel Mack73969ff2009-03-04 23:27:14 -0800492config INPUT_GPIO_ROTARY_ENCODER
493 tristate "Rotary encoders connected to GPIO pins"
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700494 depends on GPIOLIB
Daniel Mack73969ff2009-03-04 23:27:14 -0800495 help
496 Say Y here to add support for rotary encoders connected to GPIO lines.
Alessio Igor Bogani492d0f92009-05-21 19:54:33 +0200497 Check file:Documentation/input/rotary-encoder.txt for more
Daniel Mack73969ff2009-03-04 23:27:14 -0800498 information.
499
500 To compile this driver as a module, choose M here: the
501 module will be called rotary_encoder.
502
Phil Sutterd9bdffd2009-03-04 23:27:15 -0800503config INPUT_RB532_BUTTON
504 tristate "Mikrotik Routerboard 532 button interface"
505 depends on MIKROTIK_RB532
Alexandre Courbot76ec9d12013-03-28 04:34:56 -0700506 depends on GPIOLIB
Phil Sutterd9bdffd2009-03-04 23:27:15 -0800507 select INPUT_POLLDEV
508 help
509 Say Y here if you want support for the S1 button built into
510 Mikrotik's Routerboard 532.
511
512 To compile this driver as a module, choose M here: the
513 module will be called rb532_button.
514
Ashish Jangamf0c5f652012-03-04 08:40:58 -0800515config INPUT_DA9052_ONKEY
516 tristate "Dialog DA9052/DA9053 Onkey"
517 depends on PMIC_DA9052
518 help
519 Support the ONKEY of Dialog DA9052 PMICs as an input device
520 reporting power button status.
521
522 To compile this driver as a module, choose M here: the
523 module will be called da9052_onkey.
524
Ashish Jangam8ed27572012-10-30 00:27:25 -0700525config INPUT_DA9055_ONKEY
526 tristate "Dialog Semiconductor DA9055 ONKEY"
527 depends on MFD_DA9055
528 help
529 Support the ONKEY of DA9055 PMICs as an input device
530 reporting power button status.
531
532 To compile this driver as a module, choose M here: the module
533 will be called da9055_onkey.
534
David Brownelleb990b52009-04-23 19:25:29 -0700535config INPUT_DM355EVM
536 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
537 depends on MFD_DM355EVM_MSP
Dmitry Torokhov66040722009-12-04 10:22:25 -0800538 select INPUT_SPARSEKMAP
David Brownelleb990b52009-04-23 19:25:29 -0700539 help
540 Supports the pushbuttons and IR remote used with
541 the DM355 EVM board.
542
543 To compile this driver as a module, choose M here: the
544 module will be called dm355evm_keys.
Michael Hennerich48329582009-07-22 21:51:34 -0700545
546config INPUT_BFIN_ROTARY
547 tristate "Blackfin Rotary support"
548 depends on BF54x || BF52x
549 help
550 Say Y here if you want to use the Blackfin Rotary.
551
552 To compile this driver as a module, choose M here: the
553 module will be called bfin-rotary.
554
Mark Brown0c73b992009-09-15 12:07:12 +0200555config INPUT_WM831X_ON
556 tristate "WM831X ON pin"
557 depends on MFD_WM831X
558 help
559 Support the ON pin of WM831X PMICs as an input device
560 reporting power button status.
561
562 To compile this driver as a module, choose M here: the module
563 will be called wm831x_on.
564
Daniel Ribeirod0a82132009-08-10 20:27:48 +0200565config INPUT_PCAP
566 tristate "Motorola EZX PCAP misc input events"
567 depends on EZX_PCAP
568 help
569 Say Y here if you want to use Power key and Headphone button
570 on Motorola EZX phones.
571
572 To compile this driver as a module, choose M here: the
573 module will be called pcap_keys.
574
Michael Henneriche27c7292010-06-25 08:44:10 -0700575config INPUT_ADXL34X
576 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
577 default n
578 help
579 Say Y here if you have a Accelerometer interface using the
580 ADXL345/6 controller, and your board-specific initialization
581 code includes that in its table of devices.
582
583 This driver can use either I2C or SPI communication to the
584 ADXL345/6 controller. Select the appropriate method for
585 your system.
586
587 If unsure, say N (but it's safe to say "Y").
588
589 To compile this driver as a module, choose M here: the
590 module will be called adxl34x.
591
592config INPUT_ADXL34X_I2C
593 tristate "support I2C bus connection"
594 depends on INPUT_ADXL34X && I2C
595 default y
596 help
597 Say Y here if you have ADXL345/6 hooked to an I2C bus.
598
599 To compile this driver as a module, choose M here: the
600 module will be called adxl34x-i2c.
601
602config INPUT_ADXL34X_SPI
603 tristate "support SPI bus connection"
604 depends on INPUT_ADXL34X && SPI
605 default y
606 help
607 Say Y here if you have ADXL345/6 hooked to a SPI bus.
608
609 To compile this driver as a module, choose M here: the
610 module will be called adxl34x-spi.
611
Dmitry Torokhov628329d2013-02-02 11:26:13 -0800612config INPUT_IMS_PCU
613 tristate "IMS Passenger Control Unit driver"
614 depends on USB
615 depends on LEDS_CLASS
616 help
617 Say Y here if you have system with IMS Rave Passenger Control Unit.
618
619 To compile this driver as a module, choose M here: the module will be
620 called ims_pcu.
621
Hemanth Vb029ffa2010-11-30 23:03:54 -0800622config INPUT_CMA3000
623 tristate "VTI CMA3000 Tri-axis accelerometer"
624 help
625 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
626 driver
627
628 This driver currently only supports I2C interface to the
629 controller. Also select the I2C method.
630
631 If unsure, say N
632
633 To compile this driver as a module, choose M here: the
634 module will be called cma3000_d0x.
635
636config INPUT_CMA3000_I2C
637 tristate "Support I2C bus connection"
638 depends on INPUT_CMA3000 && I2C
639 help
640 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
641 through I2C interface.
642
643 To compile this driver as a module, choose M here: the
644 module will be called cma3000_d0x_i2c.
645
Dmitry Torokhov49851ca2011-03-16 22:56:03 -0700646config INPUT_XEN_KBDDEV_FRONTEND
647 tristate "Xen virtual keyboard and mouse support"
Andrew Jones4bc25af2012-01-06 10:43:09 +0100648 depends on XEN
Dmitry Torokhov49851ca2011-03-16 22:56:03 -0700649 default y
650 select XEN_XENBUS_FRONTEND
651 help
652 This driver implements the front-end of the Xen virtual
653 keyboard and mouse device driver. It communicates with a back-end
654 in another domain.
655
656 To compile this driver as a module, choose M here: the
657 module will be called xen-kbdfront.
658
Binghua Duan9b5f9532013-06-02 23:38:46 -0700659config INPUT_SIRFSOC_ONKEY
660 bool "CSR SiRFSoC power on/off/suspend key support"
661 depends on ARCH_SIRF && OF
662 default y
663 help
664 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
665 in Linux, after you press the onkey, system will suspend.
666
667 If unsure, say N.
668
Andrey Moiseev1ea4c162013-08-25 22:51:15 -0700669config INPUT_IDEAPAD_SLIDEBAR
670 tristate "IdeaPad Laptop Slidebar"
671 depends on INPUT
672 depends on SERIO_I8042
673 help
674 Say Y here if you have an IdeaPad laptop with a slidebar.
675
676 To compile this driver as a module, choose M here: the
677 module will be called ideapad_slidebar.
678
Lejun Zhu61cd4822014-03-30 23:12:00 -0700679config INPUT_SOC_BUTTON_ARRAY
680 tristate "Windows-compatible SoC Button Array"
681 depends on KEYBOARD_GPIO
682 help
683 Say Y here if you have a SoC-based tablet that originally
684 runs Windows 8.
685
686 To compile this driver as a module, choose M here: the
687 module will be called soc_button_array.
688
Dan Murphy7132fe42014-08-17 09:24:26 -0700689config INPUT_DRV260X_HAPTICS
690 tristate "TI DRV260X haptics support"
691 depends on INPUT && I2C && GPIOLIB
692 select INPUT_FF_MEMLESS
693 select REGMAP_I2C
694 help
695 Say Y to enable support for the TI DRV260X haptics driver.
696
697 To compile this driver as a module, choose M here: the
698 module will be called drv260x-haptics.
699
Dan Murphy1c246222014-09-08 16:10:49 -0700700config INPUT_DRV2667_HAPTICS
701 tristate "TI DRV2667 haptics support"
702 depends on INPUT && I2C
703 select INPUT_FF_MEMLESS
704 select REGMAP_I2C
705 help
706 Say Y to enable support for the TI DRV2667 haptics driver.
707
708 To compile this driver as a module, choose M here: the
709 module will be called drv260x-haptics.
710
Linus Torvalds1da177e2005-04-16 15:20:36 -0700711endif