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 | ||
77686517 SI |
25 | config INPUT_AB8500_PONKEY |
26 | tristate "AB8500 Pon (PowerOn) Key" | |
27 | depends on AB8500_CORE | |
28 | help | |
29 | Say Y here to use the PowerOn Key for ST-Ericsson's AB8500 | |
30 | Mix-Sig PMIC. | |
31 | ||
32 | To compile this driver as a module, choose M here: the module | |
33 | will be called ab8500-ponkey. | |
34 | ||
31a62963 BW |
35 | config INPUT_AD714X |
36 | tristate "Analog Devices AD714x Capacitance Touch Sensor" | |
37 | help | |
6c04d7b3 | 38 | Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. |
31a62963 BW |
39 | |
40 | You should select a bus connection too. | |
41 | ||
42 | To compile this driver as a module, choose M here: the | |
43 | module will be called ad714x. | |
44 | ||
45 | config INPUT_AD714X_I2C | |
46 | tristate "support I2C bus connection" | |
47 | depends on INPUT_AD714X && I2C | |
48 | default y | |
49 | help | |
50 | Say Y here if you have AD7142/AD7147 hooked to an I2C bus. | |
51 | ||
52 | To compile this driver as a module, choose M here: the | |
53 | module will be called ad714x-i2c. | |
54 | ||
55 | config INPUT_AD714X_SPI | |
56 | tristate "support SPI bus connection" | |
57 | depends on INPUT_AD714X && SPI | |
58 | default y | |
59 | help | |
60 | Say Y here if you have AD7142/AD7147 hooked to a SPI bus. | |
61 | ||
62 | To compile this driver as a module, choose M here: the | |
63 | module will be called ad714x-spi. | |
64 | ||
c17ca3f5 EA |
65 | config INPUT_BMA150 |
66 | tristate "BMA150/SMB380 acceleration sensor support" | |
67 | depends on I2C | |
68 | select INPUT_POLLDEV | |
69 | help | |
70 | Say Y here if you have Bosch Sensortec's BMA150 or SMB380 | |
71 | acceleration sensor hooked to an I2C bus. | |
72 | ||
73 | To compile this driver as a module, choose M here: the | |
74 | module will be called bma150. | |
75 | ||
1da177e4 LT |
76 | config INPUT_PCSPKR |
77 | tristate "PC Speaker support" | |
e5e1d3cb | 78 | depends on PCSPKR_PLATFORM |
1da177e4 LT |
79 | help |
80 | Say Y here if you want the standard PC Speaker to be used for | |
81 | bells and whistles. | |
82 | ||
83 | If unsure, say Y. | |
84 | ||
85 | To compile this driver as a module, choose M here: the | |
86 | module will be called pcspkr. | |
87 | ||
11205bb6 AM |
88 | config INPUT_PM8XXX_VIBRATOR |
89 | tristate "Qualcomm PM8XXX vibrator support" | |
90 | depends on MFD_PM8XXX | |
91 | select INPUT_FF_MEMLESS | |
92 | help | |
93 | This option enables device driver support for the vibrator | |
94 | on Qualcomm PM8xxx chip. This driver supports ff-memless interface | |
95 | from input framework. | |
96 | ||
97 | To compile this driver as module, choose M here: the | |
98 | module will be called pm8xxx-vibrator. | |
99 | ||
100 | config INPUT_PMIC8XXX_PWRKEY | |
101 | tristate "PMIC8XXX power key support" | |
102 | depends on MFD_PM8XXX | |
103 | help | |
104 | Say Y here if you want support for the PMIC8XXX power key. | |
105 | ||
106 | If unsure, say N. | |
107 | ||
108 | To compile this driver as a module, choose M here: the | |
109 | module will be called pmic8xxx-pwrkey. | |
110 | ||
1da177e4 LT |
111 | config INPUT_SPARCSPKR |
112 | tristate "SPARC Speaker support" | |
a2bd4fd1 | 113 | depends on PCI && SPARC64 |
1da177e4 LT |
114 | help |
115 | Say Y here if you want the standard Speaker on Sparc PCI systems | |
116 | to be used for bells and whistles. | |
117 | ||
118 | If unsure, say Y. | |
119 | ||
120 | To compile this driver as a module, choose M here: the | |
121 | module will be called sparcspkr. | |
122 | ||
123 | config INPUT_M68K_BEEP | |
124 | tristate "M68k Beeper support" | |
125 | depends on M68K | |
126 | ||
3734574c HZ |
127 | config INPUT_MAX8925_ONKEY |
128 | tristate "MAX8925 ONKEY support" | |
129 | depends on MFD_MAX8925 | |
130 | help | |
131 | Support the ONKEY of MAX8925 PMICs as an input device | |
132 | reporting power button status. | |
133 | ||
134 | To compile this driver as a module, choose M here: the module | |
135 | will be called max8925_onkey. | |
136 | ||
30fc7ac3 PR |
137 | config INPUT_MC13783_PWRBUTTON |
138 | tristate "MC13783 ON buttons" | |
139 | depends on MFD_MC13783 | |
140 | help | |
141 | Support the ON buttons of MC13783 PMIC as an input device | |
142 | reporting power button status. | |
143 | ||
144 | To compile this driver as a module, choose M here: the module | |
145 | will be called mc13783-pwrbutton. | |
146 | ||
3ead8b5d EM |
147 | config INPUT_MMA8450 |
148 | tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" | |
149 | depends on I2C | |
150 | select INPUT_POLLDEV | |
151 | help | |
152 | Say Y here if you want to support Freescale's MMA8450 Accelerometer | |
153 | through I2C interface. | |
154 | ||
155 | To compile this driver as a module, choose M here: the | |
156 | module will be called mma8450. | |
157 | ||
631b16e8 JL |
158 | config INPUT_MPU3050 |
159 | tristate "MPU3050 Triaxial gyroscope sensor" | |
160 | depends on I2C | |
161 | help | |
162 | Say Y here if you want to support InvenSense MPU3050 | |
163 | connected via an I2C bus. | |
164 | ||
165 | To compile this driver as a module, choose M here: the | |
166 | module will be called mpu3050. | |
167 | ||
52fe0cdb SH |
168 | config INPUT_APANEL |
169 | tristate "Fujitsu Lifebook Application Panel buttons" | |
19131305 | 170 | depends on X86 && I2C && LEDS_CLASS |
52fe0cdb SH |
171 | select INPUT_POLLDEV |
172 | select CHECK_SIGNATURE | |
173 | help | |
174 | Say Y here for support of the Application Panel buttons, used on | |
175 | Fujitsu Lifebook. These are attached to the mainboard through | |
19131305 RD |
176 | an SMBus interface managed by the I2C Intel ICH (i801) driver, |
177 | which you should also build for this kernel. | |
52fe0cdb SH |
178 | |
179 | To compile this driver as a module, choose M here: the module will | |
180 | be called apanel. | |
181 | ||
ff803ed4 CC |
182 | config INPUT_GP2A |
183 | tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver" | |
184 | depends on I2C | |
185 | depends on GENERIC_GPIO | |
186 | help | |
187 | Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip | |
188 | hooked to an I2C bus. | |
189 | ||
190 | To compile this driver as a module, choose M here: the | |
191 | module will be called gp2ap002a00f. | |
192 | ||
3bfd5c5b HS |
193 | config INPUT_GPIO_TILT_POLLED |
194 | tristate "Polled GPIO tilt switch" | |
195 | depends on GENERIC_GPIO | |
196 | select INPUT_POLLDEV | |
197 | help | |
198 | This driver implements support for tilt switches connected | |
199 | to GPIO pins that are not capable of generating interrupts. | |
200 | ||
201 | The list of gpios to use and the mapping of their states | |
202 | to specific angles is done via platform data. | |
203 | ||
204 | To compile this driver as a module, choose M here: the | |
205 | module will be called gpio_tilt_polled. | |
206 | ||
ba0acb5e DT |
207 | config INPUT_IXP4XX_BEEPER |
208 | tristate "IXP4XX Beeper support" | |
209 | depends on ARCH_IXP4XX | |
210 | help | |
211 | If you say yes here, you can connect a beeper to the | |
212 | ixp4xx gpio pins. This is used by the LinkSys NSLU2. | |
213 | ||
214 | If unsure, say Y. | |
215 | ||
216 | To compile this driver as a module, choose M here: the | |
217 | module will be called ixp4xx-beeper. | |
218 | ||
bebb8a2b YY |
219 | config INPUT_COBALT_BTNS |
220 | tristate "Cobalt button interface" | |
221 | depends on MIPS_COBALT | |
3d29cdff | 222 | select INPUT_POLLDEV |
bebb8a2b YY |
223 | help |
224 | Say Y here if you want to support MIPS Cobalt button interface. | |
225 | ||
226 | To compile this driver as a module, choose M here: the | |
227 | module will be called cobalt_btns. | |
228 | ||
5fc14680 DT |
229 | config INPUT_WISTRON_BTNS |
230 | tristate "x86 Wistron laptop button interface" | |
e9fb028e | 231 | depends on X86 && !X86_64 |
c2554c91 | 232 | select INPUT_POLLDEV |
e97af4cb | 233 | select INPUT_SPARSEKMAP |
389679d8 EP |
234 | select NEW_LEDS |
235 | select LEDS_CLASS | |
928923c7 | 236 | select CHECK_SIGNATURE |
5fc14680 | 237 | help |
01dd2fbf | 238 | Say Y here for support of Wistron laptop button interfaces, used on |
389679d8 | 239 | laptops of various brands, including Acer and Fujitsu-Siemens. If |
01dd2fbf | 240 | available, mail and wifi LEDs will be controllable via /sys/class/leds. |
5fc14680 DT |
241 | |
242 | To compile this driver as a module, choose M here: the module will | |
243 | be called wistron_btns. | |
244 | ||
31ea7ff0 JK |
245 | config INPUT_ATLAS_BTNS |
246 | tristate "x86 Atlas button interface" | |
247 | depends on X86 && ACPI | |
248 | help | |
249 | Say Y here for support of Atlas wallmount touchscreen buttons. | |
250 | The events will show up as scancodes F1 through F9 via evdev. | |
251 | ||
252 | To compile this driver as a module, choose M here: the module will | |
253 | be called atlas_btns. | |
254 | ||
ba0acb5e DT |
255 | config INPUT_ATI_REMOTE2 |
256 | tristate "ATI / Philips USB RF remote control" | |
7a86edef | 257 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
258 | select USB |
259 | help | |
260 | Say Y here if you want to use an ATI or Philips USB RF remote control. | |
261 | These are RF remotes with USB receivers. | |
262 | ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards | |
263 | and is also available as a separate product. | |
264 | This driver provides mouse pointer, left and right mouse buttons, | |
265 | and maps all the other remote buttons to keypress events. | |
266 | ||
267 | To compile this driver as a module, choose M here: the module will be | |
268 | called ati_remote2. | |
269 | ||
270 | config INPUT_KEYSPAN_REMOTE | |
271 | tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" | |
272 | depends on EXPERIMENTAL | |
7a86edef | 273 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
274 | select USB |
275 | help | |
276 | Say Y here if you want to use a Keyspan DMR USB remote control. | |
277 | Currently only the UIA-11 type of receiver has been tested. The tag | |
278 | on the receiver that connects to the USB port should have a P/N that | |
279 | will tell you what type of DMR you have. The UIA-10 type is not | |
280 | supported at this time. This driver maps all buttons to keypress | |
281 | events. | |
01387959 | 282 | |
ba0acb5e DT |
283 | To compile this driver as a module, choose M here: the module will |
284 | be called keyspan_remote. | |
285 | ||
e8e70d83 CH |
286 | config INPUT_KXTJ9 |
287 | tristate "Kionix KXTJ9 tri-axis digital accelerometer" | |
288 | depends on I2C | |
289 | help | |
290 | Say Y here to enable support for the Kionix KXTJ9 digital tri-axis | |
291 | accelerometer. | |
292 | ||
293 | To compile this driver as a module, choose M here: the module will | |
294 | be called kxtj9. | |
295 | ||
296 | config INPUT_KXTJ9_POLLED_MODE | |
297 | bool "Enable polling mode support" | |
298 | depends on INPUT_KXTJ9 | |
299 | select INPUT_POLLDEV | |
300 | help | |
301 | Say Y here if you need accelerometer to work in polling mode. | |
302 | ||
ba0acb5e DT |
303 | config INPUT_POWERMATE |
304 | tristate "Griffin PowerMate and Contour Jog support" | |
7a86edef | 305 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
306 | select USB |
307 | help | |
308 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | |
309 | These are aluminum dials which can measure clockwise and anticlockwise | |
310 | rotation. The dial also acts as a pushbutton. The base contains an LED | |
311 | which can be instructed to pulse or to switch to a particular intensity. | |
312 | ||
313 | You can download userspace tools from | |
314 | <http://sowerbutts.com/powermate/>. | |
01387959 AZ |
315 | |
316 | To compile this driver as a module, choose M here: the | |
ba0acb5e DT |
317 | module will be called powermate. |
318 | ||
319 | config INPUT_YEALINK | |
320 | tristate "Yealink usb-p1k voip phone" | |
247537b9 | 321 | depends on EXPERIMENTAL |
7a86edef | 322 | depends on USB_ARCH_HAS_HCD |
ba0acb5e DT |
323 | select USB |
324 | help | |
325 | Say Y here if you want to enable keyboard and LCD functions of the | |
326 | Yealink usb-p1k usb phones. The audio part is enabled by the generic | |
327 | usb sound driver, so you might want to enable that as well. | |
328 | ||
329 | For information about how to use these additional functions, see | |
330 | <file:Documentation/input/yealink.txt>. | |
331 | ||
332 | To compile this driver as a module, choose M here: the module will be | |
333 | called yealink. | |
01387959 | 334 | |
c04148f9 AH |
335 | config INPUT_CM109 |
336 | tristate "C-Media CM109 USB I/O Controller" | |
337 | depends on EXPERIMENTAL | |
338 | depends on USB_ARCH_HAS_HCD | |
339 | select USB | |
340 | help | |
341 | Say Y here if you want to enable keyboard and buzzer functions of the | |
342 | C-Media CM109 usb phones. The audio part is enabled by the generic | |
343 | usb sound driver, so you might want to enable that as well. | |
344 | ||
345 | To compile this driver as a module, choose M here: the module will be | |
346 | called cm109. | |
347 | ||
68d8bf04 FB |
348 | config INPUT_TWL4030_PWRBUTTON |
349 | tristate "TWL4030 Power button Driver" | |
350 | depends on TWL4030_CORE | |
351 | help | |
352 | Say Y here if you want to enable power key reporting via the | |
353 | TWL4030 family of chips. | |
354 | ||
355 | To compile this driver as a module, choose M here. The module will | |
356 | be called twl4030_pwrbutton. | |
357 | ||
3dd1b394 JV |
358 | config INPUT_TWL4030_VIBRA |
359 | tristate "Support for TWL4030 Vibrator" | |
360 | depends on TWL4030_CORE | |
57fe7251 | 361 | select MFD_TWL4030_AUDIO |
3dd1b394 JV |
362 | select INPUT_FF_MEMLESS |
363 | help | |
364 | This option enables support for TWL4030 Vibrator Driver. | |
365 | ||
366 | To compile this driver as a module, choose M here. The module will | |
367 | be called twl4030_vibra. | |
368 | ||
cc697d38 MLC |
369 | config INPUT_TWL6040_VIBRA |
370 | tristate "Support for TWL6040 Vibrator" | |
371 | depends on TWL4030_CORE | |
372 | select TWL6040_CORE | |
373 | select INPUT_FF_MEMLESS | |
374 | help | |
375 | This option enables support for TWL6040 Vibrator Driver. | |
376 | ||
377 | To compile this driver as a module, choose M here. The module will | |
378 | be called twl6040_vibra. | |
379 | ||
1da177e4 LT |
380 | config INPUT_UINPUT |
381 | tristate "User level driver support" | |
382 | help | |
383 | Say Y here if you want to support user level drivers for input | |
384 | subsystem accessible under char device 10:223 - /dev/input/uinput. | |
385 | ||
386 | To compile this driver as a module, choose M here: the | |
387 | module will be called uinput. | |
388 | ||
48ad88b1 TB |
389 | config INPUT_SGI_BTNS |
390 | tristate "SGI Indy/O2 volume button interface" | |
391 | depends on SGI_IP22 || SGI_IP32 | |
3bee2a04 TB |
392 | select INPUT_POLLDEV |
393 | help | |
48ad88b1 | 394 | Say Y here if you want to support SGI Indy/O2 volume button interface. |
3bee2a04 TB |
395 | |
396 | To compile this driver as a module, choose M here: the | |
48ad88b1 | 397 | module will be called sgi_btns. |
3bee2a04 | 398 | |
1da177e4 | 399 | config HP_SDC_RTC |
bebb8a2b | 400 | tristate "HP SDC Real Time Clock" |
d061ebd5 | 401 | depends on (GSC || HP300) && SERIO |
1da177e4 LT |
402 | select HP_SDC |
403 | help | |
404 | Say Y here if you want to support the built-in real time clock | |
405 | of the HP SDC controller. | |
406 | ||
1851b06a BR |
407 | config INPUT_PCF50633_PMU |
408 | tristate "PCF50633 PMU events" | |
409 | depends on MFD_PCF50633 | |
410 | help | |
411 | Say Y to include support for delivering PMU events via input | |
412 | layer on NXP PCF50633. | |
413 | ||
b91c4be7 BW |
414 | config INPUT_PCF8574 |
415 | tristate "PCF8574 Keypad input device" | |
416 | depends on I2C && EXPERIMENTAL | |
417 | help | |
393f9ffb | 418 | Say Y here if you want to support a keypad connected via I2C |
b91c4be7 BW |
419 | with a PCF8574. |
420 | ||
421 | To compile this driver as a module, choose M here: the | |
422 | module will be called pcf8574_keypad. | |
423 | ||
e22739d0 LPC |
424 | config INPUT_PWM_BEEPER |
425 | tristate "PWM beeper support" | |
426 | depends on HAVE_PWM | |
427 | help | |
428 | Say Y here to get support for PWM based beeper devices. | |
429 | ||
430 | If unsure, say N. | |
431 | ||
432 | To compile this driver as a module, choose M here: the module will be | |
433 | called pwm-beeper. | |
434 | ||
73969ff0 DM |
435 | config INPUT_GPIO_ROTARY_ENCODER |
436 | tristate "Rotary encoders connected to GPIO pins" | |
437 | depends on GPIOLIB && GENERIC_GPIO | |
438 | help | |
439 | Say Y here to add support for rotary encoders connected to GPIO lines. | |
492d0f95 | 440 | Check file:Documentation/input/rotary-encoder.txt for more |
73969ff0 DM |
441 | information. |
442 | ||
443 | To compile this driver as a module, choose M here: the | |
444 | module will be called rotary_encoder. | |
445 | ||
d9bdffd2 PS |
446 | config INPUT_RB532_BUTTON |
447 | tristate "Mikrotik Routerboard 532 button interface" | |
448 | depends on MIKROTIK_RB532 | |
449 | depends on GPIOLIB && GENERIC_GPIO | |
450 | select INPUT_POLLDEV | |
451 | help | |
452 | Say Y here if you want support for the S1 button built into | |
453 | Mikrotik's Routerboard 532. | |
454 | ||
455 | To compile this driver as a module, choose M here: the | |
456 | module will be called rb532_button. | |
457 | ||
f0c5f65b AJ |
458 | config INPUT_DA9052_ONKEY |
459 | tristate "Dialog DA9052/DA9053 Onkey" | |
460 | depends on PMIC_DA9052 | |
461 | help | |
462 | Support the ONKEY of Dialog DA9052 PMICs as an input device | |
463 | reporting power button status. | |
464 | ||
465 | To compile this driver as a module, choose M here: the | |
466 | module will be called da9052_onkey. | |
467 | ||
eb990b55 DB |
468 | config INPUT_DM355EVM |
469 | tristate "TI DaVinci DM355 EVM Keypad and IR Remote" | |
470 | depends on MFD_DM355EVM_MSP | |
66040727 | 471 | select INPUT_SPARSEKMAP |
eb990b55 DB |
472 | help |
473 | Supports the pushbuttons and IR remote used with | |
474 | the DM355 EVM board. | |
475 | ||
476 | To compile this driver as a module, choose M here: the | |
477 | module will be called dm355evm_keys. | |
48329582 MH |
478 | |
479 | config INPUT_BFIN_ROTARY | |
480 | tristate "Blackfin Rotary support" | |
481 | depends on BF54x || BF52x | |
482 | help | |
483 | Say Y here if you want to use the Blackfin Rotary. | |
484 | ||
485 | To compile this driver as a module, choose M here: the | |
486 | module will be called bfin-rotary. | |
487 | ||
0c73b992 MB |
488 | config INPUT_WM831X_ON |
489 | tristate "WM831X ON pin" | |
490 | depends on MFD_WM831X | |
491 | help | |
492 | Support the ON pin of WM831X PMICs as an input device | |
493 | reporting power button status. | |
494 | ||
495 | To compile this driver as a module, choose M here: the module | |
496 | will be called wm831x_on. | |
497 | ||
d0a82132 DR |
498 | config INPUT_PCAP |
499 | tristate "Motorola EZX PCAP misc input events" | |
500 | depends on EZX_PCAP | |
501 | help | |
502 | Say Y here if you want to use Power key and Headphone button | |
503 | on Motorola EZX phones. | |
504 | ||
505 | To compile this driver as a module, choose M here: the | |
506 | module will be called pcap_keys. | |
507 | ||
e27c7292 MH |
508 | config INPUT_ADXL34X |
509 | tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" | |
510 | default n | |
511 | help | |
512 | Say Y here if you have a Accelerometer interface using the | |
513 | ADXL345/6 controller, and your board-specific initialization | |
514 | code includes that in its table of devices. | |
515 | ||
516 | This driver can use either I2C or SPI communication to the | |
517 | ADXL345/6 controller. Select the appropriate method for | |
518 | your system. | |
519 | ||
520 | If unsure, say N (but it's safe to say "Y"). | |
521 | ||
522 | To compile this driver as a module, choose M here: the | |
523 | module will be called adxl34x. | |
524 | ||
525 | config INPUT_ADXL34X_I2C | |
526 | tristate "support I2C bus connection" | |
527 | depends on INPUT_ADXL34X && I2C | |
528 | default y | |
529 | help | |
530 | Say Y here if you have ADXL345/6 hooked to an I2C bus. | |
531 | ||
532 | To compile this driver as a module, choose M here: the | |
533 | module will be called adxl34x-i2c. | |
534 | ||
535 | config INPUT_ADXL34X_SPI | |
536 | tristate "support SPI bus connection" | |
537 | depends on INPUT_ADXL34X && SPI | |
538 | default y | |
539 | help | |
540 | Say Y here if you have ADXL345/6 hooked to a SPI bus. | |
541 | ||
542 | To compile this driver as a module, choose M here: the | |
543 | module will be called adxl34x-spi. | |
544 | ||
b029ffaf H |
545 | config INPUT_CMA3000 |
546 | tristate "VTI CMA3000 Tri-axis accelerometer" | |
547 | help | |
548 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
549 | driver | |
550 | ||
551 | This driver currently only supports I2C interface to the | |
552 | controller. Also select the I2C method. | |
553 | ||
554 | If unsure, say N | |
555 | ||
556 | To compile this driver as a module, choose M here: the | |
557 | module will be called cma3000_d0x. | |
558 | ||
559 | config INPUT_CMA3000_I2C | |
560 | tristate "Support I2C bus connection" | |
561 | depends on INPUT_CMA3000 && I2C | |
562 | help | |
563 | Say Y here if you want to use VTI CMA3000_D0x Accelerometer | |
564 | through I2C interface. | |
565 | ||
566 | To compile this driver as a module, choose M here: the | |
567 | module will be called cma3000_d0x_i2c. | |
568 | ||
49851ca0 DT |
569 | config INPUT_XEN_KBDDEV_FRONTEND |
570 | tristate "Xen virtual keyboard and mouse support" | |
571 | depends on XEN_FBDEV_FRONTEND | |
572 | default y | |
573 | select XEN_XENBUS_FRONTEND | |
574 | help | |
575 | This driver implements the front-end of the Xen virtual | |
576 | keyboard and mouse device driver. It communicates with a back-end | |
577 | in another domain. | |
578 | ||
579 | To compile this driver as a module, choose M here: the | |
580 | module will be called xen-kbdfront. | |
581 | ||
1da177e4 | 582 | endif |