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