2 # Input misc drivers configuration
5 bool "Miscellaneous devices"
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.
16 tristate "PC Speaker support"
17 depends on ALPHA || X86 || MIPS || PPC_PREP || PPC_CHRP || PPC_PSERIES
19 Say Y here if you want the standard PC Speaker to be used for
24 To compile this driver as a module, choose M here: the
25 module will be called pcspkr.
27 config INPUT_SPARCSPKR
28 tristate "SPARC Speaker support"
29 depends on PCI && SPARC64
31 Say Y here if you want the standard Speaker on Sparc PCI systems
32 to be used for bells and whistles.
36 To compile this driver as a module, choose M here: the
37 module will be called sparcspkr.
39 config INPUT_M68K_BEEP
40 tristate "M68k Beeper support"
44 tristate "Fujitsu Lifebook Application Panel buttons"
45 <<<<<<< HEAD:drivers/input/misc/Kconfig
49 depends on X86 && I2C && LEDS_CLASS
50 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/input/misc/Kconfig
52 select CHECK_SIGNATURE
54 Say Y here for support of the Application Panel buttons, used on
55 Fujitsu Lifebook. These are attached to the mainboard through
56 <<<<<<< HEAD:drivers/input/misc/Kconfig
57 an SMBus interface managed by the I2C Intel ICH (i801) driver.
59 an SMBus interface managed by the I2C Intel ICH (i801) driver,
60 which you should also build for this kernel.
61 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:drivers/input/misc/Kconfig
63 To compile this driver as a module, choose M here: the module will
66 config INPUT_IXP4XX_BEEPER
67 tristate "IXP4XX Beeper support"
68 depends on ARCH_IXP4XX
70 If you say yes here, you can connect a beeper to the
71 ixp4xx gpio pins. This is used by the LinkSys NSLU2.
75 To compile this driver as a module, choose M here: the
76 module will be called ixp4xx-beeper.
78 config INPUT_COBALT_BTNS
79 tristate "Cobalt button interface"
80 depends on MIPS_COBALT
83 Say Y here if you want to support MIPS Cobalt button interface.
85 To compile this driver as a module, choose M here: the
86 module will be called cobalt_btns.
88 config INPUT_WISTRON_BTNS
89 tristate "x86 Wistron laptop button interface"
90 depends on X86 && !X86_64
94 select CHECK_SIGNATURE
96 Say Y here for support of Wistron laptop button interfaces, used on
97 laptops of various brands, including Acer and Fujitsu-Siemens. If
98 available, mail and wifi LEDs will be controllable via /sys/class/leds.
100 To compile this driver as a module, choose M here: the module will
101 be called wistron_btns.
103 config INPUT_ATLAS_BTNS
104 tristate "x86 Atlas button interface"
105 depends on X86 && ACPI
107 Say Y here for support of Atlas wallmount touchscreen buttons.
108 The events will show up as scancodes F1 through F9 via evdev.
110 To compile this driver as a module, choose M here: the module will
111 be called atlas_btns.
113 config INPUT_ATI_REMOTE
114 tristate "ATI / X10 USB RF remote control"
115 depends on USB_ARCH_HAS_HCD
118 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
119 These are RF remotes with USB receivers.
120 The ATI remote comes with many of ATI's All-In-Wonder video cards.
121 The X10 "Lola" remote is available at:
122 <http://www.x10.com/products/lola_sg1.htm>
123 This driver provides mouse pointer, left and right mouse buttons,
124 and maps all the other remote buttons to keypress events.
126 To compile this driver as a module, choose M here: the module will be
129 config INPUT_ATI_REMOTE2
130 tristate "ATI / Philips USB RF remote control"
131 depends on USB_ARCH_HAS_HCD
134 Say Y here if you want to use an ATI or Philips USB RF remote control.
135 These are RF remotes with USB receivers.
136 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
137 and is also available as a separate product.
138 This driver provides mouse pointer, left and right mouse buttons,
139 and maps all the other remote buttons to keypress events.
141 To compile this driver as a module, choose M here: the module will be
144 config INPUT_KEYSPAN_REMOTE
145 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
146 depends on EXPERIMENTAL
147 depends on USB_ARCH_HAS_HCD
150 Say Y here if you want to use a Keyspan DMR USB remote control.
151 Currently only the UIA-11 type of receiver has been tested. The tag
152 on the receiver that connects to the USB port should have a P/N that
153 will tell you what type of DMR you have. The UIA-10 type is not
154 supported at this time. This driver maps all buttons to keypress
157 To compile this driver as a module, choose M here: the module will
158 be called keyspan_remote.
160 config INPUT_POWERMATE
161 tristate "Griffin PowerMate and Contour Jog support"
162 depends on USB_ARCH_HAS_HCD
165 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
166 These are aluminum dials which can measure clockwise and anticlockwise
167 rotation. The dial also acts as a pushbutton. The base contains an LED
168 which can be instructed to pulse or to switch to a particular intensity.
170 You can download userspace tools from
171 <http://sowerbutts.com/powermate/>.
173 To compile this driver as a module, choose M here: the
174 module will be called powermate.
177 tristate "Yealink usb-p1k voip phone"
178 depends on EXPERIMENTAL
179 depends on USB_ARCH_HAS_HCD
182 Say Y here if you want to enable keyboard and LCD functions of the
183 Yealink usb-p1k usb phones. The audio part is enabled by the generic
184 usb sound driver, so you might want to enable that as well.
186 For information about how to use these additional functions, see
187 <file:Documentation/input/yealink.txt>.
189 To compile this driver as a module, choose M here: the module will be
193 tristate "User level driver support"
195 Say Y here if you want to support user level drivers for input
196 subsystem accessible under char device 10:223 - /dev/input/uinput.
198 To compile this driver as a module, choose M here: the
199 module will be called uinput.
202 tristate "HP SDC Real Time Clock"
203 depends on GSC || HP300
206 Say Y here if you want to support the built-in real time clock
207 of the HP SDC controller.