Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Input misc drivers configuration | |
3 | # | |
4 | menuconfig 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 | ||
13 | if INPUT_MISC | |
14 | ||
69854031 HZ |
15 | config 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 | ||
96c905f4 QZ |
25 | config 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 | ||
77686517 SI |
35 | config 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 | ||
31a62963 BW |
45 | config INPUT_AD714X |
46 | tristate "Analog Devices AD714x Capacitance Touch Sensor" | |
47 | help | |
6c04d7b3 | 48 | Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. |
31a62963 BW |
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 | ||
55 | config 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 | ||
65 | config 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 | ||
9dd555e2 MB |
75 | config 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 | ||
c17ca3f5 EA |
85 | config INPUT_BMA150 |
86 | tristate "BMA150/SMB380 acceleration sensor support" | |
87 | depends on I2C | |
88 | select INPUT_POLLDEV | |
89 | help | |
90 | Say Y here if you have Bosch Sensortec's BMA150 or SMB380 | |
91 | acceleration sensor hooked to an I2C bus. | |
92 | ||
93 | To compile this driver as a module, choose M here: the | |
94 | module will be called bma150. | |
95 | ||
1da177e4 LT |
96 | config INPUT_PCSPKR |
97 | tristate "PC Speaker support" | |
e5e1d3cb | 98 | depends on PCSPKR_PLATFORM |
1da177e4 LT |
99 | help |
100 | Say Y here if you want the standard PC Speaker to be used for | |
101 | bells and whistles. | |
102 | ||
103 | If unsure, say Y. | |
104 | ||
105 | To compile this driver as a module, choose M here: the | |
106 | module will be called pcspkr. | |
107 | ||
11205bb6 AM |
108 | config INPUT_PM8XXX_VIBRATOR |
109 | tristate "Qualcomm PM8XXX vibrator support" | |
110 | depends on MFD_PM8XXX | |
111 | select INPUT_FF_MEMLESS | |
112 | help | |
113 | This option enables device driver support for the vibrator | |
114 | on Qualcomm PM8xxx chip. This driver supports ff-memless interface | |
115 | from input framework. | |
116 | ||
117 | To compile this driver as module, choose M here: the | |
118 | module will be called pm8xxx-vibrator. | |
119 | ||
120 | config INPUT_PMIC8XXX_PWRKEY | |
121 | tristate "PMIC8XXX power key support" | |
122 | depends on MFD_PM8XXX | |
123 | help | |
124 | Say Y here if you want support for the PMIC8XXX power key. | |
125 | ||
126 | If unsure, say N. | |
127 | ||
128 | To compile this driver as a module, choose M here: the | |
129 | module will be called pmic8xxx-pwrkey. | |
130 | ||
1da177e4 LT |
131 | config INPUT_SPARCSPKR |
132 | tristate "SPARC Speaker support" | |
a2bd4fd1 | 133 | depends on PCI && SPARC64 |
1da177e4 LT |
134 | help |
135 | Say Y here if you want the standard Speaker on Sparc PCI systems | |
136 | to be used for bells and whistles. | |
137 | ||
138 | If unsure, say Y. | |
139 | ||
140 | To compile this driver as a module, choose M here: the | |
141 | module will be called sparcspkr. | |
142 | ||
143 | config INPUT_M68K_BEEP | |
144 | tristate "M68k Beeper support" | |
145 | depends on M68K | |
146 | ||
a3b3ca75 JK |
147 | config INPUT_MAX77693_HAPTIC |
148 | tristate "MAXIM MAX77693 haptic controller support" | |
149 | depends on MFD_MAX77693 && PWM | |
150 | select INPUT_FF_MEMLESS | |
151 | help | |
152 | This option enables support for the haptic controller on | |
153 | MAXIM MAX77693 chip. | |
154 | ||
155 | To compile this driver as module, choose M here: the | |
156 | module will be called max77693-haptic. | |
157 | ||
3734574c HZ |
158 | config INPUT_MAX8925_ONKEY |
159 | tristate "MAX8925 ONKEY support" | |
160 | depends on MFD_MAX8925 | |
161 | help | |
162 | Support the ONKEY of MAX8925 PMICs as an input device | |
163 | reporting power button status. | |
164 | ||
165 | To compile this driver as a module, choose M here: the module | |
166 | will be called max8925_onkey. | |
167 | ||
104594b0 DK |
168 | config INPUT_MAX8997_HAPTIC |
169 | tristate "MAXIM MAX8997 haptic controller support" | |
557fe99d | 170 | depends on PWM && MFD_MAX8997 |
104594b0 DK |
171 | select INPUT_FF_MEMLESS |
172 | help | |
173 | This option enables device driver support for the haptic controller | |
174 | on MAXIM MAX8997 chip. This driver supports ff-memless interface | |
175 | from input framework. | |
176 | ||
177 | To compile this driver as module, choose M here: the | |
178 | module will be called max8997-haptic. | |
179 | ||
30fc7ac3 PR |
180 | config INPUT_MC13783_PWRBUTTON |
181 | tristate "MC13783 ON buttons" | |
e5a3da21 | 182 | depends on MFD_MC13XXX |
30fc7ac3 PR |
183 | help |
184 | Support the ON buttons of MC13783 PMIC as an input device | |
185 | reporting power button status. | |
186 | ||
187 | To compile this driver as a module, choose M here: the module | |
188 | will be called mc13783-pwrbutton. | |
189 | ||
3ead8b5d EM |
190 | config INPUT_MMA8450 |
191 | tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" | |
192 | depends on I2C | |
193 | select INPUT_POLLDEV | |
194 | help | |
195 | Say Y here if you want to support Freescale's MMA8450 Accelerometer | |
196 | through I2C interface. | |
197 | ||
198 | To compile this driver as a module, choose M here: the | |
199 | module will be called mma8450. | |
200 | ||
631b16e8 JL |
201 | config INPUT_MPU3050 |
202 | tristate "MPU3050 Triaxial gyroscope sensor" | |
203 | depends on I2C | |
204 | help | |
205 | Say Y here if you want to support InvenSense MPU3050 | |
206 | connected via an I2C bus. | |
207 | ||
208 | To compile this driver as a module, choose M here: the | |
209 | module will be called mpu3050. | |
210 | ||
52fe0cdb SH |
211 | config INPUT_APANEL |
212 | tristate "Fujitsu Lifebook Application Panel buttons" | |
19131305 | 213 | depends on X86 && I2C && LEDS_CLASS |
52fe0cdb SH |
214 | select INPUT_POLLDEV |
215 | select CHECK_SIGNATURE | |
216 | help | |
217 | Say Y here for support of the Application Panel buttons, used on | |
218 | Fujitsu Lifebook. These are attached to the mainboard through | |
19131305 RD |
219 | an SMBus interface managed by the I2C Intel ICH (i801) driver, |
220 | which you should also build for this kernel. | |
52fe0cdb SH |
221 | |
222 | To compile this driver as a module, choose M here: the module will | |
223 | be called apanel. | |
224 | ||
ff803ed4 CC |
225 | config INPUT_GP2A |
226 | tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver" | |
227 | depends on I2C | |
76ec9d18 | 228 | depends on GPIOLIB |
ff803ed4 CC |
229 | help |
230 | Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip | |
231 | hooked to an I2C bus. | |
232 | ||
233 | To compile this driver as a module, choose M here: the | |
234 | module will be called gp2ap002a00f. | |
235 | ||
976358e2 AS |
236 | config INPUT_GPIO_BEEPER |
237 | tristate "Generic GPIO Beeper support" | |
c95dc011 | 238 | depends on GPIOLIB |
976358e2 AS |
239 | help |
240 | Say Y here if you have a beeper connected to a GPIO pin. | |
241 | ||
242 | To compile this driver as a module, choose M here: the | |
243 | module will be called gpio-beeper. | |
244 | ||
3bfd5c5b HS |
245 | config INPUT_GPIO_TILT_POLLED |
246 | tristate "Polled GPIO tilt switch" | |
76ec9d18 | 247 | depends on GPIOLIB |
3bfd5c5b HS |
248 | select INPUT_POLLDEV |
249 | help | |
250 | This driver implements support for tilt switches connected | |
251 | to GPIO pins that are not capable of generating interrupts. | |
252 | ||
253 | The list of gpios to use and the mapping of their states | |
254 | to specific angles is done via platform data. | |
255 | ||
256 | To compile this driver as a module, choose M here: the | |
257 | module will be called gpio_tilt_polled. | |
258 | ||
ba0acb5e DT |
259 | config INPUT_IXP4XX_BEEPER |
260 | tristate "IXP4XX Beeper support" | |
261 | depends on ARCH_IXP4XX | |
262 | help | |
263 | If you say yes here, you can connect a beeper to the | |
264 | ixp4xx gpio pins. This is used by the LinkSys NSLU2. | |
265 | ||
266 | If unsure, say Y. | |
267 | ||
268 | To compile this driver as a module, choose M here: the | |
269 | module will be called ixp4xx-beeper. | |
270 | ||
bebb8a2b YY |
271 | config INPUT_COBALT_BTNS |
272 | tristate "Cobalt button interface" | |
273 | depends on MIPS_COBALT | |
3d29cdff | 274 | select INPUT_POLLDEV |
bebb8a2b YY |
275 | help |
276 | Say Y here if you want to support MIPS Cobalt button interface. | |
277 | ||
278 | To compile this driver as a module, choose M here: the | |
279 | module will be called cobalt_btns. | |
280 | ||
5fc14680 DT |
281 | config INPUT_WISTRON_BTNS |
282 | tristate "x86 Wistron laptop button interface" | |
86234eb7 | 283 | depends on X86_32 |
c2554c91 | 284 | select INPUT_POLLDEV |
e97af4cb | 285 | select INPUT_SPARSEKMAP |
389679d8 EP |
286 | select NEW_LEDS |
287 | select LEDS_CLASS | |
928923c7 | 288 | select CHECK_SIGNATURE |
5fc14680 | 289 | help |
01dd2fbf | 290 | Say Y here for support of Wistron laptop button interfaces, used on |
389679d8 | 291 | laptops of various brands, including Acer and Fujitsu-Siemens. If |
01dd2fbf | 292 | available, mail and wifi LEDs will be controllable via /sys/class/leds. |
5fc14680 DT |
293 | |
294 | To compile this driver as a module, choose M here: the module will | |
295 | be called wistron_btns. | |
296 | ||
31ea7ff0 JK |
297 | config INPUT_ATLAS_BTNS |
298 | tristate "x86 Atlas button interface" | |
299 | depends on X86 && ACPI | |
300 | help | |
301 | Say Y here for support of Atlas wallmount touchscreen buttons. | |
302 | The events will show up as scancodes F1 through F9 via evdev. | |
303 | ||
304 | To compile this driver as a module, choose M here: the module will | |
305 | be called atlas_btns. | |
306 | ||
ba0acb5e DT |
307 | config INPUT_ATI_REMOTE2 |
308 | tristate "ATI / Philips USB RF remote control" | |
7a86edef | 309 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
310 | select USB |
311 | help | |
312 | Say Y here if you want to use an ATI or Philips USB RF remote control. | |
313 | These are RF remotes with USB receivers. | |
314 | ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards | |
315 | and is also available as a separate product. | |
316 | This driver provides mouse pointer, left and right mouse buttons, | |
317 | and maps all the other remote buttons to keypress events. | |
318 | ||
319 | To compile this driver as a module, choose M here: the module will be | |
320 | called ati_remote2. | |
321 | ||
322 | config INPUT_KEYSPAN_REMOTE | |
e52278a3 | 323 | tristate "Keyspan DMR USB remote control" |
7a86edef | 324 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
325 | select USB |
326 | help | |
327 | Say Y here if you want to use a Keyspan DMR USB remote control. | |
328 | Currently only the UIA-11 type of receiver has been tested. The tag | |
329 | on the receiver that connects to the USB port should have a P/N that | |
330 | will tell you what type of DMR you have. The UIA-10 type is not | |
331 | supported at this time. This driver maps all buttons to keypress | |
332 | events. | |
01387959 | 333 | |
ba0acb5e DT |
334 | To compile this driver as a module, choose M here: the module will |
335 | be called keyspan_remote. | |
336 | ||
e8e70d83 CH |
337 | config INPUT_KXTJ9 |
338 | tristate "Kionix KXTJ9 tri-axis digital accelerometer" | |
339 | depends on I2C | |
340 | help | |
341 | Say Y here to enable support for the Kionix KXTJ9 digital tri-axis | |
342 | accelerometer. | |
343 | ||
344 | To compile this driver as a module, choose M here: the module will | |
345 | be called kxtj9. | |
346 | ||
347 | config INPUT_KXTJ9_POLLED_MODE | |
348 | bool "Enable polling mode support" | |
349 | depends on INPUT_KXTJ9 | |
350 | select INPUT_POLLDEV | |
351 | help | |
352 | Say Y here if you need accelerometer to work in polling mode. | |
353 | ||
ba0acb5e DT |
354 | config INPUT_POWERMATE |
355 | tristate "Griffin PowerMate and Contour Jog support" | |
7a86edef | 356 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
357 | select USB |
358 | help | |
359 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | |
360 | These are aluminum dials which can measure clockwise and anticlockwise | |
361 | rotation. The dial also acts as a pushbutton. The base contains an LED | |
362 | which can be instructed to pulse or to switch to a particular intensity. | |
363 | ||
364 | You can download userspace tools from | |
365 | <http://sowerbutts.com/powermate/>. | |
01387959 AZ |
366 | |
367 | To compile this driver as a module, choose M here: the | |
ba0acb5e DT |
368 | module will be called powermate. |
369 | ||
370 | config INPUT_YEALINK | |
371 | tristate "Yealink usb-p1k voip phone" | |
7a86edef | 372 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
373 | select USB |
374 | help | |
375 | Say Y here if you want to enable keyboard and LCD functions of the | |
376 | Yealink usb-p1k usb phones. The audio part is enabled by the generic | |
377 | usb sound driver, so you might want to enable that as well. | |
378 | ||
379 | For information about how to use these additional functions, see | |
380 | <file:Documentation/input/yealink.txt>. | |
381 | ||
382 | To compile this driver as a module, choose M here: the module will be | |
383 | called yealink. | |
01387959 | 384 | |
c04148f9 AH |
385 | config INPUT_CM109 |
386 | tristate "C-Media CM109 USB I/O Controller" | |
c04148f9 AH |
387 | depends on USB_ARCH_HAS_HCD |
388 | select USB | |
389 | help | |
390 | Say Y here if you want to enable keyboard and buzzer functions of the | |
391 | C-Media CM109 usb phones. The audio part is enabled by the generic | |
392 | usb sound driver, so you might want to enable that as well. | |
393 | ||
394 | To compile this driver as a module, choose M here: the module will be | |
395 | called cm109. | |
396 | ||
d64cb71b JK |
397 | config INPUT_REGULATOR_HAPTIC |
398 | tristate "Regulator haptics support" | |
399 | depends on REGULATOR | |
400 | select INPUT_FF_MEMLESS | |
401 | help | |
402 | This option enables device driver support for the haptic controlled | |
403 | by a regulator. This driver supports ff-memless interface | |
404 | from input framework. | |
405 | ||
406 | To compile this driver as a module, choose M here: the | |
407 | module will be called regulator-haptic. | |
408 | ||
544a46c9 AK |
409 | config INPUT_RETU_PWRBUTTON |
410 | tristate "Retu Power button Driver" | |
411 | depends on MFD_RETU | |
412 | help | |
413 | Say Y here if you want to enable power key reporting via the | |
414 | Retu chips found in Nokia Internet Tablets (770, N800, N810). | |
415 | ||
416 | To compile this driver as a module, choose M here. The module will | |
417 | be called retu-pwrbutton. | |
418 | ||
68d8bf04 FB |
419 | config INPUT_TWL4030_PWRBUTTON |
420 | tristate "TWL4030 Power button Driver" | |
421 | depends on TWL4030_CORE | |
422 | help | |
423 | Say Y here if you want to enable power key reporting via the | |
424 | TWL4030 family of chips. | |
425 | ||
426 | To compile this driver as a module, choose M here. The module will | |
427 | be called twl4030_pwrbutton. | |
428 | ||
3dd1b394 JV |
429 | config INPUT_TWL4030_VIBRA |
430 | tristate "Support for TWL4030 Vibrator" | |
431 | depends on TWL4030_CORE | |
57fe7251 | 432 | select MFD_TWL4030_AUDIO |
3dd1b394 JV |
433 | select INPUT_FF_MEMLESS |
434 | help | |
435 | This option enables support for TWL4030 Vibrator Driver. | |
436 | ||
437 | To compile this driver as a module, choose M here. The module will | |
438 | be called twl4030_vibra. | |
439 | ||
cc697d38 MLC |
440 | config INPUT_TWL6040_VIBRA |
441 | tristate "Support for TWL6040 Vibrator" | |
8eaeb939 | 442 | depends on TWL6040_CORE |
cc697d38 MLC |
443 | select INPUT_FF_MEMLESS |
444 | help | |
445 | This option enables support for TWL6040 Vibrator Driver. | |
446 | ||
447 | To compile this driver as a module, choose M here. The module will | |
448 | be called twl6040_vibra. | |
449 | ||
1da177e4 LT |
450 | config INPUT_UINPUT |
451 | tristate "User level driver support" | |
452 | help | |
453 | Say Y here if you want to support user level drivers for input | |
454 | subsystem accessible under char device 10:223 - /dev/input/uinput. | |
455 | ||
456 | To compile this driver as a module, choose M here: the | |
457 | module will be called uinput. | |
458 | ||
48ad88b1 TB |
459 | config INPUT_SGI_BTNS |
460 | tristate "SGI Indy/O2 volume button interface" | |
461 | depends on SGI_IP22 || SGI_IP32 | |
3bee2a04 TB |
462 | select INPUT_POLLDEV |
463 | help | |
48ad88b1 | 464 | Say Y here if you want to support SGI Indy/O2 volume button interface. |
3bee2a04 TB |
465 | |
466 | To compile this driver as a module, choose M here: the | |
48ad88b1 | 467 | module will be called sgi_btns. |
3bee2a04 | 468 | |
1da177e4 | 469 | config HP_SDC_RTC |
bebb8a2b | 470 | tristate "HP SDC Real Time Clock" |
d061ebd5 | 471 | depends on (GSC || HP300) && SERIO |
1da177e4 LT |
472 | select HP_SDC |
473 | help | |
474 | Say Y here if you want to support the built-in real time clock | |
475 | of the HP SDC controller. | |
476 | ||
adff5962 NM |
477 | config INPUT_PALMAS_PWRBUTTON |
478 | tristate "Palmas Power button Driver" | |
479 | depends on MFD_PALMAS | |
480 | help | |
481 | Say Y here if you want to enable power key reporting via the | |
482 | Palmas family of PMICs. | |
483 | ||
484 | To compile this driver as a module, choose M here. The module will | |
485 | be called palmas_pwrbutton. | |
486 | ||
1851b06a BR |
487 | config INPUT_PCF50633_PMU |
488 | tristate "PCF50633 PMU events" | |
489 | depends on MFD_PCF50633 | |
490 | help | |
491 | Say Y to include support for delivering PMU events via input | |
492 | layer on NXP PCF50633. | |
493 | ||
b91c4be7 BW |
494 | config INPUT_PCF8574 |
495 | tristate "PCF8574 Keypad input device" | |
e52278a3 | 496 | depends on I2C |
b91c4be7 | 497 | help |
393f9ffb | 498 | Say Y here if you want to support a keypad connected via I2C |
b91c4be7 BW |
499 | with a PCF8574. |
500 | ||
501 | To compile this driver as a module, choose M here: the | |
502 | module will be called pcf8574_keypad. | |
503 | ||
e22739d0 LPC |
504 | config INPUT_PWM_BEEPER |
505 | tristate "PWM beeper support" | |
557fe99d | 506 | depends on PWM |
e22739d0 LPC |
507 | help |
508 | Say Y here to get support for PWM based beeper devices. | |
509 | ||
510 | If unsure, say N. | |
511 | ||
512 | To compile this driver as a module, choose M here: the module will be | |
513 | called pwm-beeper. | |
514 | ||
73969ff0 DM |
515 | config INPUT_GPIO_ROTARY_ENCODER |
516 | tristate "Rotary encoders connected to GPIO pins" | |
76ec9d18 | 517 | depends on GPIOLIB |
73969ff0 DM |
518 | help |
519 | Say Y here to add support for rotary encoders connected to GPIO lines. | |
492d0f95 | 520 | Check file:Documentation/input/rotary-encoder.txt for more |
73969ff0 DM |
521 | information. |
522 | ||
523 | To compile this driver as a module, choose M here: the | |
524 | module will be called rotary_encoder. | |
525 | ||
d9bdffd2 PS |
526 | config INPUT_RB532_BUTTON |
527 | tristate "Mikrotik Routerboard 532 button interface" | |
528 | depends on MIKROTIK_RB532 | |
76ec9d18 | 529 | depends on GPIOLIB |
d9bdffd2 PS |
530 | select INPUT_POLLDEV |
531 | help | |
532 | Say Y here if you want support for the S1 button built into | |
533 | Mikrotik's Routerboard 532. | |
534 | ||
535 | To compile this driver as a module, choose M here: the | |
536 | module will be called rb532_button. | |
537 | ||
f0c5f65b AJ |
538 | config INPUT_DA9052_ONKEY |
539 | tristate "Dialog DA9052/DA9053 Onkey" | |
540 | depends on PMIC_DA9052 | |
541 | help | |
542 | Support the ONKEY of Dialog DA9052 PMICs as an input device | |
543 | reporting power button status. | |
544 | ||
545 | To compile this driver as a module, choose M here: the | |
546 | module will be called da9052_onkey. | |
547 | ||
8ed2757e AJ |
548 | config INPUT_DA9055_ONKEY |
549 | tristate "Dialog Semiconductor DA9055 ONKEY" | |
550 | depends on MFD_DA9055 | |
551 | help | |
552 | Support the ONKEY of DA9055 PMICs as an input device | |
553 | reporting power button status. | |
554 | ||
555 | To compile this driver as a module, choose M here: the module | |
556 | will be called da9055_onkey. | |
557 | ||
eb990b55 DB |
558 | config INPUT_DM355EVM |
559 | tristate "TI DaVinci DM355 EVM Keypad and IR Remote" | |
560 | depends on MFD_DM355EVM_MSP | |
66040727 | 561 | select INPUT_SPARSEKMAP |
eb990b55 DB |
562 | help |
563 | Supports the pushbuttons and IR remote used with | |
564 | the DM355 EVM board. | |
565 | ||
566 | To compile this driver as a module, choose M here: the | |
567 | module will be called dm355evm_keys. | |
48329582 MH |
568 | |
569 | config INPUT_BFIN_ROTARY | |
570 | tristate "Blackfin Rotary support" | |
571 | depends on BF54x || BF52x | |
572 | help | |
573 | Say Y here if you want to use the Blackfin Rotary. | |
574 | ||
575 | To compile this driver as a module, choose M here: the | |
576 | module will be called bfin-rotary. | |
577 | ||
0c73b992 MB |
578 | config INPUT_WM831X_ON |
579 | tristate "WM831X ON pin" | |
580 | depends on MFD_WM831X | |
581 | help | |
582 | Support the ON pin of WM831X PMICs as an input device | |
583 | reporting power button status. | |
584 | ||
585 | To compile this driver as a module, choose M here: the module | |
586 | will be called wm831x_on. | |
587 | ||
d0a82132 DR |
588 | config INPUT_PCAP |
589 | tristate "Motorola EZX PCAP misc input events" | |
590 | depends on EZX_PCAP | |
591 | help | |
592 | Say Y here if you want to use Power key and Headphone button | |
593 | on Motorola EZX phones. | |
594 | ||
595 | To compile this driver as a module, choose M here: the | |
596 | module will be called pcap_keys. | |
597 | ||
e27c7292 MH |
598 | config INPUT_ADXL34X |
599 | tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" | |
600 | default n | |
601 | help | |
602 | Say Y here if you have a Accelerometer interface using the | |
603 | ADXL345/6 controller, and your board-specific initialization | |
604 | code includes that in its table of devices. | |
605 | ||
606 | This driver can use either I2C or SPI communication to the | |
607 | ADXL345/6 controller. Select the appropriate method for | |
608 | your system. | |
609 | ||
610 | If unsure, say N (but it's safe to say "Y"). | |
611 | ||
612 | To compile this driver as a module, choose M here: the | |
613 | module will be called adxl34x. | |
614 | ||
615 | config INPUT_ADXL34X_I2C | |
616 | tristate "support I2C bus connection" | |
617 | depends on INPUT_ADXL34X && I2C | |
618 | default y | |
619 | help | |
620 | Say Y here if you have ADXL345/6 hooked to an I2C bus. | |
621 | ||
622 | To compile this driver as a module, choose M here: the | |
623 | module will be called adxl34x-i2c. | |
624 | ||
625 | config INPUT_ADXL34X_SPI | |
626 | tristate "support SPI bus connection" | |
627 | depends on INPUT_ADXL34X && SPI | |
628 | default y | |
629 | help | |
630 | Say Y here if you have ADXL345/6 hooked to a SPI bus. | |
631 | ||
632 | To compile this driver as a module, choose M here: the | |
633 | module will be called adxl34x-spi. | |
634 | ||
628329d5 DT |
635 | config INPUT_IMS_PCU |
636 | tristate "IMS Passenger Control Unit driver" | |
637 | depends on USB | |
638 | depends on LEDS_CLASS | |
639 | help | |
640 | Say Y here if you have system with IMS Rave Passenger Control Unit. | |
641 | ||
642 | To compile this driver as a module, choose M here: the module will be | |
643 | called ims_pcu. | |
644 | ||
b029ffaf H |
645 | config INPUT_CMA3000 |
646 | tristate "VTI CMA3000 Tri-axis accelerometer" | |
647 | help | |
648 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
649 | driver | |
650 | ||
651 | This driver currently only supports I2C interface to the | |
652 | controller. Also select the I2C method. | |
653 | ||
654 | If unsure, say N | |
655 | ||
656 | To compile this driver as a module, choose M here: the | |
657 | module will be called cma3000_d0x. | |
658 | ||
659 | config INPUT_CMA3000_I2C | |
660 | tristate "Support I2C bus connection" | |
661 | depends on INPUT_CMA3000 && I2C | |
662 | help | |
663 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
664 | through I2C interface. | |
665 | ||
666 | To compile this driver as a module, choose M here: the | |
667 | module will be called cma3000_d0x_i2c. | |
668 | ||
49851ca0 DT |
669 | config INPUT_XEN_KBDDEV_FRONTEND |
670 | tristate "Xen virtual keyboard and mouse support" | |
4bc25af7 | 671 | depends on XEN |
49851ca0 DT |
672 | default y |
673 | select XEN_XENBUS_FRONTEND | |
674 | help | |
675 | This driver implements the front-end of the Xen virtual | |
676 | keyboard and mouse device driver. It communicates with a back-end | |
677 | in another domain. | |
678 | ||
679 | To compile this driver as a module, choose M here: the | |
680 | module will be called xen-kbdfront. | |
681 | ||
9b5f953d BD |
682 | config INPUT_SIRFSOC_ONKEY |
683 | bool "CSR SiRFSoC power on/off/suspend key support" | |
684 | depends on ARCH_SIRF && OF | |
685 | default y | |
686 | help | |
687 | Say Y here if you want to support for the SiRFSoC power on/off/suspend key | |
688 | in Linux, after you press the onkey, system will suspend. | |
689 | ||
690 | If unsure, say N. | |
691 | ||
1ea4c161 AM |
692 | config INPUT_IDEAPAD_SLIDEBAR |
693 | tristate "IdeaPad Laptop Slidebar" | |
694 | depends on INPUT | |
695 | depends on SERIO_I8042 | |
696 | help | |
697 | Say Y here if you have an IdeaPad laptop with a slidebar. | |
698 | ||
699 | To compile this driver as a module, choose M here: the | |
700 | module will be called ideapad_slidebar. | |
701 | ||
61cd4822 LZ |
702 | config INPUT_SOC_BUTTON_ARRAY |
703 | tristate "Windows-compatible SoC Button Array" | |
704 | depends on KEYBOARD_GPIO | |
705 | help | |
706 | Say Y here if you have a SoC-based tablet that originally | |
707 | runs Windows 8. | |
708 | ||
709 | To compile this driver as a module, choose M here: the | |
710 | module will be called soc_button_array. | |
711 | ||
7132fe4f DM |
712 | config INPUT_DRV260X_HAPTICS |
713 | tristate "TI DRV260X haptics support" | |
714 | depends on INPUT && I2C && GPIOLIB | |
715 | select INPUT_FF_MEMLESS | |
716 | select REGMAP_I2C | |
717 | help | |
718 | Say Y to enable support for the TI DRV260X haptics driver. | |
719 | ||
720 | To compile this driver as a module, choose M here: the | |
721 | module will be called drv260x-haptics. | |
722 | ||
1c246225 DM |
723 | config INPUT_DRV2667_HAPTICS |
724 | tristate "TI DRV2667 haptics support" | |
725 | depends on INPUT && I2C | |
726 | select INPUT_FF_MEMLESS | |
727 | select REGMAP_I2C | |
728 | help | |
729 | Say Y to enable support for the TI DRV2667 haptics driver. | |
730 | ||
731 | To compile this driver as a module, choose M here: the | |
732 | module will be called drv260x-haptics. | |
733 | ||
1da177e4 | 734 | endif |