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_UINPUT 197 tristate "User level driver support" 198 help 199 Say Y here if you want to support user level drivers for input 200 subsystem accessible under char device 10:223 - /dev/input/uinput. 201 202 To compile this driver as a module, choose M here: the 203 module will be called uinput. 204 205config INPUT_SGI_BTNS 206 tristate "SGI Indy/O2 volume button interface" 207 depends on SGI_IP22 || SGI_IP32 208 select INPUT_POLLDEV 209 help 210 Say Y here if you want to support SGI Indy/O2 volume button interface. 211 212 To compile this driver as a module, choose M here: the 213 module will be called sgi_btns. 214 215config HP_SDC_RTC 216 tristate "HP SDC Real Time Clock" 217 depends on (GSC || HP300) && SERIO 218 select HP_SDC 219 help 220 Say Y here if you want to support the built-in real time clock 221 of the HP SDC controller. 222 223config INPUT_PCF50633_PMU 224 tristate "PCF50633 PMU events" 225 depends on MFD_PCF50633 226 help 227 Say Y to include support for delivering PMU events via input 228 layer on NXP PCF50633. 229 230config INPUT_GPIO_ROTARY_ENCODER 231 tristate "Rotary encoders connected to GPIO pins" 232 depends on GPIOLIB && GENERIC_GPIO 233 help 234 Say Y here to add support for rotary encoders connected to GPIO lines. 235 Check file:Documentation/incput/rotary_encoder.txt for more 236 information. 237 238 To compile this driver as a module, choose M here: the 239 module will be called rotary_encoder. 240 241config INPUT_RB532_BUTTON 242 tristate "Mikrotik Routerboard 532 button interface" 243 depends on MIKROTIK_RB532 244 depends on GPIOLIB && GENERIC_GPIO 245 select INPUT_POLLDEV 246 help 247 Say Y here if you want support for the S1 button built into 248 Mikrotik's Routerboard 532. 249 250 To compile this driver as a module, choose M here: the 251 module will be called rb532_button. 252 253endif 254