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