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