blob: c528deadd63c0e0bce3a6603c3018d24ab2d9145 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Input misc drivers configuration
3#
4menuconfig INPUT_MISC
5 bool "Miscellaneous devices"
6 help
7 Say Y here, and a list of miscellaneous input drivers will be displayed.
8 Everything that didn't fit into the other categories is here. This option
9 doesn't affect the kernel.
10
11 If unsure, say Y.
12
13if INPUT_MISC
14
Haojian Zhuang69854032010-02-03 15:40:59 -050015config 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
Sundar R Iyer77686512010-09-05 12:18:47 -070025config 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
Bryan Wu31a62962010-03-21 23:23:24 -070035config INPUT_AD714X
36 tristate "Analog Devices AD714x Capacitance Touch Sensor"
37 help
Barry Song6c04d7b2010-03-21 23:23:29 -070038 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
Bryan Wu31a62962010-03-21 23:23:24 -070039
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
45config 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
55config 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
Eric Anderssonc17ca3f2011-08-09 00:06:37 -070065config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070076config INPUT_PCSPKR
77 tristate "PC Speaker support"
Stas Sergeeve5e1d3c2008-05-07 12:39:56 +020078 depends on PCSPKR_PLATFORM
Linus Torvalds1da177e2005-04-16 15:20:36 -070079 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
Amy Maloche11205bb2011-08-01 23:41:44 -070088config 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
100config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700111config INPUT_SPARCSPKR
112 tristate "SPARC Speaker support"
David S. Millera2bd4fd2006-06-23 01:44:10 -0700113 depends on PCI && SPARC64
Linus Torvalds1da177e2005-04-16 15:20:36 -0700114 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
123config INPUT_M68K_BEEP
124 tristate "M68k Beeper support"
125 depends on M68K
126
Haojian Zhuang37345742010-05-22 00:57:26 -0700127config 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
Philippe Rétornaz30fc7ac2011-09-18 18:10:53 +0200137config 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
Eric Miao3ead8b52011-06-22 01:02:50 -0700147config 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
Joseph Lai631b16e2011-06-27 13:26:53 -0700158config 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
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500168config INPUT_APANEL
169 tristate "Fujitsu Lifebook Application Panel buttons"
Randy Dunlap19131302008-03-04 14:29:43 -0800170 depends on X86 && I2C && LEDS_CLASS
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500171 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
Randy Dunlap19131302008-03-04 14:29:43 -0800176 an SMBus interface managed by the I2C Intel ICH (i801) driver,
177 which you should also build for this kernel.
Stephen Hemminger52fe0cd2007-12-14 11:08:37 -0500178
179 To compile this driver as a module, choose M here: the module will
180 be called apanel.
181
Courtney Cavinff803ed2011-12-11 23:38:27 -0800182config 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
Heiko Stübner3bfd5c52011-11-29 11:04:09 -0800193config 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
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400207config 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
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500219config INPUT_COBALT_BTNS
220 tristate "Cobalt button interface"
221 depends on MIPS_COBALT
Dmitry Torokhov3d29cdf2007-04-29 23:43:06 -0400222 select INPUT_POLLDEV
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500223 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
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500229config INPUT_WISTRON_BTNS
230 tristate "x86 Wistron laptop button interface"
Andrew Mortone9fb0282005-11-20 00:50:21 -0500231 depends on X86 && !X86_64
Dmitry Torokhovc2554c92007-05-22 23:48:39 -0400232 select INPUT_POLLDEV
Dmitry Torokhove97af4c2009-12-04 10:22:24 -0800233 select INPUT_SPARSEKMAP
Eric Piel389679d2007-05-21 00:46:31 -0400234 select NEW_LEDS
235 select LEDS_CLASS
Geert Uytterhoeven928923c2007-08-22 14:01:36 -0700236 select CHECK_SIGNATURE
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500237 help
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200238 Say Y here for support of Wistron laptop button interfaces, used on
Eric Piel389679d2007-05-21 00:46:31 -0400239 laptops of various brands, including Acer and Fujitsu-Siemens. If
Matt LaPlante01dd2fb2007-10-20 01:34:40 +0200240 available, mail and wifi LEDs will be controllable via /sys/class/leds.
Dmitry Torokhov5fc146802005-11-20 00:50:06 -0500241
242 To compile this driver as a module, choose M here: the module will
243 be called wistron_btns.
244
Jaya Kumar31ea7ff2007-02-10 01:29:00 -0500245config 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
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400255config INPUT_ATI_REMOTE2
256 tristate "ATI / Philips USB RF remote control"
Al Viro7a86ede2007-05-15 20:36:20 +0100257 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400258 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
270config INPUT_KEYSPAN_REMOTE
271 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
272 depends on EXPERIMENTAL
Al Viro7a86ede2007-05-15 20:36:20 +0100273 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400274 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.
282
283 To compile this driver as a module, choose M here: the module will
284 be called keyspan_remote.
285
Chris Hudsone8e70d82011-07-06 18:36:51 -0700286config 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
296config 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
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400303config INPUT_POWERMATE
304 tristate "Griffin PowerMate and Contour Jog support"
Al Viro7a86ede2007-05-15 20:36:20 +0100305 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400306 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/>.
Alessandro Zummo01387952006-01-29 21:50:40 -0500315
316 To compile this driver as a module, choose M here: the
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400317 module will be called powermate.
318
319config INPUT_YEALINK
320 tristate "Yealink usb-p1k voip phone"
Adrian Bunk247537b2007-09-26 20:02:52 +0200321 depends on EXPERIMENTAL
Al Viro7a86ede2007-05-15 20:36:20 +0100322 depends on USB_ARCH_HAS_HCD
Dmitry Torokhovba0acb52007-05-07 17:31:32 -0400323 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.
Alessandro Zummo01387952006-01-29 21:50:40 -0500334
Alfred E. Heggestadc04148f2008-08-08 11:49:08 -0400335config 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
Felipe Balbi68d8bf02009-04-19 23:07:50 -0700348config 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
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800358config INPUT_TWL4030_VIBRA
359 tristate "Support for TWL4030 Vibrator"
360 depends on TWL4030_CORE
Peter Ujfalusi57fe7252011-05-31 12:02:49 +0300361 select MFD_TWL4030_AUDIO
Jari Vanhala3dd1b392010-03-09 00:29:46 -0800362 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
Misael Lopez Cruzcc697d382011-05-01 03:51:24 -0500369config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700380config 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
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400389config INPUT_SGI_BTNS
390 tristate "SGI Indy/O2 volume button interface"
391 depends on SGI_IP22 || SGI_IP32
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400392 select INPUT_POLLDEV
393 help
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400394 Say Y here if you want to support SGI Indy/O2 volume button interface.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400395
396 To compile this driver as a module, choose M here: the
Thomas Bogendoerfer48ad88b2008-07-19 00:14:26 -0400397 module will be called sgi_btns.
Thomas Bogendoerfer3bee2a02008-07-07 09:07:31 -0400398
Linus Torvalds1da177e2005-04-16 15:20:36 -0700399config HP_SDC_RTC
Yoichi Yuasabebb8a22007-02-18 01:50:18 -0500400 tristate "HP SDC Real Time Clock"
Alexander Beregalovd061ebd2009-04-11 16:55:41 -0700401 depends on (GSC || HP300) && SERIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700402 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
Balaji Rao1851b062009-01-09 01:50:58 +0100407config 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
Bryan Wub91c4be2010-03-19 22:18:15 -0700414config INPUT_PCF8574
415 tristate "PCF8574 Keypad input device"
416 depends on I2C && EXPERIMENTAL
417 help
Masanari Iida393f9ff2012-01-31 00:07:33 -0800418 Say Y here if you want to support a keypad connected via I2C
Bryan Wub91c4be2010-03-19 22:18:15 -0700419 with a PCF8574.
420
421 To compile this driver as a module, choose M here: the
422 module will be called pcf8574_keypad.
423
Lars-Peter Clausene22739d2010-07-14 00:25:21 -0700424config 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
Daniel Mack73969ff2009-03-04 23:27:14 -0800435config 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.
Alessio Igor Bogani492d0f92009-05-21 19:54:33 +0200440 Check file:Documentation/input/rotary-encoder.txt for more
Daniel Mack73969ff2009-03-04 23:27:14 -0800441 information.
442
443 To compile this driver as a module, choose M here: the
444 module will be called rotary_encoder.
445
Phil Sutterd9bdffd2009-03-04 23:27:15 -0800446config 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
David Brownelleb990b52009-04-23 19:25:29 -0700458config INPUT_DM355EVM
459 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
460 depends on MFD_DM355EVM_MSP
Dmitry Torokhov66040722009-12-04 10:22:25 -0800461 select INPUT_SPARSEKMAP
David Brownelleb990b52009-04-23 19:25:29 -0700462 help
463 Supports the pushbuttons and IR remote used with
464 the DM355 EVM board.
465
466 To compile this driver as a module, choose M here: the
467 module will be called dm355evm_keys.
Michael Hennerich48329582009-07-22 21:51:34 -0700468
469config INPUT_BFIN_ROTARY
470 tristate "Blackfin Rotary support"
471 depends on BF54x || BF52x
472 help
473 Say Y here if you want to use the Blackfin Rotary.
474
475 To compile this driver as a module, choose M here: the
476 module will be called bfin-rotary.
477
Mark Brown0c73b992009-09-15 12:07:12 +0200478config INPUT_WM831X_ON
479 tristate "WM831X ON pin"
480 depends on MFD_WM831X
481 help
482 Support the ON pin of WM831X PMICs as an input device
483 reporting power button status.
484
485 To compile this driver as a module, choose M here: the module
486 will be called wm831x_on.
487
Daniel Ribeirod0a82132009-08-10 20:27:48 +0200488config INPUT_PCAP
489 tristate "Motorola EZX PCAP misc input events"
490 depends on EZX_PCAP
491 help
492 Say Y here if you want to use Power key and Headphone button
493 on Motorola EZX phones.
494
495 To compile this driver as a module, choose M here: the
496 module will be called pcap_keys.
497
Michael Henneriche27c7292010-06-25 08:44:10 -0700498config INPUT_ADXL34X
499 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
500 default n
501 help
502 Say Y here if you have a Accelerometer interface using the
503 ADXL345/6 controller, and your board-specific initialization
504 code includes that in its table of devices.
505
506 This driver can use either I2C or SPI communication to the
507 ADXL345/6 controller. Select the appropriate method for
508 your system.
509
510 If unsure, say N (but it's safe to say "Y").
511
512 To compile this driver as a module, choose M here: the
513 module will be called adxl34x.
514
515config INPUT_ADXL34X_I2C
516 tristate "support I2C bus connection"
517 depends on INPUT_ADXL34X && I2C
518 default y
519 help
520 Say Y here if you have ADXL345/6 hooked to an I2C bus.
521
522 To compile this driver as a module, choose M here: the
523 module will be called adxl34x-i2c.
524
525config INPUT_ADXL34X_SPI
526 tristate "support SPI bus connection"
527 depends on INPUT_ADXL34X && SPI
528 default y
529 help
530 Say Y here if you have ADXL345/6 hooked to a SPI bus.
531
532 To compile this driver as a module, choose M here: the
533 module will be called adxl34x-spi.
534
Hemanth Vb029ffa2010-11-30 23:03:54 -0800535config INPUT_CMA3000
536 tristate "VTI CMA3000 Tri-axis accelerometer"
537 help
538 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
539 driver
540
541 This driver currently only supports I2C interface to the
542 controller. Also select the I2C method.
543
544 If unsure, say N
545
546 To compile this driver as a module, choose M here: the
547 module will be called cma3000_d0x.
548
549config INPUT_CMA3000_I2C
550 tristate "Support I2C bus connection"
551 depends on INPUT_CMA3000 && I2C
552 help
553 Say Y here if you want to use VTI CMA3000_D0x Accelerometer
554 through I2C interface.
555
556 To compile this driver as a module, choose M here: the
557 module will be called cma3000_d0x_i2c.
558
Dmitry Torokhov49851ca2011-03-16 22:56:03 -0700559config INPUT_XEN_KBDDEV_FRONTEND
560 tristate "Xen virtual keyboard and mouse support"
561 depends on XEN_FBDEV_FRONTEND
562 default y
563 select XEN_XENBUS_FRONTEND
564 help
565 This driver implements the front-end of the Xen virtual
566 keyboard and mouse device driver. It communicates with a back-end
567 in another domain.
568
569 To compile this driver as a module, choose M here: the
570 module will be called xen-kbdfront.
571
Linus Torvalds1da177e2005-04-16 15:20:36 -0700572endif