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