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 ALPHA || X86 || MIPS || PPC_PREP || PPC_CHRP || PPC_PSERIES 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_IXP4XX_BEEPER 44 tristate "IXP4XX Beeper support" 45 depends on ARCH_IXP4XX 46 help 47 If you say yes here, you can connect a beeper to the 48 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 49 50 If unsure, say Y. 51 52 To compile this driver as a module, choose M here: the 53 module will be called ixp4xx-beeper. 54 55config INPUT_COBALT_BTNS 56 tristate "Cobalt button interface" 57 depends on MIPS_COBALT 58 select INPUT_POLLDEV 59 help 60 Say Y here if you want to support MIPS Cobalt button interface. 61 62 To compile this driver as a module, choose M here: the 63 module will be called cobalt_btns. 64 65config INPUT_WISTRON_BTNS 66 tristate "x86 Wistron laptop button interface" 67 depends on X86 && !X86_64 68 help 69 Say Y here for support of Winstron laptop button interface, used on 70 laptops of various brands, including Acer and Fujitsu-Siemens. 71 72 To compile this driver as a module, choose M here: the module will 73 be called wistron_btns. 74 75config INPUT_ATLAS_BTNS 76 tristate "x86 Atlas button interface" 77 depends on X86 && ACPI 78 help 79 Say Y here for support of Atlas wallmount touchscreen buttons. 80 The events will show up as scancodes F1 through F9 via evdev. 81 82 To compile this driver as a module, choose M here: the module will 83 be called atlas_btns. 84 85config INPUT_ATI_REMOTE 86 tristate "ATI / X10 USB RF remote control" 87 depends on USB_ARCH_HAS_HCD 88 select USB 89 help 90 Say Y here if you want to use an ATI or X10 "Lola" USB remote control. 91 These are RF remotes with USB receivers. 92 The ATI remote comes with many of ATI's All-In-Wonder video cards. 93 The X10 "Lola" remote is available at: 94 <http://www.x10.com/products/lola_sg1.htm> 95 This driver provides mouse pointer, left and right mouse buttons, 96 and maps all the other remote buttons to keypress events. 97 98 To compile this driver as a module, choose M here: the module will be 99 called ati_remote. 100 101config INPUT_ATI_REMOTE2 102 tristate "ATI / Philips USB RF remote control" 103 depends on USB_ARCH_HAS_HCD 104 select USB 105 help 106 Say Y here if you want to use an ATI or Philips USB RF remote control. 107 These are RF remotes with USB receivers. 108 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 109 and is also available as a separate product. 110 This driver provides mouse pointer, left and right mouse buttons, 111 and maps all the other remote buttons to keypress events. 112 113 To compile this driver as a module, choose M here: the module will be 114 called ati_remote2. 115 116config INPUT_KEYSPAN_REMOTE 117 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" 118 depends on EXPERIMENTAL 119 depends on USB_ARCH_HAS_HCD 120 select USB 121 help 122 Say Y here if you want to use a Keyspan DMR USB remote control. 123 Currently only the UIA-11 type of receiver has been tested. The tag 124 on the receiver that connects to the USB port should have a P/N that 125 will tell you what type of DMR you have. The UIA-10 type is not 126 supported at this time. This driver maps all buttons to keypress 127 events. 128 129 To compile this driver as a module, choose M here: the module will 130 be called keyspan_remote. 131 132config INPUT_POWERMATE 133 tristate "Griffin PowerMate and Contour Jog support" 134 depends on USB_ARCH_HAS_HCD 135 select USB 136 help 137 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 138 These are aluminum dials which can measure clockwise and anticlockwise 139 rotation. The dial also acts as a pushbutton. The base contains an LED 140 which can be instructed to pulse or to switch to a particular intensity. 141 142 You can download userspace tools from 143 <http://sowerbutts.com/powermate/>. 144 145 To compile this driver as a module, choose M here: the 146 module will be called powermate. 147 148config INPUT_YEALINK 149 tristate "Yealink usb-p1k voip phone" 150 depends EXPERIMENTAL 151 depends on USB_ARCH_HAS_HCD 152 select USB 153 help 154 Say Y here if you want to enable keyboard and LCD functions of the 155 Yealink usb-p1k usb phones. The audio part is enabled by the generic 156 usb sound driver, so you might want to enable that as well. 157 158 For information about how to use these additional functions, see 159 <file:Documentation/input/yealink.txt>. 160 161 To compile this driver as a module, choose M here: the module will be 162 called yealink. 163 164config INPUT_UINPUT 165 tristate "User level driver support" 166 help 167 Say Y here if you want to support user level drivers for input 168 subsystem accessible under char device 10:223 - /dev/input/uinput. 169 170 To compile this driver as a module, choose M here: the 171 module will be called uinput. 172 173config HP_SDC_RTC 174 tristate "HP SDC Real Time Clock" 175 depends on GSC || HP300 176 select HP_SDC 177 help 178 Say Y here if you want to support the built-in real time clock 179 of the HP SDC controller. 180 181endif 182