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