2 # Input misc drivers configuration
5 bool "Miscellaneous devices"
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.
15 config INPUT_88PM860X_ONKEY
16 tristate "88PM860x ONKEY support"
17 depends on MFD_88PM860X
19 Support the ONKEY of Marvell 88PM860x PMICs as an input device
20 reporting power button status.
22 To compile this driver as a module, choose M here: the module
23 will be called 88pm860x_onkey.
26 tristate "PC Speaker support"
27 depends on PCSPKR_PLATFORM
29 Say Y here if you want the standard PC Speaker to be used for
34 To compile this driver as a module, choose M here: the
35 module will be called pcspkr.
37 config INPUT_SPARCSPKR
38 tristate "SPARC Speaker support"
39 depends on PCI && SPARC64
41 Say Y here if you want the standard Speaker on Sparc PCI systems
42 to be used for bells and whistles.
46 To compile this driver as a module, choose M here: the
47 module will be called sparcspkr.
49 config INPUT_M68K_BEEP
50 tristate "M68k Beeper support"
54 tristate "Fujitsu Lifebook Application Panel buttons"
55 depends on X86 && I2C && LEDS_CLASS
57 select CHECK_SIGNATURE
59 Say Y here for support of the Application Panel buttons, used on
60 Fujitsu Lifebook. These are attached to the mainboard through
61 an SMBus interface managed by the I2C Intel ICH (i801) driver,
62 which you should also build for this kernel.
64 To compile this driver as a module, choose M here: the module will
67 config INPUT_IXP4XX_BEEPER
68 tristate "IXP4XX Beeper support"
69 depends on ARCH_IXP4XX
71 If you say yes here, you can connect a beeper to the
72 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
76 To compile this driver as a module, choose M here: the
77 module will be called ixp4xx-beeper.
79 config INPUT_COBALT_BTNS
80 tristate "Cobalt button interface"
81 depends on MIPS_COBALT
84 Say Y here if you want to support MIPS Cobalt button interface.
86 To compile this driver as a module, choose M here: the
87 module will be called cobalt_btns.
89 config INPUT_WISTRON_BTNS
90 tristate "x86 Wistron laptop button interface"
91 depends on X86 && !X86_64
93 select INPUT_SPARSEKMAP
96 select CHECK_SIGNATURE
98 Say Y here for support of Wistron laptop button interfaces, used on
99 laptops of various brands, including Acer and Fujitsu-Siemens. If
100 available, mail and wifi LEDs will be controllable via /sys/class/leds.
102 To compile this driver as a module, choose M here: the module will
103 be called wistron_btns.
105 config INPUT_ATLAS_BTNS
106 tristate "x86 Atlas button interface"
107 depends on X86 && ACPI
109 Say Y here for support of Atlas wallmount touchscreen buttons.
110 The events will show up as scancodes F1 through F9 via evdev.
112 To compile this driver as a module, choose M here: the module will
113 be called atlas_btns.
115 config INPUT_ATI_REMOTE
116 tristate "ATI / X10 USB RF remote control"
117 depends on USB_ARCH_HAS_HCD
120 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
121 These are RF remotes with USB receivers.
122 The ATI remote comes with many of ATI's All-In-Wonder video cards.
123 The X10 "Lola" remote is available at:
124 <http://www.x10.com/products/lola_sg1.htm>
125 This driver provides mouse pointer, left and right mouse buttons,
126 and maps all the other remote buttons to keypress events.
128 To compile this driver as a module, choose M here: the module will be
131 config INPUT_ATI_REMOTE2
132 tristate "ATI / Philips USB RF remote control"
133 depends on USB_ARCH_HAS_HCD
136 Say Y here if you want to use an ATI or Philips USB RF remote control.
137 These are RF remotes with USB receivers.
138 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
139 and is also available as a separate product.
140 This driver provides mouse pointer, left and right mouse buttons,
141 and maps all the other remote buttons to keypress events.
143 To compile this driver as a module, choose M here: the module will be
146 config INPUT_KEYSPAN_REMOTE
147 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
148 depends on EXPERIMENTAL
149 depends on USB_ARCH_HAS_HCD
152 Say Y here if you want to use a Keyspan DMR USB remote control.
153 Currently only the UIA-11 type of receiver has been tested. The tag
154 on the receiver that connects to the USB port should have a P/N that
155 will tell you what type of DMR you have. The UIA-10 type is not
156 supported at this time. This driver maps all buttons to keypress
159 To compile this driver as a module, choose M here: the module will
160 be called keyspan_remote.
162 config INPUT_POWERMATE
163 tristate "Griffin PowerMate and Contour Jog support"
164 depends on USB_ARCH_HAS_HCD
167 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
168 These are aluminum dials which can measure clockwise and anticlockwise
169 rotation. The dial also acts as a pushbutton. The base contains an LED
170 which can be instructed to pulse or to switch to a particular intensity.
172 You can download userspace tools from
173 <http://sowerbutts.com/powermate/>.
175 To compile this driver as a module, choose M here: the
176 module will be called powermate.
179 tristate "Yealink usb-p1k voip phone"
180 depends on EXPERIMENTAL
181 depends on USB_ARCH_HAS_HCD
184 Say Y here if you want to enable keyboard and LCD functions of the
185 Yealink usb-p1k usb phones. The audio part is enabled by the generic
186 usb sound driver, so you might want to enable that as well.
188 For information about how to use these additional functions, see
189 <file:Documentation/input/yealink.txt>.
191 To compile this driver as a module, choose M here: the module will be
195 tristate "C-Media CM109 USB I/O Controller"
196 depends on EXPERIMENTAL
197 depends on USB_ARCH_HAS_HCD
200 Say Y here if you want to enable keyboard and buzzer functions of the
201 C-Media CM109 usb phones. The audio part is enabled by the generic
202 usb sound driver, so you might want to enable that as well.
204 To compile this driver as a module, choose M here: the module will be
207 config INPUT_TWL4030_PWRBUTTON
208 tristate "TWL4030 Power button Driver"
209 depends on TWL4030_CORE
211 Say Y here if you want to enable power key reporting via the
212 TWL4030 family of chips.
214 To compile this driver as a module, choose M here. The module will
215 be called twl4030_pwrbutton.
217 config INPUT_TWL4030_VIBRA
218 tristate "Support for TWL4030 Vibrator"
219 depends on TWL4030_CORE
221 select INPUT_FF_MEMLESS
223 This option enables support for TWL4030 Vibrator Driver.
225 To compile this driver as a module, choose M here. The module will
226 be called twl4030_vibra.
229 tristate "User level driver support"
231 Say Y here if you want to support user level drivers for input
232 subsystem accessible under char device 10:223 - /dev/input/uinput.
234 To compile this driver as a module, choose M here: the
235 module will be called uinput.
237 config INPUT_SGI_BTNS
238 tristate "SGI Indy/O2 volume button interface"
239 depends on SGI_IP22 || SGI_IP32
242 Say Y here if you want to support SGI Indy/O2 volume button interface.
244 To compile this driver as a module, choose M here: the
245 module will be called sgi_btns.
247 config INPUT_WINBOND_CIR
248 tristate "Winbond IR remote control"
249 depends on X86 && PNP
255 Say Y here if you want to use the IR remote functionality found
256 in some Winbond SuperI/O chips. Currently only the WPCD376I
257 chip is supported (included in some Intel Media series motherboards).
259 IR Receive and wake-on-IR from suspend and power-off is currently
262 To compile this driver as a module, choose M here: the module will be
266 tristate "HP SDC Real Time Clock"
267 depends on (GSC || HP300) && SERIO
270 Say Y here if you want to support the built-in real time clock
271 of the HP SDC controller.
273 config INPUT_PCF50633_PMU
274 tristate "PCF50633 PMU events"
275 depends on MFD_PCF50633
277 Say Y to include support for delivering PMU events via input
278 layer on NXP PCF50633.
280 config INPUT_GPIO_ROTARY_ENCODER
281 tristate "Rotary encoders connected to GPIO pins"
282 depends on GPIOLIB && GENERIC_GPIO
284 Say Y here to add support for rotary encoders connected to GPIO lines.
285 Check file:Documentation/input/rotary-encoder.txt for more
288 To compile this driver as a module, choose M here: the
289 module will be called rotary_encoder.
291 config INPUT_RB532_BUTTON
292 tristate "Mikrotik Routerboard 532 button interface"
293 depends on MIKROTIK_RB532
294 depends on GPIOLIB && GENERIC_GPIO
297 Say Y here if you want support for the S1 button built into
298 Mikrotik's Routerboard 532.
300 To compile this driver as a module, choose M here: the
301 module will be called rb532_button.
303 config INPUT_DM355EVM
304 tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
305 depends on MFD_DM355EVM_MSP
306 select INPUT_SPARSEKMAP
308 Supports the pushbuttons and IR remote used with
311 To compile this driver as a module, choose M here: the
312 module will be called dm355evm_keys.
314 config INPUT_BFIN_ROTARY
315 tristate "Blackfin Rotary support"
316 depends on BF54x || BF52x
318 Say Y here if you want to use the Blackfin Rotary.
320 To compile this driver as a module, choose M here: the
321 module will be called bfin-rotary.
323 config INPUT_WM831X_ON
324 tristate "WM831X ON pin"
325 depends on MFD_WM831X
327 Support the ON pin of WM831X PMICs as an input device
328 reporting power button status.
330 To compile this driver as a module, choose M here: the module
331 will be called wm831x_on.
334 tristate "Motorola EZX PCAP misc input events"
337 Say Y here if you want to use Power key and Headphone button
338 on Motorola EZX phones.
340 To compile this driver as a module, choose M here: the
341 module will be called pcap_keys.