1 # SPDX-License-Identifier: GPL-2.0-only
3 # Input core configuration
6 tristate "Serial I/O support"
9 Say Yes here if you have any input device that uses serial I/O to
10 communicate with the system. This includes the
11 * standard AT keyboard and PS/2 mouse *
12 as well as serial mice, Sun keyboards, some joysticks and 6dof
17 To compile this driver as a module, choose M here: the
18 module will be called serio.
20 config ARCH_MIGHT_HAVE_PC_SERIO
23 Select this config option from the architecture Kconfig if
24 the architecture might use a PC serio device (i8042) to
25 communicate with keyboard, mouse, etc.
30 tristate "i8042 PC Keyboard controller"
32 depends on ARCH_MIGHT_HAVE_PC_SERIO
34 i8042 is the chip over which the standard AT keyboard and PS/2
35 mouse are connected to the computer. If you use these devices,
36 you'll need to say Y here.
40 To compile this driver as a module, choose M here: the
41 module will be called i8042.
44 tristate "Serial port line discipline"
48 Say Y here if you plan to use an input device (mouse, joystick,
49 tablet, 6dof) that communicates over the RS232 serial (COM) port.
51 More information is available: <file:Documentation/input/input.rst>
55 To compile this driver as a module, choose M here: the
56 module will be called serport.
59 tristate "ct82c710 Aux port controller"
62 Say Y here if you have a Texas Instruments TravelMate notebook
63 equipped with the ct82c710 chip and want to use a mouse connected
68 To compile this driver as a module, choose M here: the
69 module will be called ct82c710.
72 tristate "Q40 keyboard controller"
76 tristate "Parallel port keyboard adapter"
79 Say Y here if you built a simple parallel port adapter to attach
80 an additional AT keyboard, XT keyboard or PS/2 mouse.
82 More information is available: <file:Documentation/input/input.rst>
86 To compile this driver as a module, choose M here: the
87 module will be called parkbd.
90 tristate "Acorn RiscPC keyboard controller"
94 Say Y here if you have the Acorn RiscPC and want to use an AT
95 keyboard connected to its keyboard controller.
97 To compile this driver as a module, choose M here: the
98 module will be called rpckbd.
101 tristate "AMBA KMI keyboard controller"
105 tristate "Intel SA1111 keyboard controller"
109 tristate "HP GSC PS/2 keyboard and PS/2 mouse controller"
113 This driver provides support for the PS/2 ports on PA-RISC machines
114 over which HP PS/2 keyboards and PS/2 mice may be connected.
115 If you use these devices, you'll need to say Y here.
117 It's safe to enable this driver, so if unsure, say Y.
119 To compile this driver as a module, choose M here: the
120 module will be called gscps2.
123 tristate "HP System Device Controller i8042 Support"
124 depends on (GSC || HP300) && SERIO
127 This option enables support for the "System Device
128 Controller", an i8042 carrying microcode to manage a
129 few miscellaneous devices on some Hewlett Packard systems.
130 The SDC itself contains a 10ms resolution timer/clock capable
131 of delivering interrupts on a periodic and one-shot basis.
132 The SDC may also be connected to a battery-backed real-time
133 clock, a basic audio waveform generator, and an HP-HIL Master
134 Link Controller serving up to seven input devices.
136 By itself this option is rather useless, but enabling it will
137 enable selection of drivers for the abovementioned devices.
138 It is, however, incompatible with the old, reliable HIL keyboard
139 driver, and the new HIL driver is experimental, so if you plan
140 to use a HIL keyboard as your primary keyboard, you may wish
141 to keep using that driver until the new HIL drivers have had
145 tristate "HIL MLC Support (needed for HIL input devices)"
149 tristate "PCI PS/2 keyboard and PS/2 mouse controller"
152 Say Y here if you have a Mobility Docking station with PS/2
153 keyboard and mice ports.
155 To compile this driver as a module, choose M here: the
156 module will be called pcips2.
159 tristate "SGI O2 MACE PS/2 controller"
162 Say Y here if you have SGI O2 workstation and want to use its
165 To compile this driver as a module, choose M here: the
166 module will be called maceps2.
168 config SERIO_SGI_IOC3
169 tristate "SGI IOC3 PS/2 controller"
170 depends on SGI_MFD_IOC3
172 Say Y here if you have an SGI Onyx2, SGI Octane or IOC3 PCI card
173 and you want to attach and use a keyboard, mouse, or both.
175 To compile this driver as a module, choose M here: the
176 module will be called ioc3kbd.
179 tristate "PS/2 driver library"
180 depends on SERIO_I8042 || SERIO_I8042=n
182 Say Y here if you are using a driver for device connected
183 to a PS/2 port, such as PS/2 mouse or standard AT keyboard.
185 To compile this driver as a module, choose M here: the
186 module will be called libps2.
189 tristate "Raw access to serio ports"
191 Say Y here if you want to have raw access to serio ports, such as
192 AUX ports on i8042 keyboard controller. Each serio port that is
193 bound to this driver will be accessible via a char device with
194 major 10 and dynamically allocated minor. The driver will try
195 allocating minor 1 (that historically corresponds to /dev/psaux)
196 first. To bind this driver to a serio port use sysfs interface:
198 echo -n "serio_raw" > /sys/bus/serio/devices/serioX/drvctl
200 To compile this driver as a module, choose M here: the
201 module will be called serio_raw.
203 config SERIO_XILINX_XPS_PS2
204 tristate "Xilinx XPS PS/2 Controller Support"
205 depends on PPC || MICROBLAZE
207 This driver supports XPS PS/2 IP from the Xilinx EDK on
210 To compile this driver as a module, choose M here: the
211 module will be called xilinx_ps2.
213 config SERIO_ALTERA_PS2
214 tristate "Altera UP PS/2 controller"
217 Say Y here if you have Altera University Program PS/2 ports.
219 To compile this driver as a module, choose M here: the
220 module will be called altera_ps2.
222 config SERIO_AMS_DELTA
223 tristate "Amstrad Delta (E3) mailboard support"
224 depends on MACH_AMS_DELTA
227 Say Y here if you have an E3 and want to use its mailboard,
228 or any standard AT keyboard connected to the mailboard port.
230 When used for the E3 mailboard, a non-standard key table
231 must be loaded from userspace, possibly using udev extras
232 provided keymap helper utility.
234 To compile this driver as a module, choose M here;
235 the module will be called ams_delta_serio.
238 tristate "TQC PS/2 multiplexer"
240 Say Y here if you have the PS/2 line multiplexer like the one
241 present on TQC boards.
243 To compile this driver as a module, choose M here: the
244 module will be called ps2mult.
247 tristate "ARC PS/2 support"
250 Say Y here if you have an ARC FPGA platform with a PS/2
253 To compile this driver as a module, choose M here; the module
254 will be called arc_ps2.
257 tristate "GRLIB APBPS2 PS/2 keyboard/mouse controller"
260 Say Y here if you want support for GRLIB APBPS2 peripherals used
261 to connect to PS/2 keyboard and/or mouse.
263 To compile this driver as a module, choose M here: the module will
266 config SERIO_OLPC_APSP
267 tristate "OLPC AP-SP input support"
268 depends on ARCH_MMP || COMPILE_TEST
270 Say Y here if you want support for the keyboard and touchpad included
271 in the OLPC XO-1.75 and XO-4 laptops.
273 To compile this driver as a module, choose M here: the module will
276 config HYPERV_KEYBOARD
277 tristate "Microsoft Synthetic Keyboard driver"
281 Select this option to enable the Hyper-V Keyboard driver.
283 To compile this driver as a module, choose M here: the module will
284 be called hyperv_keyboard.
286 config SERIO_SUN4I_PS2
287 tristate "Allwinner A10 PS/2 controller support"
288 depends on ARCH_SUNXI || COMPILE_TEST
290 This selects support for the PS/2 Host Controller on
293 To compile this driver as a module, choose M here: the
294 module will be called sun4i-ps2.
296 config SERIO_GPIO_PS2
297 tristate "GPIO PS/2 bit banging driver"
300 Say Y here if you want PS/2 bit banging support via GPIO.
302 To compile this driver as a module, choose M here: the
303 module will be called ps2-gpio.
305 If you are unsure, say N.
308 tristate "User space serio port driver support"
310 Say Y here if you want to support user level drivers for serio
311 subsystem accessible under char device 10:240 - /dev/userio. Using
312 this facility userspace programs can implement serio ports that
313 will be used by the standard in-kernel serio consumer drivers,
314 such as psmouse and atkbd.
316 To compile this driver as a module, choose M here: the module will be
319 If you are unsure, say N.