1
2
3
4
5menuconfig INPUT_MISC
6 bool "Miscellaneous devices"
7 help
8 Say Y here, and a list of miscellaneous input drivers will be displayed.
9 Everything that didn't fit into the other categories is here. This option
10 doesn't affect the kernel.
11
12 If unsure, say Y.
13
14if INPUT_MISC
15
16config INPUT_88PM860X_ONKEY
17 tristate "88PM860x ONKEY support"
18 depends on MFD_88PM860X
19 help
20 Support the ONKEY of Marvell 88PM860x PMICs as an input device
21 reporting power button status.
22
23 To compile this driver as a module, choose M here: the module
24 will be called 88pm860x_onkey.
25
26config INPUT_88PM80X_ONKEY
27 tristate "88PM80x ONKEY support"
28 depends on MFD_88PM800
29 help
30 Support the ONKEY of Marvell 88PM80x PMICs as an input device
31 reporting power button status.
32
33 To compile this driver as a module, choose M here: the module
34 will be called 88pm80x_onkey.
35
36config INPUT_AB8500_PONKEY
37 tristate "AB8500 Pon (PowerOn) Key"
38 depends on AB8500_CORE
39 help
40 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
41 Mix-Sig PMIC.
42
43 To compile this driver as a module, choose M here: the module
44 will be called ab8500-ponkey.
45
46config INPUT_AD714X
47 tristate "Analog Devices AD714x Capacitance Touch Sensor"
48 help
49 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
50
51 You should select a bus connection too.
52
53 To compile this driver as a module, choose M here: the
54 module will be called ad714x.
55
56config INPUT_AD714X_I2C
57 tristate "support I2C bus connection"
58 depends on INPUT_AD714X && I2C
59 default y
60 help
61 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
62
63 To compile this driver as a module, choose M here: the
64 module will be called ad714x-i2c.
65
66config INPUT_AD714X_SPI
67 tristate "support SPI bus connection"
68 depends on INPUT_AD714X && SPI
69 default y
70 help
71 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
72
73 To compile this driver as a module, choose M here: the
74 module will be called ad714x-spi.
75
76config INPUT_ARIEL_PWRBUTTON
77 tristate "Dell Wyse 3020 Power Button Driver"
78 depends on SPI
79 depends on MACH_MMP3_DT || COMPILE_TEST
80 help
81 Say Y to enable support for reporting power button status on
82 on Dell Wyse 3020 ("Ariel") thin client.
83
84 To compile this driver as a module, choose M here: the module
85 will be called ariel-pwrbutton.
86
87config INPUT_ARIZONA_HAPTICS
88 tristate "Arizona haptics support"
89 depends on MFD_ARIZONA && SND_SOC
90 select INPUT_FF_MEMLESS
91 help
92 Say Y to enable support for the haptics module in Arizona CODECs.
93
94 To compile this driver as a module, choose M here: the
95 module will be called arizona-haptics.
96
97config INPUT_ATC260X_ONKEY
98 tristate "Actions Semi ATC260x PMIC ONKEY"
99 depends on MFD_ATC260X
100 help
101 Support the ONKEY of ATC260x PMICs as an input device reporting
102 power button status. ONKEY can be used to wakeup from low power
103 modes and force a reset on long press.
104
105 To compile this driver as a module, choose M here: the
106 module will be called atc260x-onkey.
107
108config INPUT_ATMEL_CAPTOUCH
109 tristate "Atmel Capacitive Touch Button Driver"
110 depends on OF || COMPILE_TEST
111 depends on I2C
112 help
113 Say Y here if an Atmel Capacitive Touch Button device which
114 implements "captouch" protocol is connected to I2C bus. Typically
115 this device consists of Atmel Touch sensor controlled by AtMegaXX
116 MCU running firmware based on Qtouch library.
117 One should find "atmel,captouch" node in the board specific DTS.
118
119 To compile this driver as a module, choose M here: the
120 module will be called atmel_captouch.
121
122config INPUT_BMA150
123 tristate "BMA150/SMB380 acceleration sensor support"
124 depends on I2C
125 help
126 Say Y here if you have Bosch Sensortec's BMA150 or SMB380
127 acceleration sensor hooked to an I2C bus.
128
129 To compile this driver as a module, choose M here: the
130 module will be called bma150.
131
132config INPUT_E3X0_BUTTON
133 tristate "NI Ettus Research USRP E3xx Button support."
134 default n
135 help
136 Say Y here to enable support for the NI Ettus Research
137 USRP E3xx Button.
138
139 To compile this driver as a module, choose M here: the
140 module will be called e3x0_button.
141
142config INPUT_PCSPKR
143 tristate "PC Speaker support"
144 depends on PCSPKR_PLATFORM
145 help
146 Say Y here if you want the standard PC Speaker to be used for
147 bells and whistles.
148
149 If unsure, say Y.
150
151 To compile this driver as a module, choose M here: the
152 module will be called pcspkr.
153
154config INPUT_PM8941_PWRKEY
155 tristate "Qualcomm PM8941 power key support"
156 depends on MFD_SPMI_PMIC
157 help
158 Say Y here if you want support for the power key usually found
159 on boards using a Qualcomm PM8941 compatible PMIC.
160
161 If unsure, say Y.
162
163 To compile this driver as a module, choose M here: the module
164 will be called pm8941-pwrkey.
165
166config INPUT_PM8XXX_VIBRATOR
167 tristate "Qualcomm PM8XXX vibrator support"
168 depends on MFD_PM8XXX || MFD_SPMI_PMIC
169 select INPUT_FF_MEMLESS
170 help
171 This option enables device driver support for the vibrator
172 on Qualcomm PM8xxx chip. This driver supports ff-memless interface
173 from input framework.
174
175 To compile this driver as module, choose M here: the
176 module will be called pm8xxx-vibrator.
177
178config INPUT_PMIC8XXX_PWRKEY
179 tristate "PMIC8XXX power key support"
180 depends on MFD_PM8XXX
181 help
182 Say Y here if you want support for the PMIC8XXX power key.
183
184 If unsure, say N.
185
186 To compile this driver as a module, choose M here: the
187 module will be called pmic8xxx-pwrkey.
188
189config INPUT_SPARCSPKR
190 tristate "SPARC Speaker support"
191 depends on PCI && SPARC64
192 help
193 Say Y here if you want the standard Speaker on Sparc PCI systems
194 to be used for bells and whistles.
195
196 If unsure, say Y.
197
198 To compile this driver as a module, choose M here: the
199 module will be called sparcspkr.
200
201config INPUT_M68K_BEEP
202 tristate "M68k Beeper support"
203 depends on M68K
204
205config INPUT_MAX77650_ONKEY
206 tristate "Maxim MAX77650 ONKEY support"
207 depends on MFD_MAX77650
208 help
209 Support the ONKEY of the MAX77650 PMIC as an input device.
210
211 To compile this driver as a module, choose M here: the module
212 will be called max77650-onkey.
213
214config INPUT_MAX77693_HAPTIC
215 tristate "MAXIM MAX77693/MAX77843 haptic controller support"
216 depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
217 select INPUT_FF_MEMLESS
218 help
219 This option enables support for the haptic controller on
220 MAXIM MAX77693 and MAX77843 chips.
221
222 To compile this driver as module, choose M here: the
223 module will be called max77693-haptic.
224
225config INPUT_MAX8925_ONKEY
226 tristate "MAX8925 ONKEY support"
227 depends on MFD_MAX8925
228 help
229 Support the ONKEY of MAX8925 PMICs as an input device
230 reporting power button status.
231
232 To compile this driver as a module, choose M here: the module
233 will be called max8925_onkey.
234
235config INPUT_MAX8997_HAPTIC
236 tristate "MAXIM MAX8997 haptic controller support"
237 depends on PWM && MFD_MAX8997
238 select INPUT_FF_MEMLESS
239 help
240 This option enables device driver support for the haptic controller
241 on MAXIM MAX8997 chip. This driver supports ff-memless interface
242 from input framework.
243
244 To compile this driver as module, choose M here: the
245 module will be called max8997-haptic.
246
247config INPUT_MC13783_PWRBUTTON
248 tristate "MC13783 ON buttons"
249 depends on MFD_MC13XXX
250 help
251 Support the ON buttons of MC13783 PMIC as an input device
252 reporting power button status.
253
254 To compile this driver as a module, choose M here: the module
255 will be called mc13783-pwrbutton.
256
257config INPUT_MMA8450
258 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
259 depends on I2C
260 help
261 Say Y here if you want to support Freescale's MMA8450 Accelerometer
262 through I2C interface.
263
264 To compile this driver as a module, choose M here: the
265 module will be called mma8450.
266
267config INPUT_APANEL
268 tristate "Fujitsu Lifebook Application Panel buttons"
269 depends on X86 && I2C && LEDS_CLASS
270 select CHECK_SIGNATURE
271 help
272 Say Y here for support of the Application Panel buttons, used on
273 Fujitsu Lifebook. These are attached to the mainboard through
274 an SMBus interface managed by the I2C Intel ICH (i801) driver,
275 which you should also build for this kernel.
276
277 To compile this driver as a module, choose M here: the module will
278 be called apanel.
279
280config INPUT_GPIO_BEEPER
281 tristate "Generic GPIO Beeper support"
282 depends on GPIOLIB || COMPILE_TEST
283 help
284 Say Y here if you have a beeper connected to a GPIO pin.
285
286 To compile this driver as a module, choose M here: the
287 module will be called gpio-beeper.
288
289config INPUT_GPIO_DECODER
290 tristate "Polled GPIO Decoder Input driver"
291 depends on GPIOLIB || COMPILE_TEST
292 help
293 Say Y here if you want driver to read status of multiple GPIO
294 lines and report the encoded value as an absolute integer to
295 input subsystem.
296
297 To compile this driver as a module, choose M here: the module
298 will be called gpio_decoder.
299
300config INPUT_GPIO_VIBRA
301 tristate "GPIO vibrator support"
302 depends on GPIOLIB || COMPILE_TEST
303 select INPUT_FF_MEMLESS
304 help
305 Say Y here to get support for GPIO based vibrator devices.
306
307 If unsure, say N.
308
309 To compile this driver as a module, choose M here: the module will be
310 called gpio-vibra.
311
312config INPUT_COBALT_BTNS
313 tristate "Cobalt button interface"
314 depends on MIPS_COBALT
315 help
316 Say Y here if you want to support MIPS Cobalt button interface.
317
318 To compile this driver as a module, choose M here: the
319 module will be called cobalt_btns.
320
321config INPUT_CPCAP_PWRBUTTON
322 tristate "CPCAP OnKey"
323 depends on MFD_CPCAP
324 help
325 Say Y here if you want to enable power key reporting via the
326 Motorola CPCAP chip.
327
328 To compile this driver as a module, choose M here. The module will
329 be called cpcap-pwrbutton.
330
331config INPUT_WISTRON_BTNS
332 tristate "x86 Wistron laptop button interface"
333 depends on X86_32
334 select INPUT_SPARSEKMAP
335 select NEW_LEDS
336 select LEDS_CLASS
337 select CHECK_SIGNATURE
338 help
339 Say Y here for support of Wistron laptop button interfaces, used on
340 laptops of various brands, including Acer and Fujitsu-Siemens. If
341 available, mail and wifi LEDs will be controllable via /sys/class/leds.
342
343 To compile this driver as a module, choose M here: the module will
344 be called wistron_btns.
345
346config INPUT_ATLAS_BTNS
347 tristate "x86 Atlas button interface"
348 depends on X86 && ACPI
349 help
350 Say Y here for support of Atlas wallmount touchscreen buttons.
351 The events will show up as scancodes F1 through F9 via evdev.
352
353 To compile this driver as a module, choose M here: the module will
354 be called atlas_btns.
355
356config INPUT_ATI_REMOTE2
357 tristate "ATI / Philips USB RF remote control"
358 depends on USB_ARCH_HAS_HCD
359 select USB
360 help
361 Say Y here if you want to use an ATI or Philips USB RF remote control.
362 These are RF remotes with USB receivers.
363 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
364 and is also available as a separate product.
365 This driver provides mouse pointer, left and right mouse buttons,
366 and maps all the other remote buttons to keypress events.
367
368 To compile this driver as a module, choose M here: the module will be
369 called ati_remote2.
370
371config INPUT_KEYSPAN_REMOTE
372 tristate "Keyspan DMR USB remote control"
373 depends on USB_ARCH_HAS_HCD
374 select USB
375 help
376 Say Y here if you want to use a Keyspan DMR USB remote control.
377 Currently only the UIA-11 type of receiver has been tested. The tag
378 on the receiver that connects to the USB port should have a P/N that
379 will tell you what type of DMR you have. The UIA-10 type is not
380 supported at this time. This driver maps all buttons to keypress
381 events.
382
383 To compile this driver as a module, choose M here: the module will
384 be called keyspan_remote.
385
386config INPUT_KXTJ9
387 tristate "Kionix KXTJ9 tri-axis digital accelerometer"
388 depends on I2C
389 help
390 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
391 accelerometer.
392
393 To compile this driver as a module, choose M here: the module will
394 be called kxtj9.
395
396config INPUT_POWERMATE
397 tristate "Griffin PowerMate and Contour Jog support"
398 depends on USB_ARCH_HAS_HCD
399 select USB
400 help
401 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
402 These are aluminum dials which can measure clockwise and anticlockwise
403 rotation. The dial also acts as a pushbutton. The base contains an LED
404 which can be instructed to pulse or to switch to a particular intensity.
405
406 You can download userspace tools from
407 <http://sowerbutts.com/powermate/>.
408
409 To compile this driver as a module, choose M here: the
410 module will be called powermate.
411
412config INPUT_YEALINK
413 tristate "Yealink usb-p1k voip phone"
414 depends on USB_ARCH_HAS_HCD
415 select USB
416 help
417 Say Y here if you want to enable keyboard and LCD functions of the
418 Yealink usb-p1k usb phones. The audio part is enabled by the generic
419 usb sound driver, so you might want to enable that as well.
420
421 For information about how to use these additional functions, see
422 <file:Documentation/input/devices/yealink.rst>.
423
424 To compile this driver as a module, choose M here: the module will be
425 called yealink.
426
427config INPUT_CM109
428 tristate "C-Media CM109 USB I/O Controller"
429 depends on USB_ARCH_HAS_HCD
430 select USB
431 help
432 Say Y here if you want to enable keyboard and buzzer functions of the
433 C-Media CM109 usb phones. The audio part is enabled by the generic
434 usb sound driver, so you might want to enable that as well.
435
436 To compile this driver as a module, choose M here: the module will be
437 called cm109.
438
439config INPUT_REGULATOR_HAPTIC
440 tristate "Regulator haptics support"
441 depends on REGULATOR
442 select INPUT_FF_MEMLESS
443 help
444 This option enables device driver support for the haptic controlled
445 by a regulator. This driver supports ff-memless interface
446 from input framework.
447
448 To compile this driver as a module, choose M here: the
449 module will be called regulator-haptic.
450
451config INPUT_RETU_PWRBUTTON
452 tristate "Retu Power button Driver"
453 depends on MFD_RETU
454 help
455 Say Y here if you want to enable power key reporting via the
456 Retu chips found in Nokia Internet Tablets (770, N800, N810).
457
458 To compile this driver as a module, choose M here. The module will
459 be called retu-pwrbutton.
460
461config INPUT_TPS65218_PWRBUTTON
462 tristate "TPS65218 Power button driver"
463 depends on (MFD_TPS65217 || MFD_TPS65218)
464 help
465 Say Y here if you want to enable power button reporting for
466 TPS65217 and TPS65218 Power Management IC devices.
467
468 To compile this driver as a module, choose M here. The module will
469 be called tps65218-pwrbutton.
470
471config INPUT_AXP20X_PEK
472 tristate "X-Powers AXP20X power button driver"
473 depends on MFD_AXP20X
474 help
475 Say Y here if you want to enable power key reporting via the
476 AXP20X PMIC.
477
478 To compile this driver as a module, choose M here. The module will
479 be called axp20x-pek.
480
481
482config INPUT_TWL4030_PWRBUTTON
483 tristate "TWL4030 Power button Driver"
484 depends on TWL4030_CORE
485 help
486 Say Y here if you want to enable power key reporting via the
487 TWL4030 family of chips.
488
489 To compile this driver as a module, choose M here. The module will
490 be called twl4030_pwrbutton.
491
492config INPUT_TWL4030_VIBRA
493 tristate "Support for TWL4030 Vibrator"
494 depends on TWL4030_CORE
495 select MFD_TWL4030_AUDIO
496 select INPUT_FF_MEMLESS
497 help
498 This option enables support for TWL4030 Vibrator Driver.
499
500 To compile this driver as a module, choose M here. The module will
501 be called twl4030_vibra.
502
503config INPUT_TWL6040_VIBRA
504 tristate "Support for TWL6040 Vibrator"
505 depends on TWL6040_CORE
506 select INPUT_FF_MEMLESS
507 help
508 This option enables support for TWL6040 Vibrator Driver.
509
510 To compile this driver as a module, choose M here. The module will
511 be called twl6040_vibra.
512
513config INPUT_UINPUT
514 tristate "User level driver support"
515 help
516 Say Y here if you want to support user level drivers for input
517 subsystem accessible under char device 10:223 - /dev/input/uinput.
518
519 To compile this driver as a module, choose M here: the
520 module will be called uinput.
521
522config INPUT_SGI_BTNS
523 tristate "SGI Indy/O2 volume button interface"
524 depends on SGI_IP22 || SGI_IP32
525 help
526 Say Y here if you want to support SGI Indy/O2 volume button interface.
527
528 To compile this driver as a module, choose M here: the
529 module will be called sgi_btns.
530
531config HP_SDC_RTC
532 tristate "HP SDC Real Time Clock"
533 depends on (GSC || HP300) && SERIO
534 select HP_SDC
535 help
536 Say Y here if you want to support the built-in real time clock
537 of the HP SDC controller.
538
539config INPUT_PALMAS_PWRBUTTON
540 tristate "Palmas Power button Driver"
541 depends on MFD_PALMAS
542 help
543 Say Y here if you want to enable power key reporting via the
544 Palmas family of PMICs.
545
546 To compile this driver as a module, choose M here. The module will
547 be called palmas_pwrbutton.
548
549config INPUT_PCF50633_PMU
550 tristate "PCF50633 PMU events"
551 depends on MFD_PCF50633
552 help
553 Say Y to include support for delivering PMU events via input
554 layer on NXP PCF50633.
555
556config INPUT_PCF8574
557 tristate "PCF8574 Keypad input device"
558 depends on I2C
559 help
560 Say Y here if you want to support a keypad connected via I2C
561 with a PCF8574.
562
563 To compile this driver as a module, choose M here: the
564 module will be called pcf8574_keypad.
565
566config INPUT_PWM_BEEPER
567 tristate "PWM beeper support"
568 depends on PWM
569 help
570 Say Y here to get support for PWM based beeper devices.
571
572 If unsure, say N.
573
574 To compile this driver as a module, choose M here: the module will be
575 called pwm-beeper.
576
577config INPUT_PWM_VIBRA
578 tristate "PWM vibrator support"
579 depends on PWM
580 select INPUT_FF_MEMLESS
581 help
582 Say Y here to get support for PWM based vibrator devices.
583
584 If unsure, say N.
585
586 To compile this driver as a module, choose M here: the module will be
587 called pwm-vibra.
588
589config INPUT_RK805_PWRKEY
590 tristate "Rockchip RK805 PMIC power key support"
591 depends on MFD_RK808
592 help
593 Select this option to enable power key driver for RK805.
594
595 If unsure, say N.
596
597 To compile this driver as a module, choose M here: the module will be
598 called rk805_pwrkey.
599
600config INPUT_GPIO_ROTARY_ENCODER
601 tristate "Rotary encoders connected to GPIO pins"
602 depends on GPIOLIB || COMPILE_TEST
603 help
604 Say Y here to add support for rotary encoders connected to GPIO lines.
605 Check file:Documentation/input/devices/rotary-encoder.rst for more
606 information.
607
608 To compile this driver as a module, choose M here: the
609 module will be called rotary_encoder.
610
611config INPUT_RB532_BUTTON
612 tristate "Mikrotik Routerboard 532 button interface"
613 depends on MIKROTIK_RB532
614 depends on GPIOLIB
615 help
616 Say Y here if you want support for the S1 button built into
617 Mikrotik's Routerboard 532.
618
619 To compile this driver as a module, choose M here: the
620 module will be called rb532_button.
621
622config INPUT_DA7280_HAPTICS
623 tristate "Dialog Semiconductor DA7280 haptics support"
624 depends on INPUT && I2C
625 select REGMAP_I2C
626 help
627 Say Y to enable support for the Dialog DA7280 haptics driver.
628 The haptics can be controlled by PWM or GPIO
629 with I2C communication.
630
631 To compile this driver as a module, choose M here: the
632 module will be called da7280.
633
634config INPUT_DA9052_ONKEY
635 tristate "Dialog DA9052/DA9053 Onkey"
636 depends on PMIC_DA9052
637 help
638 Support the ONKEY of Dialog DA9052 PMICs as an input device
639 reporting power button status.
640
641 To compile this driver as a module, choose M here: the
642 module will be called da9052_onkey.
643
644config INPUT_DA9055_ONKEY
645 tristate "Dialog Semiconductor DA9055 ONKEY"
646 depends on MFD_DA9055
647 help
648 Support the ONKEY of DA9055 PMICs as an input device
649 reporting power button status.
650
651 To compile this driver as a module, choose M here: the module
652 will be called da9055_onkey.
653
654config INPUT_DA9063_ONKEY
655 tristate "Dialog DA9063/62/61 OnKey"
656 depends on MFD_DA9063 || MFD_DA9062
657 help
658 Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
659 Management ICs as an input device capable of reporting the
660 power button status.
661
662 To compile this driver as a module, choose M here: the module
663 will be called da9063_onkey.
664
665config INPUT_DM355EVM
666 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
667 depends on MFD_DM355EVM_MSP
668 select INPUT_SPARSEKMAP
669 help
670 Supports the pushbuttons and IR remote used with
671 the DM355 EVM board.
672
673 To compile this driver as a module, choose M here: the
674 module will be called dm355evm_keys.
675
676config INPUT_WM831X_ON
677 tristate "WM831X ON pin"
678 depends on MFD_WM831X
679 help
680 Support the ON pin of WM831X PMICs as an input device
681 reporting power button status.
682
683 To compile this driver as a module, choose M here: the module
684 will be called wm831x_on.
685
686config INPUT_PCAP
687 tristate "Motorola EZX PCAP misc input events"
688 depends on EZX_PCAP
689 help
690 Say Y here if you want to use Power key and Headphone button
691 on Motorola EZX phones.
692
693 To compile this driver as a module, choose M here: the
694 module will be called pcap_keys.
695
696config INPUT_ADXL34X
697 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
698 default n
699 help
700 Say Y here if you have a Accelerometer interface using the
701 ADXL345/6 controller, and your board-specific initialization
702 code includes that in its table of devices.
703
704 This driver can use either I2C or SPI communication to the
705 ADXL345/6 controller. Select the appropriate method for
706 your system.
707
708 If unsure, say N (but it's safe to say "Y").
709
710 To compile this driver as a module, choose M here: the
711 module will be called adxl34x.
712
713config INPUT_ADXL34X_I2C
714 tristate "support I2C bus connection"
715 depends on INPUT_ADXL34X && I2C
716 default y
717 help
718 Say Y here if you have ADXL345/6 hooked to an I2C bus.
719
720 To compile this driver as a module, choose M here: the
721 module will be called adxl34x-i2c.
722
723config INPUT_ADXL34X_SPI
724 tristate "support SPI bus connection"
725 depends on INPUT_ADXL34X && SPI
726 default y
727 help
728 Say Y here if you have ADXL345/6 hooked to a SPI bus.
729
730 To compile this driver as a module, choose M here: the
731 module will be called adxl34x-spi.
732
733config INPUT_IMS_PCU
734 tristate "IMS Passenger Control Unit driver"
735 depends on USB
736 depends on LEDS_CLASS
737 help
738 Say Y here if you have system with IMS Rave Passenger Control Unit.
739
740 To compile this driver as a module, choose M here: the module will be
741 called ims_pcu.
742
743config INPUT_IQS269A
744 tristate "Azoteq IQS269A capacitive touch controller"
745 depends on I2C
746 select REGMAP_I2C
747 help
748 Say Y to enable support for the Azoteq IQS269A capacitive
749 touch controller.
750
751 To compile this driver as a module, choose M here: the
752 module will be called iqs269a.
753
754config INPUT_IQS626A
755 tristate "Azoteq IQS626A capacitive touch controller"
756 depends on I2C
757 select REGMAP_I2C
758 help
759 Say Y to enable support for the Azoteq IQS626A capacitive
760 touch controller.
761
762 To compile this driver as a module, choose M here: the
763 module will be called iqs626a.
764
765config INPUT_CMA3000
766 tristate "VTI CMA3000 Tri-axis accelerometer"
767 help
768 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
769 driver
770
771 This driver currently only supports I2C interface to the
772 controller. Also select the I2C method.
773
774 If unsure, say N
775
776 To compile this driver as a module, choose M here: the
777 module will be called cma3000_d0x.
778
779config INPUT_CMA3000_I2C
780 tristate "Support I2C bus connection"
781 depends on INPUT_CMA3000 && I2C
782 help
783 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
784 through I2C interface.
785
786 To compile this driver as a module, choose M here: the
787 module will be called cma3000_d0x_i2c.
788
789config INPUT_XEN_KBDDEV_FRONTEND
790 tristate "Xen virtual keyboard and mouse support"
791 depends on XEN
792 default y
793 select XEN_XENBUS_FRONTEND
794 help
795 This driver implements the front-end of the Xen virtual
796 keyboard and mouse device driver. It communicates with a back-end
797 in another domain.
798
799 To compile this driver as a module, choose M here: the
800 module will be called xen-kbdfront.
801
802config INPUT_IDEAPAD_SLIDEBAR
803 tristate "IdeaPad Laptop Slidebar"
804 depends on INPUT
805 depends on SERIO_I8042
806 help
807 Say Y here if you have an IdeaPad laptop with a slidebar.
808
809 To compile this driver as a module, choose M here: the
810 module will be called ideapad_slidebar.
811
812config INPUT_SOC_BUTTON_ARRAY
813 tristate "Windows-compatible SoC Button Array"
814 depends on KEYBOARD_GPIO && ACPI
815 help
816 Say Y here if you have a SoC-based tablet that originally runs
817 Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later.
818
819 To compile this driver as a module, choose M here: the
820 module will be called soc_button_array.
821
822config INPUT_DRV260X_HAPTICS
823 tristate "TI DRV260X haptics support"
824 depends on INPUT && I2C
825 depends on GPIOLIB || COMPILE_TEST
826 select INPUT_FF_MEMLESS
827 select REGMAP_I2C
828 help
829 Say Y to enable support for the TI DRV260X haptics driver.
830
831 To compile this driver as a module, choose M here: the
832 module will be called drv260x-haptics.
833
834config INPUT_DRV2665_HAPTICS
835 tristate "TI DRV2665 haptics support"
836 depends on INPUT && I2C
837 select INPUT_FF_MEMLESS
838 select REGMAP_I2C
839 help
840 Say Y to enable support for the TI DRV2665 haptics driver.
841
842 To compile this driver as a module, choose M here: the
843 module will be called drv2665-haptics.
844
845config INPUT_DRV2667_HAPTICS
846 tristate "TI DRV2667 haptics support"
847 depends on INPUT && I2C
848 select INPUT_FF_MEMLESS
849 select REGMAP_I2C
850 help
851 Say Y to enable support for the TI DRV2667 haptics driver.
852
853 To compile this driver as a module, choose M here: the
854 module will be called drv2667-haptics.
855
856config INPUT_HISI_POWERKEY
857 tristate "Hisilicon PMIC ONKEY support"
858 depends on ARCH_HISI || COMPILE_TEST
859 help
860 Say Y to enable support for PMIC ONKEY.
861
862 To compile this driver as a module, choose M here: the
863 module will be called hisi_powerkey.
864
865config INPUT_RAVE_SP_PWRBUTTON
866 tristate "RAVE SP Power button Driver"
867 depends on RAVE_SP_CORE
868 help
869 Say Y here if you want to enable power key reporting from RAVE SP
870
871 To compile this driver as a module, choose M here: the
872 module will be called rave-sp-pwrbutton.
873
874config INPUT_SC27XX_VIBRA
875 tristate "Spreadtrum sc27xx vibrator support"
876 depends on MFD_SC27XX_PMIC || COMPILE_TEST
877 select INPUT_FF_MEMLESS
878 help
879 This option enables support for Spreadtrum sc27xx vibrator driver.
880
881 To compile this driver as a module, choose M here. The module will
882 be called sc27xx_vibra.
883
884config INPUT_STPMIC1_ONKEY
885 tristate "STPMIC1 PMIC Onkey support"
886 depends on MFD_STPMIC1
887 help
888 Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
889 can be used to wakeup from low power modes and force a shut-down on
890 long press.
891
892 To compile this driver as a module, choose M here: the
893 module will be called stpmic1_onkey.
894
895endif
896
