Merge remote-tracking branch 'ftrace/for-next'
[deliverable/linux.git] / drivers / input / misc / Kconfig
CommitLineData
1da177e4
LT
1#
2# Input misc drivers configuration
3#
4menuconfig INPUT_MISC
5 bool "Miscellaneous devices"
6 help
7 Say Y here, and a list of miscellaneous input drivers will be displayed.
8 Everything that didn't fit into the other categories is here. This option
9 doesn't affect the kernel.
10
11 If unsure, say Y.
12
13if INPUT_MISC
14
69854031
HZ
15config INPUT_88PM860X_ONKEY
16 tristate "88PM860x ONKEY support"
17 depends on MFD_88PM860X
18 help
19 Support the ONKEY of Marvell 88PM860x PMICs as an input device
20 reporting power button status.
21
22 To compile this driver as a module, choose M here: the module
23 will be called 88pm860x_onkey.
24
96c905f4
QZ
25config 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
77686517
SI
35config 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
31a62963
BW
45config INPUT_AD714X
46 tristate "Analog Devices AD714x Capacitance Touch Sensor"
47 help
6c04d7b3 48 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
31a62963
BW
49
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
9dd555e2
MB
75config 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
b06d43f7
DHW
85config INPUT_ATMEL_CAPTOUCH
86 tristate "Atmel Capacitive Touch Button Driver"
87 depends on OF || COMPILE_TEST
14f935f9 88 depends on I2C
b06d43f7
DHW
89 help
90 Say Y here if an Atmel Capacitive Touch Button device which
91 implements "captouch" protocol is connected to I2C bus. Typically
92 this device consists of Atmel Touch sensor controlled by AtMegaXX
93 MCU running firmware based on Qtouch library.
94 One should find "atmel,captouch" node in the board specific DTS.
95
96 To compile this driver as a module, choose M here: the
97 module will be called atmel_captouch.
98
c17ca3f5
EA
99config INPUT_BMA150
100 tristate "BMA150/SMB380 acceleration sensor support"
101 depends on I2C
102 select INPUT_POLLDEV
103 help
104 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
105 acceleration sensor hooked to an I2C bus.
106
107 To compile this driver as a module, choose M here: the
108 module will be called bma150.
109
846a7fc8 110config INPUT_E3X0_BUTTON
05f216dd 111 tristate "NI Ettus Research USRP E3xx Button support."
846a7fc8
MF
112 default n
113 help
114 Say Y here to enable support for the NI Ettus Research
05f216dd 115 USRP E3xx Button.
846a7fc8
MF
116
117 To compile this driver as a module, choose M here: the
118 module will be called e3x0_button.
119
1da177e4
LT
120config INPUT_PCSPKR
121 tristate "PC Speaker support"
e5e1d3cb 122 depends on PCSPKR_PLATFORM
1da177e4
LT
123 help
124 Say Y here if you want the standard PC Speaker to be used for
125 bells and whistles.
126
127 If unsure, say Y.
128
129 To compile this driver as a module, choose M here: the
130 module will be called pcspkr.
131
68c581d5
CC
132config INPUT_PM8941_PWRKEY
133 tristate "Qualcomm PM8941 power key support"
134 depends on MFD_SPMI_PMIC
135 help
136 Say Y here if you want support for the power key usually found
137 on boards using a Qualcomm PM8941 compatible PMIC.
138
139 If unsure, say Y.
140
141 To compile this driver as a module, choose M here: the module
142 will be called pm8941-pwrkey.
143
11205bb6
AM
144config INPUT_PM8XXX_VIBRATOR
145 tristate "Qualcomm PM8XXX vibrator support"
146 depends on MFD_PM8XXX
147 select INPUT_FF_MEMLESS
148 help
149 This option enables device driver support for the vibrator
150 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
151 from input framework.
152
153 To compile this driver as module, choose M here: the
154 module will be called pm8xxx-vibrator.
155
156config INPUT_PMIC8XXX_PWRKEY
157 tristate "PMIC8XXX power key support"
158 depends on MFD_PM8XXX
159 help
160 Say Y here if you want support for the PMIC8XXX power key.
161
162 If unsure, say N.
163
164 To compile this driver as a module, choose M here: the
165 module will be called pmic8xxx-pwrkey.
166
1da177e4
LT
167config INPUT_SPARCSPKR
168 tristate "SPARC Speaker support"
a2bd4fd1 169 depends on PCI && SPARC64
1da177e4
LT
170 help
171 Say Y here if you want the standard Speaker on Sparc PCI systems
172 to be used for bells and whistles.
173
174 If unsure, say Y.
175
176 To compile this driver as a module, choose M here: the
177 module will be called sparcspkr.
178
179config INPUT_M68K_BEEP
180 tristate "M68k Beeper support"
181 depends on M68K
182
a3b3ca75 183config INPUT_MAX77693_HAPTIC
56bbc99e
KK
184 tristate "MAXIM MAX77693/MAX77843 haptic controller support"
185 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
a3b3ca75
JK
186 select INPUT_FF_MEMLESS
187 help
188 This option enables support for the haptic controller on
56bbc99e 189 MAXIM MAX77693 and MAX77843 chips.
a3b3ca75
JK
190
191 To compile this driver as module, choose M here: the
192 module will be called max77693-haptic.
193
3734574c
HZ
194config INPUT_MAX8925_ONKEY
195 tristate "MAX8925 ONKEY support"
196 depends on MFD_MAX8925
197 help
198 Support the ONKEY of MAX8925 PMICs as an input device
199 reporting power button status.
200
201 To compile this driver as a module, choose M here: the module
202 will be called max8925_onkey.
203
104594b0
DK
204config INPUT_MAX8997_HAPTIC
205 tristate "MAXIM MAX8997 haptic controller support"
557fe99d 206 depends on PWM && MFD_MAX8997
104594b0
DK
207 select INPUT_FF_MEMLESS
208 help
209 This option enables device driver support for the haptic controller
210 on MAXIM MAX8997 chip. This driver supports ff-memless interface
211 from input framework.
212
213 To compile this driver as module, choose M here: the
214 module will be called max8997-haptic.
215
30fc7ac3
PR
216config INPUT_MC13783_PWRBUTTON
217 tristate "MC13783 ON buttons"
e5a3da21 218 depends on MFD_MC13XXX
30fc7ac3
PR
219 help
220 Support the ON buttons of MC13783 PMIC as an input device
221 reporting power button status.
222
223 To compile this driver as a module, choose M here: the module
224 will be called mc13783-pwrbutton.
225
3ead8b5d
EM
226config INPUT_MMA8450
227 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
228 depends on I2C
229 select INPUT_POLLDEV
230 help
231 Say Y here if you want to support Freescale's MMA8450 Accelerometer
232 through I2C interface.
233
234 To compile this driver as a module, choose M here: the
235 module will be called mma8450.
236
631b16e8
JL
237config INPUT_MPU3050
238 tristate "MPU3050 Triaxial gyroscope sensor"
239 depends on I2C
240 help
241 Say Y here if you want to support InvenSense MPU3050
242 connected via an I2C bus.
243
244 To compile this driver as a module, choose M here: the
245 module will be called mpu3050.
246
52fe0cdb
SH
247config INPUT_APANEL
248 tristate "Fujitsu Lifebook Application Panel buttons"
19131305 249 depends on X86 && I2C && LEDS_CLASS
52fe0cdb
SH
250 select INPUT_POLLDEV
251 select CHECK_SIGNATURE
252 help
253 Say Y here for support of the Application Panel buttons, used on
254 Fujitsu Lifebook. These are attached to the mainboard through
19131305
RD
255 an SMBus interface managed by the I2C Intel ICH (i801) driver,
256 which you should also build for this kernel.
52fe0cdb
SH
257
258 To compile this driver as a module, choose M here: the module will
259 be called apanel.
260
ff803ed4
CC
261config INPUT_GP2A
262 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
263 depends on I2C
7d6548ab 264 depends on GPIOLIB || COMPILE_TEST
ff803ed4
CC
265 help
266 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
267 hooked to an I2C bus.
268
269 To compile this driver as a module, choose M here: the
270 module will be called gp2ap002a00f.
271
976358e2
AS
272config INPUT_GPIO_BEEPER
273 tristate "Generic GPIO Beeper support"
7d6548ab 274 depends on GPIOLIB || COMPILE_TEST
976358e2
AS
275 help
276 Say Y here if you have a beeper connected to a GPIO pin.
277
278 To compile this driver as a module, choose M here: the
279 module will be called gpio-beeper.
280
3bfd5c5b
HS
281config INPUT_GPIO_TILT_POLLED
282 tristate "Polled GPIO tilt switch"
7d6548ab 283 depends on GPIOLIB || COMPILE_TEST
3bfd5c5b
HS
284 select INPUT_POLLDEV
285 help
286 This driver implements support for tilt switches connected
287 to GPIO pins that are not capable of generating interrupts.
288
289 The list of gpios to use and the mapping of their states
290 to specific angles is done via platform data.
291
292 To compile this driver as a module, choose M here: the
293 module will be called gpio_tilt_polled.
294
69464161
V
295config INPUT_GPIO_DECODER
296 tristate "Polled GPIO Decoder Input driver"
297 depends on GPIOLIB || COMPILE_TEST
298 select INPUT_POLLDEV
299 help
300 Say Y here if you want driver to read status of multiple GPIO
301 lines and report the encoded value as an absolute integer to
302 input subsystem.
303
304 To compile this driver as a module, choose M here: the module
305 will be called gpio_decoder.
306
ba0acb5e
DT
307config INPUT_IXP4XX_BEEPER
308 tristate "IXP4XX Beeper support"
309 depends on ARCH_IXP4XX
310 help
311 If you say yes here, you can connect a beeper to the
312 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
313
314 If unsure, say Y.
315
316 To compile this driver as a module, choose M here: the
317 module will be called ixp4xx-beeper.
318
bebb8a2b
YY
319config INPUT_COBALT_BTNS
320 tristate "Cobalt button interface"
321 depends on MIPS_COBALT
3d29cdff 322 select INPUT_POLLDEV
bebb8a2b
YY
323 help
324 Say Y here if you want to support MIPS Cobalt button interface.
325
326 To compile this driver as a module, choose M here: the
327 module will be called cobalt_btns.
328
5fc14680
DT
329config INPUT_WISTRON_BTNS
330 tristate "x86 Wistron laptop button interface"
86234eb7 331 depends on X86_32
c2554c91 332 select INPUT_POLLDEV
e97af4cb 333 select INPUT_SPARSEKMAP
389679d8
EP
334 select NEW_LEDS
335 select LEDS_CLASS
928923c7 336 select CHECK_SIGNATURE
5fc14680 337 help
01dd2fbf 338 Say Y here for support of Wistron laptop button interfaces, used on
389679d8 339 laptops of various brands, including Acer and Fujitsu-Siemens. If
01dd2fbf 340 available, mail and wifi LEDs will be controllable via /sys/class/leds.
5fc14680
DT
341
342 To compile this driver as a module, choose M here: the module will
343 be called wistron_btns.
344
31ea7ff0
JK
345config INPUT_ATLAS_BTNS
346 tristate "x86 Atlas button interface"
347 depends on X86 && ACPI
348 help
349 Say Y here for support of Atlas wallmount touchscreen buttons.
350 The events will show up as scancodes F1 through F9 via evdev.
351
352 To compile this driver as a module, choose M here: the module will
353 be called atlas_btns.
354
ba0acb5e
DT
355config INPUT_ATI_REMOTE2
356 tristate "ATI / Philips USB RF remote control"
7a86edef 357 depends on USB_ARCH_HAS_HCD
ba0acb5e
DT
358 select USB
359 help
360 Say Y here if you want to use an ATI or Philips USB RF remote control.
361 These are RF remotes with USB receivers.
362 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
363 and is also available as a separate product.
364 This driver provides mouse pointer, left and right mouse buttons,
365 and maps all the other remote buttons to keypress events.
366
367 To compile this driver as a module, choose M here: the module will be
368 called ati_remote2.
369
370config INPUT_KEYSPAN_REMOTE
e52278a3 371 tristate "Keyspan DMR USB remote control"
7a86edef 372 depends on USB_ARCH_HAS_HCD
ba0acb5e
DT
373 select USB
374 help
375 Say Y here if you want to use a Keyspan DMR USB remote control.
376 Currently only the UIA-11 type of receiver has been tested. The tag
377 on the receiver that connects to the USB port should have a P/N that
378 will tell you what type of DMR you have. The UIA-10 type is not
379 supported at this time. This driver maps all buttons to keypress
380 events.
01387959 381
ba0acb5e
DT
382 To compile this driver as a module, choose M here: the module will
383 be called keyspan_remote.
384
e8e70d83
CH
385config INPUT_KXTJ9
386 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
387 depends on I2C
388 help
389 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
390 accelerometer.
391
392 To compile this driver as a module, choose M here: the module will
393 be called kxtj9.
394
395config INPUT_KXTJ9_POLLED_MODE
396 bool "Enable polling mode support"
397 depends on INPUT_KXTJ9
398 select INPUT_POLLDEV
399 help
400 Say Y here if you need accelerometer to work in polling mode.
401
ba0acb5e
DT
402config INPUT_POWERMATE
403 tristate "Griffin PowerMate and Contour Jog support"
7a86edef 404 depends on USB_ARCH_HAS_HCD
ba0acb5e
DT
405 select USB
406 help
407 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
408 These are aluminum dials which can measure clockwise and anticlockwise
409 rotation. The dial also acts as a pushbutton. The base contains an LED
410 which can be instructed to pulse or to switch to a particular intensity.
411
412 You can download userspace tools from
413 <http://sowerbutts.com/powermate/>.
01387959
AZ
414
415 To compile this driver as a module, choose M here: the
ba0acb5e
DT
416 module will be called powermate.
417
418config INPUT_YEALINK
419 tristate "Yealink usb-p1k voip phone"
7a86edef 420 depends on USB_ARCH_HAS_HCD
ba0acb5e
DT
421 select USB
422 help
423 Say Y here if you want to enable keyboard and LCD functions of the
424 Yealink usb-p1k usb phones. The audio part is enabled by the generic
425 usb sound driver, so you might want to enable that as well.
426
427 For information about how to use these additional functions, see
428 <file:Documentation/input/yealink.txt>.
429
430 To compile this driver as a module, choose M here: the module will be
431 called yealink.
01387959 432
c04148f9
AH
433config INPUT_CM109
434 tristate "C-Media CM109 USB I/O Controller"
c04148f9
AH
435 depends on USB_ARCH_HAS_HCD
436 select USB
437 help
438 Say Y here if you want to enable keyboard and buzzer functions of the
439 C-Media CM109 usb phones. The audio part is enabled by the generic
440 usb sound driver, so you might want to enable that as well.
441
442 To compile this driver as a module, choose M here: the module will be
443 called cm109.
444
d64cb71b
JK
445config INPUT_REGULATOR_HAPTIC
446 tristate "Regulator haptics support"
447 depends on REGULATOR
448 select INPUT_FF_MEMLESS
449 help
450 This option enables device driver support for the haptic controlled
451 by a regulator. This driver supports ff-memless interface
452 from input framework.
453
454 To compile this driver as a module, choose M here: the
455 module will be called regulator-haptic.
456
544a46c9
AK
457config INPUT_RETU_PWRBUTTON
458 tristate "Retu Power button Driver"
459 depends on MFD_RETU
460 help
461 Say Y here if you want to enable power key reporting via the
462 Retu chips found in Nokia Internet Tablets (770, N800, N810).
463
464 To compile this driver as a module, choose M here. The module will
465 be called retu-pwrbutton.
466
5fafed3e
FB
467config INPUT_TPS65218_PWRBUTTON
468 tristate "TPS65218 Power button driver"
722dc546 469 depends on (MFD_TPS65217 || MFD_TPS65218)
5fafed3e
FB
470 help
471 Say Y here if you want to enable power buttong reporting for
722dc546 472 TPS65217 and TPS65218 Power Management IC devices.
5fafed3e
FB
473
474 To compile this driver as a module, choose M here. The module will
475 be called tps65218-pwrbutton.
476
5b6c26a9
CC
477config INPUT_AXP20X_PEK
478 tristate "X-Powers AXP20X power button driver"
479 depends on MFD_AXP20X
480 help
481 Say Y here if you want to enable power key reporting via the
482 AXP20X PMIC.
483
484 To compile this driver as a module, choose M here. The module will
485 be called axp20x-pek.
486
487
68d8bf04
FB
488config INPUT_TWL4030_PWRBUTTON
489 tristate "TWL4030 Power button Driver"
490 depends on TWL4030_CORE
491 help
492 Say Y here if you want to enable power key reporting via the
493 TWL4030 family of chips.
494
495 To compile this driver as a module, choose M here. The module will
496 be called twl4030_pwrbutton.
497
3dd1b394
JV
498config INPUT_TWL4030_VIBRA
499 tristate "Support for TWL4030 Vibrator"
500 depends on TWL4030_CORE
57fe7251 501 select MFD_TWL4030_AUDIO
3dd1b394
JV
502 select INPUT_FF_MEMLESS
503 help
504 This option enables support for TWL4030 Vibrator Driver.
505
506 To compile this driver as a module, choose M here. The module will
507 be called twl4030_vibra.
508
cc697d38
MLC
509config INPUT_TWL6040_VIBRA
510 tristate "Support for TWL6040 Vibrator"
8eaeb939 511 depends on TWL6040_CORE
cc697d38
MLC
512 select INPUT_FF_MEMLESS
513 help
514 This option enables support for TWL6040 Vibrator Driver.
515
516 To compile this driver as a module, choose M here. The module will
517 be called twl6040_vibra.
518
1da177e4
LT
519config INPUT_UINPUT
520 tristate "User level driver support"
521 help
522 Say Y here if you want to support user level drivers for input
523 subsystem accessible under char device 10:223 - /dev/input/uinput.
524
525 To compile this driver as a module, choose M here: the
526 module will be called uinput.
527
48ad88b1
TB
528config INPUT_SGI_BTNS
529 tristate "SGI Indy/O2 volume button interface"
530 depends on SGI_IP22 || SGI_IP32
3bee2a04
TB
531 select INPUT_POLLDEV
532 help
48ad88b1 533 Say Y here if you want to support SGI Indy/O2 volume button interface.
3bee2a04
TB
534
535 To compile this driver as a module, choose M here: the
48ad88b1 536 module will be called sgi_btns.
3bee2a04 537
1da177e4 538config HP_SDC_RTC
bebb8a2b 539 tristate "HP SDC Real Time Clock"
d061ebd5 540 depends on (GSC || HP300) && SERIO
1da177e4
LT
541 select HP_SDC
542 help
543 Say Y here if you want to support the built-in real time clock
544 of the HP SDC controller.
545
adff5962
NM
546config INPUT_PALMAS_PWRBUTTON
547 tristate "Palmas Power button Driver"
548 depends on MFD_PALMAS
549 help
550 Say Y here if you want to enable power key reporting via the
551 Palmas family of PMICs.
552
553 To compile this driver as a module, choose M here. The module will
554 be called palmas_pwrbutton.
555
1851b06a
BR
556config INPUT_PCF50633_PMU
557 tristate "PCF50633 PMU events"
558 depends on MFD_PCF50633
559 help
560 Say Y to include support for delivering PMU events via input
561 layer on NXP PCF50633.
562
b91c4be7
BW
563config INPUT_PCF8574
564 tristate "PCF8574 Keypad input device"
e52278a3 565 depends on I2C
b91c4be7 566 help
393f9ffb 567 Say Y here if you want to support a keypad connected via I2C
b91c4be7
BW
568 with a PCF8574.
569
570 To compile this driver as a module, choose M here: the
571 module will be called pcf8574_keypad.
572
e22739d0
LPC
573config INPUT_PWM_BEEPER
574 tristate "PWM beeper support"
557fe99d 575 depends on PWM
e22739d0
LPC
576 help
577 Say Y here to get support for PWM based beeper devices.
578
579 If unsure, say N.
580
581 To compile this driver as a module, choose M here: the module will be
582 called pwm-beeper.
583
73969ff0
DM
584config INPUT_GPIO_ROTARY_ENCODER
585 tristate "Rotary encoders connected to GPIO pins"
7d6548ab 586 depends on GPIOLIB || COMPILE_TEST
73969ff0
DM
587 help
588 Say Y here to add support for rotary encoders connected to GPIO lines.
492d0f95 589 Check file:Documentation/input/rotary-encoder.txt for more
73969ff0
DM
590 information.
591
592 To compile this driver as a module, choose M here: the
593 module will be called rotary_encoder.
594
d9bdffd2
PS
595config INPUT_RB532_BUTTON
596 tristate "Mikrotik Routerboard 532 button interface"
597 depends on MIKROTIK_RB532
76ec9d18 598 depends on GPIOLIB
d9bdffd2
PS
599 select INPUT_POLLDEV
600 help
601 Say Y here if you want support for the S1 button built into
602 Mikrotik's Routerboard 532.
603
604 To compile this driver as a module, choose M here: the
605 module will be called rb532_button.
606
f0c5f65b
AJ
607config INPUT_DA9052_ONKEY
608 tristate "Dialog DA9052/DA9053 Onkey"
609 depends on PMIC_DA9052
610 help
611 Support the ONKEY of Dialog DA9052 PMICs as an input device
612 reporting power button status.
613
614 To compile this driver as a module, choose M here: the
615 module will be called da9052_onkey.
616
8ed2757e
AJ
617config INPUT_DA9055_ONKEY
618 tristate "Dialog Semiconductor DA9055 ONKEY"
619 depends on MFD_DA9055
620 help
621 Support the ONKEY of DA9055 PMICs as an input device
622 reporting power button status.
623
624 To compile this driver as a module, choose M here: the module
625 will be called da9055_onkey.
626
5179f0ce 627config INPUT_DA9063_ONKEY
a27b5e0a
T
628 tristate "Dialog DA9062/63 OnKey"
629 depends on MFD_DA9063 || MFD_DA9062
5179f0ce 630 help
a27b5e0a
T
631 Support the ONKEY of Dialog DA9063 and DA9062 Power Management ICs
632 as an input device capable of reporting the power button status.
5179f0ce
ST
633
634 To compile this driver as a module, choose M here: the module
635 will be called da9063_onkey.
636
eb990b55
DB
637config INPUT_DM355EVM
638 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
639 depends on MFD_DM355EVM_MSP
66040727 640 select INPUT_SPARSEKMAP
eb990b55
DB
641 help
642 Supports the pushbuttons and IR remote used with
643 the DM355 EVM board.
644
645 To compile this driver as a module, choose M here: the
646 module will be called dm355evm_keys.
48329582
MH
647
648config INPUT_BFIN_ROTARY
649 tristate "Blackfin Rotary support"
650 depends on BF54x || BF52x
651 help
652 Say Y here if you want to use the Blackfin Rotary.
653
654 To compile this driver as a module, choose M here: the
655 module will be called bfin-rotary.
656
0c73b992
MB
657config INPUT_WM831X_ON
658 tristate "WM831X ON pin"
659 depends on MFD_WM831X
660 help
661 Support the ON pin of WM831X PMICs as an input device
662 reporting power button status.
663
664 To compile this driver as a module, choose M here: the module
665 will be called wm831x_on.
666
d0a82132
DR
667config INPUT_PCAP
668 tristate "Motorola EZX PCAP misc input events"
669 depends on EZX_PCAP
670 help
671 Say Y here if you want to use Power key and Headphone button
672 on Motorola EZX phones.
673
674 To compile this driver as a module, choose M here: the
675 module will be called pcap_keys.
676
e27c7292
MH
677config INPUT_ADXL34X
678 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
679 default n
680 help
681 Say Y here if you have a Accelerometer interface using the
682 ADXL345/6 controller, and your board-specific initialization
683 code includes that in its table of devices.
684
685 This driver can use either I2C or SPI communication to the
686 ADXL345/6 controller. Select the appropriate method for
687 your system.
688
689 If unsure, say N (but it's safe to say "Y").
690
691 To compile this driver as a module, choose M here: the
692 module will be called adxl34x.
693
694config INPUT_ADXL34X_I2C
695 tristate "support I2C bus connection"
696 depends on INPUT_ADXL34X && I2C
697 default y
698 help
699 Say Y here if you have ADXL345/6 hooked to an I2C bus.
700
701 To compile this driver as a module, choose M here: the
702 module will be called adxl34x-i2c.
703
704config INPUT_ADXL34X_SPI
705 tristate "support SPI bus connection"
706 depends on INPUT_ADXL34X && SPI
707 default y
708 help
709 Say Y here if you have ADXL345/6 hooked to a SPI bus.
710
711 To compile this driver as a module, choose M here: the
712 module will be called adxl34x-spi.
713
628329d5
DT
714config INPUT_IMS_PCU
715 tristate "IMS Passenger Control Unit driver"
716 depends on USB
717 depends on LEDS_CLASS
718 help
719 Say Y here if you have system with IMS Rave Passenger Control Unit.
720
721 To compile this driver as a module, choose M here: the module will be
722 called ims_pcu.
723
b029ffaf
H
724config INPUT_CMA3000
725 tristate "VTI CMA3000 Tri-axis accelerometer"
726 help
727 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
728 driver
729
730 This driver currently only supports I2C interface to the
731 controller. Also select the I2C method.
732
733 If unsure, say N
734
735 To compile this driver as a module, choose M here: the
736 module will be called cma3000_d0x.
737
738config INPUT_CMA3000_I2C
739 tristate "Support I2C bus connection"
740 depends on INPUT_CMA3000 && I2C
741 help
742 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
743 through I2C interface.
744
745 To compile this driver as a module, choose M here: the
746 module will be called cma3000_d0x_i2c.
747
49851ca0
DT
748config INPUT_XEN_KBDDEV_FRONTEND
749 tristate "Xen virtual keyboard and mouse support"
4bc25af7 750 depends on XEN
49851ca0
DT
751 default y
752 select XEN_XENBUS_FRONTEND
753 help
754 This driver implements the front-end of the Xen virtual
755 keyboard and mouse device driver. It communicates with a back-end
756 in another domain.
757
758 To compile this driver as a module, choose M here: the
759 module will be called xen-kbdfront.
760
9b5f953d 761config INPUT_SIRFSOC_ONKEY
af6e9463 762 tristate "CSR SiRFSoC power on/off/suspend key support"
9b5f953d
BD
763 depends on ARCH_SIRF && OF
764 default y
765 help
766 Say Y here if you want to support for the SiRFSoC power on/off/suspend key
767 in Linux, after you press the onkey, system will suspend.
768
769 If unsure, say N.
770
1ea4c161
AM
771config INPUT_IDEAPAD_SLIDEBAR
772 tristate "IdeaPad Laptop Slidebar"
773 depends on INPUT
774 depends on SERIO_I8042
775 help
776 Say Y here if you have an IdeaPad laptop with a slidebar.
777
778 To compile this driver as a module, choose M here: the
779 module will be called ideapad_slidebar.
780
61cd4822
LZ
781config INPUT_SOC_BUTTON_ARRAY
782 tristate "Windows-compatible SoC Button Array"
783 depends on KEYBOARD_GPIO
784 help
785 Say Y here if you have a SoC-based tablet that originally
786 runs Windows 8.
787
788 To compile this driver as a module, choose M here: the
789 module will be called soc_button_array.
790
7132fe4f
DM
791config INPUT_DRV260X_HAPTICS
792 tristate "TI DRV260X haptics support"
7d6548ab
GU
793 depends on INPUT && I2C
794 depends on GPIOLIB || COMPILE_TEST
7132fe4f
DM
795 select INPUT_FF_MEMLESS
796 select REGMAP_I2C
797 help
798 Say Y to enable support for the TI DRV260X haptics driver.
799
800 To compile this driver as a module, choose M here: the
801 module will be called drv260x-haptics.
802
4d10da13
DM
803config INPUT_DRV2665_HAPTICS
804 tristate "TI DRV2665 haptics support"
805 depends on INPUT && I2C
806 select INPUT_FF_MEMLESS
807 select REGMAP_I2C
808 help
809 Say Y to enable support for the TI DRV2665 haptics driver.
810
811 To compile this driver as a module, choose M here: the
812 module will be called drv2665-haptics.
813
1c246225
DM
814config INPUT_DRV2667_HAPTICS
815 tristate "TI DRV2667 haptics support"
816 depends on INPUT && I2C
817 select INPUT_FF_MEMLESS
818 select REGMAP_I2C
819 help
820 Say Y to enable support for the TI DRV2667 haptics driver.
821
822 To compile this driver as a module, choose M here: the
c857ea9e 823 module will be called drv2667-haptics.
1c246225 824
fcd6eb50
JRO
825config INPUT_HISI_POWERKEY
826 tristate "Hisilicon PMIC ONKEY support"
827 depends on ARCH_HISI || COMPILE_TEST
828 help
829 Say Y to enable support for PMIC ONKEY.
830
831 To compile this driver as a module, choose M here: the
832 module will be called hisi_powerkey.
833
1da177e4 834endif
This page took 0.630631 seconds and 5 git commands to generate.