1# 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 15config INPUT_PCSPKR 16 tristate "PC Speaker support" 17 depends on PCSPKR_PLATFORM 18 help 19 Say Y here if you want the standard PC Speaker to be used for 20 bells and whistles. 21 22 If unsure, say Y. 23 24 To compile this driver as a module, choose M here: the 25 module will be called pcspkr. 26 27config INPUT_SPARCSPKR 28 tristate "SPARC Speaker support" 29 depends on PCI && SPARC64 30 help 31 Say Y here if you want the standard Speaker on Sparc PCI systems 32 to be used for bells and whistles. 33 34 If unsure, say Y. 35 36 To compile this driver as a module, choose M here: the 37 module will be called sparcspkr. 38 39config INPUT_M68K_BEEP 40 tristate "M68k Beeper support" 41 depends on M68K 42 43config INPUT_APANEL 44 tristate "Fujitsu Lifebook Application Panel buttons" 45 depends on X86 && I2C && LEDS_CLASS 46 select INPUT_POLLDEV 47 select CHECK_SIGNATURE 48 help 49 Say Y here for support of the Application Panel buttons, used on 50 Fujitsu Lifebook. These are attached to the mainboard through 51 an SMBus interface managed by the I2C Intel ICH (i801) driver, 52 which you should also build for this kernel. 53 54 To compile this driver as a module, choose M here: the module will 55 be called apanel. 56 57config INPUT_IXP4XX_BEEPER 58 tristate "IXP4XX Beeper support" 59 depends on ARCH_IXP4XX 60 help 61 If you say yes here, you can connect a beeper to the 62 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 63 64 If unsure, say Y. 65 66 To compile this driver as a module, choose M here: the 67 module will be called ixp4xx-beeper. 68 69config INPUT_COBALT_BTNS 70 tristate "Cobalt button interface" 71 depends on MIPS_COBALT 72 select INPUT_POLLDEV 73 help 74 Say Y here if you want to support MIPS Cobalt button interface. 75 76 To compile this driver as a module, choose M here: the 77 module will be called cobalt_btns. 78 79config INPUT_WISTRON_BTNS 80 tristate "x86 Wistron laptop button interface" 81 depends on X86 && !X86_64 82 select INPUT_POLLDEV 83 select INPUT_SPARSEKMAP 84 select NEW_LEDS 85 select LEDS_CLASS 86 select CHECK_SIGNATURE 87 help 88 Say Y here for support of Wistron laptop button interfaces, used on 89 laptops of various brands, including Acer and Fujitsu-Siemens. If 90 available, mail and wifi LEDs will be controllable via /sys/class/leds. 91 92 To compile this driver as a module, choose M here: the module will 93 be called wistron_btns. 94 95config INPUT_ATLAS_BTNS 96 tristate "x86 Atlas button interface" 97 depends on X86 && ACPI 98 help 99 Say Y here for support of Atlas wallmount touchscreen buttons. 100 The events will show up as scancodes F1 through F9 via evdev. 101 102 To compile this driver as a module, choose M here: the module will 103 be called atlas_btns. 104 105config INPUT_ATI_REMOTE 106 tristate "ATI / X10 USB RF remote control" 107 depends on USB_ARCH_HAS_HCD 108 select USB 109 help 110 Say Y here if you want to use an ATI or X10 "Lola" USB remote control. 111 These are RF remotes with USB receivers. 112 The ATI remote comes with many of ATI's All-In-Wonder video cards. 113 The X10 "Lola" remote is available at: 114 <http://www.x10.com/products/lola_sg1.htm> 115 This driver provides mouse pointer, left and right mouse buttons, 116 and maps all the other remote buttons to keypress events. 117 118 To compile this driver as a module, choose M here: the module will be 119 called ati_remote. 120 121config INPUT_ATI_REMOTE2 122 tristate "ATI / Philips USB RF remote control" 123 depends on USB_ARCH_HAS_HCD 124 select USB 125 help 126 Say Y here if you want to use an ATI or Philips USB RF remote control. 127 These are RF remotes with USB receivers. 128 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 129 and is also available as a separate product. 130 This driver provides mouse pointer, left and right mouse buttons, 131 and maps all the other remote buttons to keypress events. 132 133 To compile this driver as a module, choose M here: the module will be 134 called ati_remote2. 135 136config INPUT_KEYSPAN_REMOTE 137 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" 138 depends on EXPERIMENTAL 139 depends on USB_ARCH_HAS_HCD 140 select USB 141 help 142 Say Y here if you want to use a Keyspan DMR USB remote control. 143 Currently only the UIA-11 type of receiver has been tested. The tag 144 on the receiver that connects to the USB port should have a P/N that 145 will tell you what type of DMR you have. The UIA-10 type is not 146 supported at this time. This driver maps all buttons to keypress 147 events. 148 149 To compile this driver as a module, choose M here: the module will 150 be called keyspan_remote. 151 152config INPUT_POWERMATE 153 tristate "Griffin PowerMate and Contour Jog support" 154 depends on USB_ARCH_HAS_HCD 155 select USB 156 help 157 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 158 These are aluminum dials which can measure clockwise and anticlockwise 159 rotation. The dial also acts as a pushbutton. The base contains an LED 160 which can be instructed to pulse or to switch to a particular intensity. 161 162 You can download userspace tools from 163 <http://sowerbutts.com/powermate/>. 164 165 To compile this driver as a module, choose M here: the 166 module will be called powermate. 167 168config INPUT_YEALINK 169 tristate "Yealink usb-p1k voip phone" 170 depends on EXPERIMENTAL 171 depends on USB_ARCH_HAS_HCD 172 select USB 173 help 174 Say Y here if you want to enable keyboard and LCD functions of the 175 Yealink usb-p1k usb phones. The audio part is enabled by the generic 176 usb sound driver, so you might want to enable that as well. 177 178 For information about how to use these additional functions, see 179 <file:Documentation/input/yealink.txt>. 180 181 To compile this driver as a module, choose M here: the module will be 182 called yealink. 183 184config INPUT_CM109 185 tristate "C-Media CM109 USB I/O Controller" 186 depends on EXPERIMENTAL 187 depends on USB_ARCH_HAS_HCD 188 select USB 189 help 190 Say Y here if you want to enable keyboard and buzzer functions of the 191 C-Media CM109 usb phones. The audio part is enabled by the generic 192 usb sound driver, so you might want to enable that as well. 193 194 To compile this driver as a module, choose M here: the module will be 195 called cm109. 196 197config INPUT_TWL4030_PWRBUTTON 198 tristate "TWL4030 Power button Driver" 199 depends on TWL4030_CORE 200 help 201 Say Y here if you want to enable power key reporting via the 202 TWL4030 family of chips. 203 204 To compile this driver as a module, choose M here. The module will 205 be called twl4030_pwrbutton. 206 207config INPUT_UINPUT 208 tristate "User level driver support" 209 help 210 Say Y here if you want to support user level drivers for input 211 subsystem accessible under char device 10:223 - /dev/input/uinput. 212 213 To compile this driver as a module, choose M here: the 214 module will be called uinput. 215 216config INPUT_SGI_BTNS 217 tristate "SGI Indy/O2 volume button interface" 218 depends on SGI_IP22 || SGI_IP32 219 select INPUT_POLLDEV 220 help 221 Say Y here if you want to support SGI Indy/O2 volume button interface. 222 223 To compile this driver as a module, choose M here: the 224 module will be called sgi_btns. 225 226config INPUT_WINBOND_CIR 227 tristate "Winbond IR remote control" 228 depends on X86 && PNP 229 select NEW_LEDS 230 select LEDS_CLASS 231 select LEDS_TRIGGERS 232 select BITREVERSE 233 help 234 Say Y here if you want to use the IR remote functionality found 235 in some Winbond SuperI/O chips. Currently only the WPCD376I 236 chip is supported (included in some Intel Media series motherboards). 237 238 IR Receive and wake-on-IR from suspend and power-off is currently 239 supported. 240 241 To compile this driver as a module, choose M here: the module will be 242 called winbond_cir. 243 244config HP_SDC_RTC 245 tristate "HP SDC Real Time Clock" 246 depends on (GSC || HP300) && SERIO 247 select HP_SDC 248 help 249 Say Y here if you want to support the built-in real time clock 250 of the HP SDC controller. 251 252config INPUT_PCF50633_PMU 253 tristate "PCF50633 PMU events" 254 depends on MFD_PCF50633 255 help 256 Say Y to include support for delivering PMU events via input 257 layer on NXP PCF50633. 258 259config INPUT_GPIO_ROTARY_ENCODER 260 tristate "Rotary encoders connected to GPIO pins" 261 depends on GPIOLIB && GENERIC_GPIO 262 help 263 Say Y here to add support for rotary encoders connected to GPIO lines. 264 Check file:Documentation/input/rotary-encoder.txt for more 265 information. 266 267 To compile this driver as a module, choose M here: the 268 module will be called rotary_encoder. 269 270config INPUT_RB532_BUTTON 271 tristate "Mikrotik Routerboard 532 button interface" 272 depends on MIKROTIK_RB532 273 depends on GPIOLIB && GENERIC_GPIO 274 select INPUT_POLLDEV 275 help 276 Say Y here if you want support for the S1 button built into 277 Mikrotik's Routerboard 532. 278 279 To compile this driver as a module, choose M here: the 280 module will be called rb532_button. 281 282config INPUT_DM355EVM 283 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 284 depends on MFD_DM355EVM_MSP 285 select INPUT_SPARSEKMAP 286 help 287 Supports the pushbuttons and IR remote used with 288 the DM355 EVM board. 289 290 To compile this driver as a module, choose M here: the 291 module will be called dm355evm_keys. 292 293config INPUT_BFIN_ROTARY 294 tristate "Blackfin Rotary support" 295 depends on BF54x || BF52x 296 help 297 Say Y here if you want to use the Blackfin Rotary. 298 299 To compile this driver as a module, choose M here: the 300 module will be called bfin-rotary. 301 302config INPUT_WM831X_ON 303 tristate "WM831X ON pin" 304 depends on MFD_WM831X 305 help 306 Support the ON pin of WM831X PMICs as an input device 307 reporting power button status. 308 309 To compile this driver as a module, choose M here: the module 310 will be called wm831x_on. 311 312config INPUT_PCAP 313 tristate "Motorola EZX PCAP misc input events" 314 depends on EZX_PCAP 315 help 316 Say Y here if you want to use Power key and Headphone button 317 on Motorola EZX phones. 318 319 To compile this driver as a module, choose M here: the 320 module will be called pcap_keys. 321 322endif 323