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 depends on SND_PCSP=n 19 help 20 Say Y here if you want the standard PC Speaker to be used for 21 bells and whistles. 22 23 If unsure, say Y. 24 25 To compile this driver as a module, choose M here: the 26 module will be called pcspkr. 27 28config INPUT_SPARCSPKR 29 tristate "SPARC Speaker support" 30 depends on PCI && SPARC64 31 help 32 Say Y here if you want the standard Speaker on Sparc PCI systems 33 to be used for bells and whistles. 34 35 If unsure, say Y. 36 37 To compile this driver as a module, choose M here: the 38 module will be called sparcspkr. 39 40config INPUT_M68K_BEEP 41 tristate "M68k Beeper support" 42 depends on M68K 43 44config INPUT_APANEL 45 tristate "Fujitsu Lifebook Application Panel buttons" 46 depends on X86 && I2C && LEDS_CLASS 47 select INPUT_POLLDEV 48 select CHECK_SIGNATURE 49 help 50 Say Y here for support of the Application Panel buttons, used on 51 Fujitsu Lifebook. These are attached to the mainboard through 52 an SMBus interface managed by the I2C Intel ICH (i801) driver, 53 which you should also build for this kernel. 54 55 To compile this driver as a module, choose M here: the module will 56 be called apanel. 57 58config INPUT_IXP4XX_BEEPER 59 tristate "IXP4XX Beeper support" 60 depends on ARCH_IXP4XX 61 help 62 If you say yes here, you can connect a beeper to the 63 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 64 65 If unsure, say Y. 66 67 To compile this driver as a module, choose M here: the 68 module will be called ixp4xx-beeper. 69 70config INPUT_COBALT_BTNS 71 tristate "Cobalt button interface" 72 depends on MIPS_COBALT 73 select INPUT_POLLDEV 74 help 75 Say Y here if you want to support MIPS Cobalt button interface. 76 77 To compile this driver as a module, choose M here: the 78 module will be called cobalt_btns. 79 80config INPUT_WISTRON_BTNS 81 tristate "x86 Wistron laptop button interface" 82 depends on X86 && !X86_64 83 select INPUT_POLLDEV 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_UINPUT 185 tristate "User level driver support" 186 help 187 Say Y here if you want to support user level drivers for input 188 subsystem accessible under char device 10:223 - /dev/input/uinput. 189 190 To compile this driver as a module, choose M here: the 191 module will be called uinput. 192 193config HP_SDC_RTC 194 tristate "HP SDC Real Time Clock" 195 depends on GSC || HP300 196 select HP_SDC 197 help 198 Say Y here if you want to support the built-in real time clock 199 of the HP SDC controller. 200 201endif 202