xref: /linux-6.15/drivers/input/misc/Kconfig (revision c38fe1bb)
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_CS40L50_VIBRA
144	tristate "CS40L50 Haptic Driver support"
145	depends on MFD_CS40L50_CORE
146	help
147	  Say Y here to enable support for Cirrus Logic's CS40L50
148	  haptic driver.
149
150	  To compile this driver as a module, choose M here: the
151	  module will be called cs40l50-vibra.
152
153config INPUT_E3X0_BUTTON
154	tristate "NI Ettus Research USRP E3xx Button support."
155	default n
156	help
157	  Say Y here to enable support for the NI Ettus Research
158	  USRP E3xx Button.
159
160	  To compile this driver as a module, choose M here: the
161	  module will be called e3x0_button.
162
163config INPUT_PCSPKR
164	tristate "PC Speaker support"
165	depends on PCSPKR_PLATFORM
166	help
167	  Say Y here if you want the standard PC Speaker to be used for
168	  bells and whistles.
169
170	  If unsure, say Y.
171
172	  To compile this driver as a module, choose M here: the
173	  module will be called pcspkr.
174
175config INPUT_PM8941_PWRKEY
176	tristate "Qualcomm PM8941 power key support"
177	depends on MFD_SPMI_PMIC
178	help
179	  Say Y here if you want support for the power key usually found
180	  on boards using a Qualcomm PM8941 compatible PMIC.
181
182	  If unsure, say Y.
183
184	  To compile this driver as a module, choose M here: the module
185	  will be called pm8941-pwrkey.
186
187config INPUT_PM8XXX_VIBRATOR
188	tristate "Qualcomm PM8XXX vibrator support"
189	depends on MFD_PM8XXX || MFD_SPMI_PMIC
190	select INPUT_FF_MEMLESS
191	help
192	  This option enables device driver support for the vibrator
193	  on Qualcomm PM8xxx chip. This driver supports ff-memless interface
194	  from input framework.
195
196	  To compile this driver as module, choose M here: the
197	  module will be called pm8xxx-vibrator.
198
199config INPUT_PMIC8XXX_PWRKEY
200	tristate "PMIC8XXX power key support"
201	depends on MFD_PM8XXX
202	help
203	  Say Y here if you want support for the PMIC8XXX power key.
204
205	  If unsure, say N.
206
207	  To compile this driver as a module, choose M here: the
208	  module will be called pmic8xxx-pwrkey.
209
210config INPUT_SPARCSPKR
211	tristate "SPARC Speaker support"
212	depends on PCI && SPARC64
213	help
214	  Say Y here if you want the standard Speaker on Sparc PCI systems
215	  to be used for bells and whistles.
216
217	  If unsure, say Y.
218
219	  To compile this driver as a module, choose M here: the
220	  module will be called sparcspkr.
221
222config INPUT_M68K_BEEP
223	tristate "M68k Beeper support"
224	depends on M68K
225
226config INPUT_MAX77650_ONKEY
227	tristate "Maxim MAX77650 ONKEY support"
228	depends on MFD_MAX77650
229	help
230	  Support the ONKEY of the MAX77650 PMIC as an input device.
231
232	  To compile this driver as a module, choose M here: the module
233	  will be called max77650-onkey.
234
235config INPUT_MAX77693_HAPTIC
236	tristate "MAXIM MAX77693/MAX77843 haptic controller support"
237	depends on (MFD_MAX77693 || MFD_MAX77843) && PWM
238	select INPUT_FF_MEMLESS
239	help
240	  This option enables support for the haptic controller on
241	  MAXIM MAX77693 and MAX77843 chips.
242
243	  To compile this driver as module, choose M here: the
244	  module will be called max77693-haptic.
245
246config INPUT_MAX8925_ONKEY
247	tristate "MAX8925 ONKEY support"
248	depends on MFD_MAX8925
249	help
250	  Support the ONKEY of MAX8925 PMICs as an input device
251	  reporting power button status.
252
253	  To compile this driver as a module, choose M here: the module
254	  will be called max8925_onkey.
255
256config INPUT_MAX8997_HAPTIC
257	tristate "MAXIM MAX8997 haptic controller support"
258	depends on PWM && MFD_MAX8997
259	select INPUT_FF_MEMLESS
260	help
261	  This option enables device driver support for the haptic controller
262	  on MAXIM MAX8997 chip. This driver supports ff-memless interface
263	  from input framework.
264
265	  To compile this driver as module, choose M here: the
266	  module will be called max8997-haptic.
267
268config INPUT_MC13783_PWRBUTTON
269	tristate "MC13783 ON buttons"
270	depends on MFD_MC13XXX
271	help
272	  Support the ON buttons of MC13783 PMIC as an input device
273	  reporting power button status.
274
275	  To compile this driver as a module, choose M here: the module
276	  will be called mc13783-pwrbutton.
277
278config INPUT_MMA8450
279	tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
280	depends on I2C
281	help
282	  Say Y here if you want to support Freescale's MMA8450 Accelerometer
283	  through I2C interface.
284
285	  To compile this driver as a module, choose M here: the
286	  module will be called mma8450.
287
288config INPUT_APANEL
289	tristate "Fujitsu Lifebook Application Panel buttons"
290	depends on X86 && I2C && LEDS_CLASS
291	select CHECK_SIGNATURE
292	help
293	 Say Y here for support of the Application Panel buttons, used on
294	 Fujitsu Lifebook. These are attached to the mainboard through
295	 an SMBus interface managed by the I2C Intel ICH (i801) driver,
296	 which you should also build for this kernel.
297
298	 To compile this driver as a module, choose M here: the module will
299	 be called apanel.
300
301config INPUT_GPIO_BEEPER
302	tristate "Generic GPIO Beeper support"
303	depends on GPIOLIB || COMPILE_TEST
304	help
305	  Say Y here if you have a beeper connected to a GPIO pin.
306
307	  To compile this driver as a module, choose M here: the
308	  module will be called gpio-beeper.
309
310config INPUT_GPIO_DECODER
311	tristate "Polled GPIO Decoder Input driver"
312	depends on GPIOLIB || COMPILE_TEST
313	help
314	 Say Y here if you want driver to read status of multiple GPIO
315	 lines and report the encoded value as an absolute integer to
316	 input subsystem.
317
318	 To compile this driver as a module, choose M here: the module
319	 will be called gpio_decoder.
320
321config INPUT_GPIO_VIBRA
322	tristate "GPIO vibrator support"
323	depends on GPIOLIB || COMPILE_TEST
324	select INPUT_FF_MEMLESS
325	help
326	  Say Y here to get support for GPIO based vibrator devices.
327
328	  If unsure, say N.
329
330	  To compile this driver as a module, choose M here: the module will be
331	  called gpio-vibra.
332
333config INPUT_COBALT_BTNS
334	tristate "Cobalt button interface"
335	depends on MIPS_COBALT
336	help
337	  Say Y here if you want to support MIPS Cobalt button interface.
338
339	  To compile this driver as a module, choose M here: the
340	  module will be called cobalt_btns.
341
342config INPUT_CPCAP_PWRBUTTON
343	tristate "CPCAP OnKey"
344	depends on MFD_CPCAP
345	help
346	  Say Y here if you want to enable power key reporting via the
347	  Motorola CPCAP chip.
348
349	  To compile this driver as a module, choose M here. The module will
350	  be called cpcap-pwrbutton.
351
352config INPUT_WISTRON_BTNS
353	tristate "x86 Wistron laptop button interface"
354	depends on X86_32 && !UML
355	select INPUT_SPARSEKMAP
356	select NEW_LEDS
357	select LEDS_CLASS
358	select CHECK_SIGNATURE
359	help
360	  Say Y here for support of Wistron laptop button interfaces, used on
361	  laptops of various brands, including Acer and Fujitsu-Siemens. If
362	  available, mail and wifi LEDs will be controllable via /sys/class/leds.
363
364	  To compile this driver as a module, choose M here: the module will
365	  be called wistron_btns.
366
367config INPUT_ATLAS_BTNS
368	tristate "x86 Atlas button interface"
369	depends on X86 && ACPI
370	help
371	  Say Y here for support of Atlas wallmount touchscreen buttons.
372	  The events will show up as scancodes F1 through F9 via evdev.
373
374	  To compile this driver as a module, choose M here: the module will
375	  be called atlas_btns.
376
377config INPUT_ATI_REMOTE2
378	tristate "ATI / Philips USB RF remote control"
379	depends on USB_ARCH_HAS_HCD
380	select USB
381	help
382	  Say Y here if you want to use an ATI or Philips USB RF remote control.
383	  These are RF remotes with USB receivers.
384	  ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
385	  and is also available as a separate product.
386	  This driver provides mouse pointer, left and right mouse buttons,
387	  and maps all the other remote buttons to keypress events.
388
389	  To compile this driver as a module, choose M here: the module will be
390	  called ati_remote2.
391
392config INPUT_KEYSPAN_REMOTE
393	tristate "Keyspan DMR USB remote control"
394	depends on USB_ARCH_HAS_HCD
395	select USB
396	help
397	  Say Y here if you want to use a Keyspan DMR USB remote control.
398	  Currently only the UIA-11 type of receiver has been tested.  The tag
399	  on the receiver that connects to the USB port should have a P/N that
400	  will tell you what type of DMR you have.  The UIA-10 type is not
401	  supported at this time.  This driver maps all buttons to keypress
402	  events.
403
404	  To compile this driver as a module, choose M here: the module will
405	  be called keyspan_remote.
406
407config INPUT_KXTJ9
408	tristate "Kionix KXTJ9 tri-axis digital accelerometer"
409	depends on I2C
410	help
411	  Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
412	  accelerometer.
413
414	  To compile this driver as a module, choose M here: the module will
415	  be called kxtj9.
416
417config INPUT_POWERMATE
418	tristate "Griffin PowerMate and Contour Jog support"
419	depends on USB_ARCH_HAS_HCD
420	select USB
421	help
422	  Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
423	  These are aluminum dials which can measure clockwise and anticlockwise
424	  rotation.  The dial also acts as a pushbutton.  The base contains an LED
425	  which can be instructed to pulse or to switch to a particular intensity.
426
427	  You can download userspace tools from
428	  <http://sowerbutts.com/powermate/>.
429
430	  To compile this driver as a module, choose M here: the
431	  module will be called powermate.
432
433config INPUT_YEALINK
434	tristate "Yealink usb-p1k voip phone"
435	depends on USB_ARCH_HAS_HCD
436	select USB
437	help
438	  Say Y here if you want to enable keyboard and LCD functions of the
439	  Yealink usb-p1k usb phones. The audio part is enabled by the generic
440	  usb sound driver, so you might want to enable that as well.
441
442	  For information about how to use these additional functions, see
443	  <file:Documentation/input/devices/yealink.rst>.
444
445	  To compile this driver as a module, choose M here: the module will be
446	  called yealink.
447
448config INPUT_CM109
449	tristate "C-Media CM109 USB I/O Controller"
450	depends on USB_ARCH_HAS_HCD
451	select USB
452	help
453	  Say Y here if you want to enable keyboard and buzzer functions of the
454	  C-Media CM109 usb phones. The audio part is enabled by the generic
455	  usb sound driver, so you might want to enable that as well.
456
457	  To compile this driver as a module, choose M here: the module will be
458	  called cm109.
459
460config INPUT_REGULATOR_HAPTIC
461	tristate "Regulator haptics support"
462	depends on REGULATOR
463	select INPUT_FF_MEMLESS
464	help
465	  This option enables device driver support for the haptic controlled
466	  by a regulator. This driver supports ff-memless interface
467	  from input framework.
468
469	  To compile this driver as a module, choose M here: the
470	  module will be called regulator-haptic.
471
472config INPUT_RETU_PWRBUTTON
473	tristate "Retu Power button Driver"
474	depends on MFD_RETU
475	help
476	  Say Y here if you want to enable power key reporting via the
477	  Retu chips found in Nokia Internet Tablets (770, N800, N810).
478
479	  To compile this driver as a module, choose M here. The module will
480	  be called retu-pwrbutton.
481
482config INPUT_TPS65218_PWRBUTTON
483	tristate "TPS65218 Power button driver"
484	depends on (MFD_TPS65217 || MFD_TPS65218)
485	help
486	  Say Y here if you want to enable power button reporting for
487	  TPS65217 and TPS65218 Power Management IC devices.
488
489	  To compile this driver as a module, choose M here. The module will
490	  be called tps65218-pwrbutton.
491
492config INPUT_TPS65219_PWRBUTTON
493	tristate "TPS65219 Power button driver"
494	depends on MFD_TPS65219
495	help
496	  Say Y here if you want to enable power button reporting for
497	  TPS65219 Power Management IC devices.
498
499	  To compile this driver as a module, choose M here. The module will
500	  be called tps65219-pwrbutton.
501
502config INPUT_AXP20X_PEK
503	tristate "X-Powers AXP20X power button driver"
504	depends on MFD_AXP20X
505	help
506	  Say Y here if you want to enable power key reporting via the
507	  AXP20X PMIC.
508
509	  To compile this driver as a module, choose M here. The module will
510	  be called axp20x-pek.
511
512
513config INPUT_TWL4030_PWRBUTTON
514	tristate "TWL4030 Power button Driver"
515	depends on TWL4030_CORE
516	help
517	  Say Y here if you want to enable power key reporting via the
518	  TWL4030 family of chips.
519
520	  To compile this driver as a module, choose M here. The module will
521	  be called twl4030_pwrbutton.
522
523config INPUT_TWL4030_VIBRA
524	tristate "Support for TWL4030 Vibrator"
525	depends on TWL4030_CORE
526	select MFD_TWL4030_AUDIO
527	select INPUT_FF_MEMLESS
528	help
529	  This option enables support for TWL4030 Vibrator Driver.
530
531	  To compile this driver as a module, choose M here. The module will
532	  be called twl4030_vibra.
533
534config INPUT_TWL6040_VIBRA
535	tristate "Support for TWL6040 Vibrator"
536	depends on TWL6040_CORE
537	select INPUT_FF_MEMLESS
538	help
539	  This option enables support for TWL6040 Vibrator Driver.
540
541	  To compile this driver as a module, choose M here. The module will
542	  be called twl6040_vibra.
543
544config INPUT_UINPUT
545	tristate "User level driver support"
546	help
547	  Say Y here if you want to support user level drivers for input
548	  subsystem accessible under char device 10:223 - /dev/input/uinput.
549
550	  To compile this driver as a module, choose M here: the
551	  module will be called uinput.
552
553config INPUT_SGI_BTNS
554	tristate "SGI Indy/O2 volume button interface"
555	depends on SGI_IP22 || SGI_IP32
556	help
557	  Say Y here if you want to support SGI Indy/O2 volume button interface.
558
559	  To compile this driver as a module, choose M here: the
560	  module will be called sgi_btns.
561
562config HP_SDC_RTC
563	tristate "HP SDC Real Time Clock"
564	depends on (GSC || HP300) && SERIO
565	select HP_SDC
566	help
567	  Say Y here if you want to support the built-in real time clock
568	  of the HP SDC controller.
569
570config INPUT_PALMAS_PWRBUTTON
571	tristate "Palmas Power button Driver"
572	depends on MFD_PALMAS
573	help
574	  Say Y here if you want to enable power key reporting via the
575	  Palmas family of PMICs.
576
577	  To compile this driver as a module, choose M here. The module will
578	  be called palmas_pwrbutton.
579
580config INPUT_PCF50633_PMU
581	tristate "PCF50633 PMU events"
582	depends on MFD_PCF50633
583	help
584	 Say Y to include support for delivering  PMU events via  input
585	 layer on NXP PCF50633.
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_RAVE_SP_PWRBUTTON
914	tristate "RAVE SP Power button Driver"
915	depends on RAVE_SP_CORE
916	help
917	  Say Y here if you want to enable power key reporting from RAVE SP
918
919	  To compile this driver as a module, choose M here: the
920	  module will be called rave-sp-pwrbutton.
921
922config INPUT_SC27XX_VIBRA
923	tristate "Spreadtrum sc27xx vibrator support"
924	depends on MFD_SC27XX_PMIC || COMPILE_TEST
925	select INPUT_FF_MEMLESS
926	help
927	  This option enables support for Spreadtrum sc27xx vibrator driver.
928
929	  To compile this driver as a module, choose M here. The module will
930	  be called sc27xx_vibra.
931
932config INPUT_RT5120_PWRKEY
933	tristate "RT5120 PMIC power key support"
934	depends on MFD_RT5120 || COMPILE_TEST
935	help
936	  This enables support for RT5120 PMIC power key driver.
937
938	  To compile this driver as a module, choose M here. the module will
939	  be called rt5120-pwrkey.
940
941config INPUT_STPMIC1_ONKEY
942	tristate "STPMIC1 PMIC Onkey support"
943	depends on MFD_STPMIC1
944	help
945	  Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey
946	  can be used to wakeup from low power modes and force a shut-down on
947	  long press.
948
949	  To compile this driver as a module, choose M here: the
950	  module will be called stpmic1_onkey.
951
952endif
953