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