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_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 && !UML
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_TPS65219_PWRBUTTON
472	tristate "TPS65219 Power button driver"
473	depends on MFD_TPS65219
474	help
475	  Say Y here if you want to enable power button reporting for
476	  TPS65219 Power Management IC devices.
477
478	  To compile this driver as a module, choose M here. The module will
479	  be called tps65219-pwrbutton.
480
481config INPUT_AXP20X_PEK
482	tristate "X-Powers AXP20X power button driver"
483	depends on MFD_AXP20X
484	help
485	  Say Y here if you want to enable power key reporting via the
486	  AXP20X PMIC.
487
488	  To compile this driver as a module, choose M here. The module will
489	  be called axp20x-pek.
490
491
492config INPUT_TWL4030_PWRBUTTON
493	tristate "TWL4030 Power button Driver"
494	depends on TWL4030_CORE
495	help
496	  Say Y here if you want to enable power key reporting via the
497	  TWL4030 family of chips.
498
499	  To compile this driver as a module, choose M here. The module will
500	  be called twl4030_pwrbutton.
501
502config INPUT_TWL4030_VIBRA
503	tristate "Support for TWL4030 Vibrator"
504	depends on TWL4030_CORE
505	select MFD_TWL4030_AUDIO
506	select INPUT_FF_MEMLESS
507	help
508	  This option enables support for TWL4030 Vibrator Driver.
509
510	  To compile this driver as a module, choose M here. The module will
511	  be called twl4030_vibra.
512
513config INPUT_TWL6040_VIBRA
514	tristate "Support for TWL6040 Vibrator"
515	depends on TWL6040_CORE
516	select INPUT_FF_MEMLESS
517	help
518	  This option enables support for TWL6040 Vibrator Driver.
519
520	  To compile this driver as a module, choose M here. The module will
521	  be called twl6040_vibra.
522
523config INPUT_UINPUT
524	tristate "User level driver support"
525	help
526	  Say Y here if you want to support user level drivers for input
527	  subsystem accessible under char device 10:223 - /dev/input/uinput.
528
529	  To compile this driver as a module, choose M here: the
530	  module will be called uinput.
531
532config INPUT_SGI_BTNS
533	tristate "SGI Indy/O2 volume button interface"
534	depends on SGI_IP22 || SGI_IP32
535	help
536	  Say Y here if you want to support SGI Indy/O2 volume button interface.
537
538	  To compile this driver as a module, choose M here: the
539	  module will be called sgi_btns.
540
541config HP_SDC_RTC
542	tristate "HP SDC Real Time Clock"
543	depends on (GSC || HP300) && SERIO
544	select HP_SDC
545	help
546	  Say Y here if you want to support the built-in real time clock
547	  of the HP SDC controller.
548
549config INPUT_PALMAS_PWRBUTTON
550	tristate "Palmas Power button Driver"
551	depends on MFD_PALMAS
552	help
553	  Say Y here if you want to enable power key reporting via the
554	  Palmas family of PMICs.
555
556	  To compile this driver as a module, choose M here. The module will
557	  be called palmas_pwrbutton.
558
559config INPUT_PCF50633_PMU
560	tristate "PCF50633 PMU events"
561	depends on MFD_PCF50633
562	help
563	 Say Y to include support for delivering  PMU events via  input
564	 layer on NXP PCF50633.
565
566config INPUT_PCF8574
567	tristate "PCF8574 Keypad input device"
568	depends on I2C
569	help
570	  Say Y here if you want to support a keypad connected via I2C
571	  with a PCF8574.
572
573	  To compile this driver as a module, choose M here: the
574	  module will be called pcf8574_keypad.
575
576config INPUT_PWM_BEEPER
577	tristate "PWM beeper support"
578	depends on PWM
579	help
580	  Say Y here to get support for PWM based beeper devices.
581
582	  If unsure, say N.
583
584	  To compile this driver as a module, choose M here: the module will be
585	  called pwm-beeper.
586
587config INPUT_PWM_VIBRA
588	tristate "PWM vibrator support"
589	depends on PWM
590	select INPUT_FF_MEMLESS
591	help
592	  Say Y here to get support for PWM based vibrator devices.
593
594	  If unsure, say N.
595
596	  To compile this driver as a module, choose M here: the module will be
597	  called pwm-vibra.
598
599config INPUT_RK805_PWRKEY
600	tristate "Rockchip RK805 PMIC power key support"
601	depends on MFD_RK808
602	help
603	  Select this option to enable power key driver for RK805.
604
605	  If unsure, say N.
606
607	  To compile this driver as a module, choose M here: the module will be
608	  called rk805_pwrkey.
609
610config INPUT_GPIO_ROTARY_ENCODER
611	tristate "Rotary encoders connected to GPIO pins"
612	depends on GPIOLIB || COMPILE_TEST
613	help
614	  Say Y here to add support for rotary encoders connected to GPIO lines.
615	  Check file:Documentation/input/devices/rotary-encoder.rst for more
616	  information.
617
618	  To compile this driver as a module, choose M here: the
619	  module will be called rotary_encoder.
620
621config INPUT_RB532_BUTTON
622	tristate "Mikrotik Routerboard 532 button interface"
623	depends on MIKROTIK_RB532
624	depends on GPIOLIB
625	help
626	  Say Y here if you want support for the S1 button built into
627	  Mikrotik's Routerboard 532.
628
629	  To compile this driver as a module, choose M here: the
630	  module will be called rb532_button.
631
632config INPUT_DA7280_HAPTICS
633	tristate "Dialog Semiconductor DA7280 haptics support"
634	depends on INPUT && I2C
635	select REGMAP_I2C
636	help
637	  Say Y to enable support for the Dialog DA7280 haptics driver.
638	  The haptics can be controlled by PWM or GPIO
639	  with I2C communication.
640
641	  To compile this driver as a module, choose M here: the
642	  module will be called da7280.
643
644config INPUT_DA9052_ONKEY
645	tristate "Dialog DA9052/DA9053 Onkey"
646	depends on PMIC_DA9052
647	help
648	  Support the ONKEY of Dialog DA9052 PMICs as an input device
649	  reporting power button status.
650
651	  To compile this driver as a module, choose M here: the
652	  module will be called da9052_onkey.
653
654config INPUT_DA9055_ONKEY
655	tristate "Dialog Semiconductor DA9055 ONKEY"
656	depends on MFD_DA9055
657	help
658	  Support the ONKEY of DA9055 PMICs as an input device
659	  reporting power button status.
660
661	  To compile this driver as a module, choose M here: the module
662	  will be called da9055_onkey.
663
664config INPUT_DA9063_ONKEY
665	tristate "Dialog DA9063/62/61 OnKey"
666	depends on MFD_DA9063 || MFD_DA9062
667	help
668	  Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
669	  Management ICs as an input device capable of reporting the
670	  power button status.
671
672	  To compile this driver as a module, choose M here: the module
673	  will be called da9063_onkey.
674
675config INPUT_WM831X_ON
676	tristate "WM831X ON pin"
677	depends on MFD_WM831X
678	help
679	  Support the ON pin of WM831X 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 wm831x_on.
684
685config INPUT_PCAP
686	tristate "Motorola EZX PCAP misc input events"
687	depends on EZX_PCAP
688	help
689	  Say Y here if you want to use Power key and Headphone button
690	  on Motorola EZX phones.
691
692	  To compile this driver as a module, choose M here: the
693	  module will be called pcap_keys.
694
695config INPUT_ADXL34X
696	tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
697	default n
698	help
699	  Say Y here if you have a Accelerometer interface using the
700	  ADXL345/6 controller, and your board-specific initialization
701	  code includes that in its table of devices.
702
703	  This driver can use either I2C or SPI communication to the
704	  ADXL345/6 controller.  Select the appropriate method for
705	  your system.
706
707	  If unsure, say N (but it's safe to say "Y").
708
709	  To compile this driver as a module, choose M here: the
710	  module will be called adxl34x.
711
712config INPUT_ADXL34X_I2C
713	tristate "support I2C bus connection"
714	depends on INPUT_ADXL34X && I2C
715	default y
716	help
717	  Say Y here if you have ADXL345/6 hooked to an I2C bus.
718
719	  To compile this driver as a module, choose M here: the
720	  module will be called adxl34x-i2c.
721
722config INPUT_ADXL34X_SPI
723	tristate "support SPI bus connection"
724	depends on INPUT_ADXL34X && SPI
725	default y
726	help
727	  Say Y here if you have ADXL345/6 hooked to a SPI bus.
728
729	  To compile this driver as a module, choose M here: the
730	  module will be called adxl34x-spi.
731
732config INPUT_IBM_PANEL
733	tristate "IBM Operation Panel driver"
734	depends on I2C && I2C_SLAVE
735	help
736	  Say Y here if you have an IBM Operation Panel connected to your system
737	  over I2C. The panel is typically connected only to a system's service
738	  processor (BMC).
739
740	  If unsure, say N.
741
742	  The Operation Panel is a controller with some buttons and an LCD
743	  display that allows someone with physical access to the system to
744	  perform various administrative tasks. This driver only supports the part
745	  of the controller that sends commands to the system.
746
747	  To compile this driver as a module, choose M here: the module will be
748	  called ibm-panel.
749
750config INPUT_IMS_PCU
751	tristate "IMS Passenger Control Unit driver"
752	depends on USB
753	depends on LEDS_CLASS
754	help
755	  Say Y here if you have system with IMS Rave Passenger Control Unit.
756
757	  To compile this driver as a module, choose M here: the module will be
758	  called ims_pcu.
759
760config INPUT_IQS269A
761	tristate "Azoteq IQS269A capacitive touch controller"
762	depends on I2C
763	select REGMAP_I2C
764	help
765	  Say Y to enable support for the Azoteq IQS269A capacitive
766	  touch controller.
767
768	  To compile this driver as a module, choose M here: the
769	  module will be called iqs269a.
770
771config INPUT_IQS626A
772	tristate "Azoteq IQS626A capacitive touch controller"
773	depends on I2C
774	select REGMAP_I2C
775	help
776	  Say Y to enable support for the Azoteq IQS626A capacitive
777	  touch controller.
778
779	  To compile this driver as a module, choose M here: the
780	  module will be called iqs626a.
781
782config INPUT_IQS7222
783	tristate "Azoteq IQS7222A/B/C capacitive touch controller"
784	depends on I2C
785	help
786	  Say Y to enable support for the Azoteq IQS7222A/B/C family
787	  of capacitive touch controllers.
788
789	  To compile this driver as a module, choose M here: the
790	  module will be called iqs7222.
791
792config INPUT_CMA3000
793	tristate "VTI CMA3000 Tri-axis accelerometer"
794	help
795	  Say Y here if you want to use VTI CMA3000_D0x Accelerometer
796	  driver
797
798	  This driver currently only supports I2C interface to the
799	  controller. Also select the I2C method.
800
801	  If unsure, say N
802
803	  To compile this driver as a module, choose M here: the
804	  module will be called cma3000_d0x.
805
806config INPUT_CMA3000_I2C
807	tristate "Support I2C bus connection"
808	depends on INPUT_CMA3000 && I2C
809	help
810	  Say Y here if you want to use VTI CMA3000_D0x Accelerometer
811	  through I2C interface.
812
813	  To compile this driver as a module, choose M here: the
814	  module will be called cma3000_d0x_i2c.
815
816config INPUT_XEN_KBDDEV_FRONTEND
817	tristate "Xen virtual keyboard and mouse support"
818	depends on XEN
819	default y
820	select XEN_XENBUS_FRONTEND
821	help
822	  This driver implements the front-end of the Xen virtual
823	  keyboard and mouse device driver.  It communicates with a back-end
824	  in another domain.
825
826	  To compile this driver as a module, choose M here: the
827	  module will be called xen-kbdfront.
828
829config INPUT_IDEAPAD_SLIDEBAR
830	tristate "IdeaPad Laptop Slidebar"
831	depends on INPUT
832	depends on SERIO_I8042
833	help
834	  Say Y here if you have an IdeaPad laptop with a slidebar.
835
836	  To compile this driver as a module, choose M here: the
837	  module will be called ideapad_slidebar.
838
839config INPUT_SOC_BUTTON_ARRAY
840	tristate "Windows-compatible SoC Button Array"
841	depends on KEYBOARD_GPIO && ACPI
842	help
843	  Say Y here if you have a SoC-based tablet that originally runs
844	  Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later.
845
846	  To compile this driver as a module, choose M here: the
847	  module will be called soc_button_array.
848
849config INPUT_DRV260X_HAPTICS
850	tristate "TI DRV260X haptics support"
851	depends on INPUT && I2C
852	depends on GPIOLIB || COMPILE_TEST
853	select INPUT_FF_MEMLESS
854	select REGMAP_I2C
855	help
856	  Say Y to enable support for the TI DRV260X haptics driver.
857
858	  To compile this driver as a module, choose M here: the
859	  module will be called drv260x-haptics.
860
861config INPUT_DRV2665_HAPTICS
862	tristate "TI DRV2665 haptics support"
863	depends on INPUT && I2C
864	select INPUT_FF_MEMLESS
865	select REGMAP_I2C
866	help
867	  Say Y to enable support for the TI DRV2665 haptics driver.
868
869	  To compile this driver as a module, choose M here: the
870	  module will be called drv2665-haptics.
871
872config INPUT_DRV2667_HAPTICS
873	tristate "TI DRV2667 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 DRV2667 haptics driver.
879
880	  To compile this driver as a module, choose M here: the
881	  module will be called drv2667-haptics.
882
883config INPUT_HISI_POWERKEY
884	tristate "Hisilicon PMIC ONKEY support"
885	depends on ARCH_HISI || COMPILE_TEST
886	help
887	  Say Y to enable support for PMIC ONKEY.
888
889	  To compile this driver as a module, choose M here: the
890	  module will be called hisi_powerkey.
891
892config INPUT_RAVE_SP_PWRBUTTON
893	tristate "RAVE SP Power button Driver"
894	depends on RAVE_SP_CORE
895	help
896	  Say Y here if you want to enable power key reporting from RAVE SP
897
898	  To compile this driver as a module, choose M here: the
899	  module will be called rave-sp-pwrbutton.
900
901config INPUT_SC27XX_VIBRA
902	tristate "Spreadtrum sc27xx vibrator support"
903	depends on MFD_SC27XX_PMIC || COMPILE_TEST
904	select INPUT_FF_MEMLESS
905	help
906	  This option enables support for Spreadtrum sc27xx vibrator driver.
907
908	  To compile this driver as a module, choose M here. The module will
909	  be called sc27xx_vibra.
910
911config INPUT_RT5120_PWRKEY
912	tristate "RT5120 PMIC power key support"
913	depends on MFD_RT5120 || COMPILE_TEST
914	help
915	  This enables support for RT5120 PMIC power key driver.
916
917	  To compile this driver as a module, choose M here. the module will
918	  be called rt5120-pwrkey.
919
920config INPUT_STPMIC1_ONKEY
921	tristate "STPMIC1 PMIC Onkey support"
922	depends on MFD_STPMIC1
923	help
924	  Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
925	  can be used to wakeup from low power modes and force a shut-down on
926	  long press.
927
928	  To compile this driver as a module, choose M here: the
929	  module will be called stpmic1_onkey.
930
931endif
932