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