2 # Mouse driver configuration
8 Say Y here, and a list of supported mice will be displayed.
9 This option doesn't affect the kernel.
20 select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO
21 select SERIO_GSCPS2 if GSC
23 Say Y here if you have a PS/2 mouse connected to your system. This
24 includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
25 mice with wheels and extra buttons, Microsoft, Logitech or Genius
28 Synaptics, ALPS or Elantech TouchPad users might be interested
29 in a specialized Xorg/XFree86 driver at:
30 <http://w1.894.telia.com/~u89404340/touchpad/index.html>
31 and a new version of GPM at:
32 <http://www.geocities.com/dt_or/gpm/gpm.html>
33 <http://xorg.freedesktop.org/archive/individual/driver/>
34 to take advantage of the advanced features of the touchpad.
38 To compile this driver as a module, choose M here: the
39 module will be called psmouse.
42 bool "ALPS PS/2 mouse protocol extension" if EXPERT
46 Say Y here if you have an ALPS PS/2 touchpad connected to
52 bool "BYD PS/2 mouse protocol extension" if EXPERT
56 Say Y here if you have a BYD PS/2 touchpad connected to
61 config MOUSE_PS2_LOGIPS2PP
62 bool "Logitech PS/2++ mouse protocol extension" if EXPERT
66 Say Y here if you have a Logitech PS/2++ mouse connected to
71 config MOUSE_PS2_SYNAPTICS
72 bool "Synaptics PS/2 mouse protocol extension" if EXPERT
76 Say Y here if you have a Synaptics PS/2 TouchPad connected to
81 config MOUSE_PS2_CYPRESS
82 bool "Cypress PS/2 mouse protocol extension" if EXPERT
86 Say Y here if you have a Cypress PS/2 Trackpad connected to
91 config MOUSE_PS2_LIFEBOOK
92 bool "Fujitsu Lifebook PS/2 mouse protocol extension" if EXPERT
94 depends on MOUSE_PS2 && X86 && DMI
96 Say Y here if you have a Fujitsu B-series Lifebook PS/2
97 TouchScreen connected to your system.
101 config MOUSE_PS2_TRACKPOINT
102 bool "IBM Trackpoint PS/2 mouse protocol extension" if EXPERT
106 Say Y here if you have an IBM Trackpoint PS/2 mouse connected
111 config MOUSE_PS2_ELANTECH
112 bool "Elantech PS/2 protocol extension"
115 Say Y here if you have an Elantech PS/2 touchpad connected
118 This driver exposes some configuration registers via sysfs
119 entries. For further information,
120 see <file:Documentation/input/elantech.txt>.
124 config MOUSE_PS2_SENTELIC
125 bool "Sentelic Finger Sensing Pad PS/2 protocol extension"
128 Say Y here if you have a laptop (such as MSI WIND Netbook)
129 with Sentelic Finger Sensing Pad touchpad.
133 config MOUSE_PS2_TOUCHKIT
134 bool "eGalax TouchKit PS/2 protocol extension"
137 Say Y here if you have an eGalax TouchKit PS/2 touchscreen
138 connected to your system.
142 config MOUSE_PS2_OLPC
143 bool "OLPC PS/2 mouse protocol extension"
144 depends on MOUSE_PS2 && OLPC
146 Say Y here if you have an OLPC XO-1 laptop (with built-in
147 PS/2 touchpad/tablet device). The manufacturer calls the
152 config MOUSE_PS2_FOCALTECH
153 bool "FocalTech PS/2 mouse protocol extension" if EXPERT
157 Say Y here if you have a FocalTech PS/2 TouchPad connected to
162 config MOUSE_PS2_VMMOUSE
163 bool "Virtual mouse (vmmouse)"
164 depends on MOUSE_PS2 && X86 && HYPERVISOR_GUEST
166 Say Y here if you are running under control of VMware hypervisor
167 (ESXi, Workstation or Fusion). Also make sure that when you enable
168 this option, you remove the xf86-input-vmmouse user-space driver
169 or upgrade it to at least xf86-input-vmmouse 13.1.0, which doesn't
170 load in the presence of an in-kernel vmmouse driver.
175 tristate "Serial mouse"
178 Say Y here if you have a serial (RS-232, COM port) mouse connected
179 to your system. This includes Sun, MouseSystems, Microsoft,
180 Logitech and all other compatible serial mice.
184 To compile this driver as a module, choose M here: the
185 module will be called sermouse.
187 config MOUSE_APPLETOUCH
188 tristate "Apple USB Touchpad support"
189 depends on USB_ARCH_HAS_HCD
192 Say Y here if you want to use an Apple USB Touchpad.
194 These are the touchpads that can be found on post-February 2005
195 Apple Powerbooks (prior models have a Synaptics touchpad connected
198 This driver provides a basic mouse driver but can be interfaced
199 with the synaptics X11 driver to provide acceleration and
202 For further information, see
203 <file:Documentation/input/appletouch.txt>.
205 To compile this driver as a module, choose M here: the
206 module will be called appletouch.
209 tristate "Apple USB BCM5974 Multitouch trackpad support"
210 depends on USB_ARCH_HAS_HCD
213 Say Y here if you have an Apple USB BCM5974 Multitouch
216 The BCM5974 is the multitouch trackpad found in the Macbook
217 Air (JAN2008) and Macbook Pro Penryn (FEB2008) laptops.
219 It is also found in the IPhone (2007) and Ipod Touch (2008).
221 This driver provides multitouch functionality together with
222 the synaptics X11 driver.
224 The interface is currently identical to the appletouch interface,
225 for further information, see
226 <file:Documentation/input/appletouch.txt>.
228 To compile this driver as a module, choose M here: the
229 module will be called bcm5974.
232 tristate "Cypress APA I2C Trackpad support"
236 This driver adds support for Cypress All Points Addressable (APA)
237 I2C Trackpads, including the ones used in 2012 Samsung Chromebooks.
239 Say Y here if you have a Cypress APA I2C Trackpad.
241 To compile this driver as a module, choose M here: the module will be
244 config MOUSE_ELAN_I2C
245 tristate "ELAN I2C Touchpad support"
248 This driver adds support for Elan I2C/SMbus Trackpads.
250 Say Y here if you have a ELAN I2C/SMbus Touchpad.
252 To compile this driver as a module, choose M here: the module will be
255 config MOUSE_ELAN_I2C_I2C
256 bool "Enable I2C support"
257 depends on MOUSE_ELAN_I2C
260 Say Y here if Elan Touchpad in your system is connected to
261 a standard I2C controller.
265 config MOUSE_ELAN_I2C_SMBUS
266 bool "Enable SMbus support"
267 depends on MOUSE_ELAN_I2C
269 Say Y here if Elan Touchpad in your system is connected to
275 tristate "InPort/MS/ATIXL busmouse"
278 Say Y here if you have an InPort, Microsoft or ATI XL busmouse.
279 They are rather rare these days.
281 To compile this driver as a module, choose M here: the
282 module will be called inport.
285 bool "ATI XL variant"
286 depends on MOUSE_INPORT
288 Say Y here if your mouse is of the ATI XL variety.
291 tristate "Logitech busmouse"
294 Say Y here if you have a Logitech busmouse.
295 They are rather rare these days.
297 To compile this driver as a module, choose M here: the
298 module will be called logibm.
300 config MOUSE_PC110PAD
301 tristate "IBM PC110 touchpad"
304 Say Y if you have the IBM PC-110 micro-notebook and want its
307 To compile this driver as a module, choose M here: the
308 module will be called pc110pad.
311 tristate "Amiga mouse"
314 Say Y here if you have an Amiga and want its native mouse
315 supported by the kernel.
317 To compile this driver as a module, choose M here: the
318 module will be called amimouse.
321 tristate "Atari mouse"
323 select ATARI_KBD_CORE
325 Say Y here if you have an Atari and want its native mouse
326 supported by the kernel.
328 To compile this driver as a module, choose M here: the
329 module will be called atarimouse.
332 tristate "Acorn RiscPC mouse"
333 depends on ARCH_ACORN
335 Say Y here if you have the Acorn RiscPC computer and want its
336 native mouse supported.
338 To compile this driver as a module, choose M here: the
339 module will be called rpcmouse.
342 tristate "DEC VSXXX-AA/GA mouse and VSXXX-AB tablet"
345 Say Y (or M) if you want to use a DEC VSXXX-AA (hockey
346 puck) or a VSXXX-GA (rectangular) mouse. Theses mice are
347 typically used on DECstations or VAXstations, but can also
348 be used on any box capable of RS232 (with some adaptor
349 described in the source file). This driver also works with the
350 digitizer (VSXXX-AB) DEC produced.
353 tristate "GPIO mouse"
354 depends on GPIOLIB || COMPILE_TEST
357 This driver simulates a mouse on GPIO lines of various CPUs (and some
360 Say Y here if your device has buttons or a simple joystick connected
361 directly to GPIO lines. Your board-specific setup logic must also
362 provide a platform device and platform data saying which GPIOs are
365 To compile this driver as a module, choose M here: the
366 module will be called gpio_mouse.
368 config MOUSE_PXA930_TRKBALL
369 tristate "PXA930 Trackball mouse"
370 depends on CPU_PXA930 || CPU_PXA935
372 Say Y here to support PXA930 Trackball mouse.
375 tristate "Maple mouse (for the Dreamcast)"
378 This driver supports the Maple mouse on the SEGA Dreamcast.
380 Most Dreamcast users, who have a mouse, will say Y here.
382 To compile this driver as a module choose M here: the module will be
385 config MOUSE_SYNAPTICS_I2C
386 tristate "Synaptics I2C Touchpad support"
389 This driver supports Synaptics I2C touchpad controller on eXeda
391 The device will not work the synaptics X11 driver because
392 (i) it reports only relative coordinates and has no capabilities
393 to report absolute coordinates
394 (ii) the eXeda device itself uses Xfbdev as X Server and it does
395 not allow using xf86-input-* drivers.
397 Say y here if you have eXeda device and want to use a Synaptics
400 To compile this driver as a module, choose M here: the
401 module will be called synaptics_i2c.
403 config MOUSE_SYNAPTICS_USB
404 tristate "Synaptics USB device support"
405 depends on USB_ARCH_HAS_HCD
408 Say Y here if you want to use a Synaptics USB touchpad or pointing
411 While these devices emulate an USB mouse by default and can be used
412 with standard usbhid driver, this driver, together with its X.Org
413 counterpart, allows you to fully utilize capabilities of the device.
414 More information can be found at:
415 <http://jan-steinhoff.de/linux/synaptics-usb.html>
417 To compile this driver as a module, choose M here: the
418 module will be called synaptics_usb.
420 config MOUSE_NAVPOINT_PXA27x
421 tristate "Synaptics NavPoint (PXA27x SSP/SPI)"
422 depends on PXA27x && PXA_SSP
424 This driver adds support for the Synaptics NavPoint touchpad connected
425 to a PXA27x SSP port in SPI slave mode. The device emulates a mouse;
426 a tap or tap-and-a-half drag gesture emulates the left mouse button.
427 For example, use the xf86-input-evdev driver for an X pointing device.
429 To compile this driver as a module, choose M here: the
430 module will be called navpoint.