Home
last modified time | relevance | path

Searched full:mouse (Results 1 – 25 of 552) sorted by relevance

12345678910>>...23

/openbmc/linux/drivers/hid/usbhid/
H A Dusbmouse.c5 * USB HIDBP Mouse support
32 #define DRIVER_DESC "USB HID Boot Protocol mouse driver"
51 struct usb_mouse *mouse = urb->context; in usb_mouse_irq() local
52 signed char *data = mouse->data; in usb_mouse_irq()
53 struct input_dev *dev = mouse->dev; in usb_mouse_irq()
82 dev_err(&mouse->usbdev->dev, in usb_mouse_irq()
84 mouse->usbdev->bus->bus_name, in usb_mouse_irq()
85 mouse->usbdev->devpath, status); in usb_mouse_irq()
90 struct usb_mouse *mouse = input_get_drvdata(dev); in usb_mouse_open() local
92 mouse->irq->dev = mouse->usbdev; in usb_mouse_open()
[all …]
/openbmc/linux/drivers/input/mouse/
H A Dvsxxxaa.c3 * Driver for DEC VSXXX-AA mouse (hockey-puck mouse, ball or two rollers)
4 * DEC VSXXX-GA mouse (rectangular mouse, with ball)
20 * anything if you break your mouse, your computer or whatever!
22 * In theory, this mouse is a simple RS232 device. In practice, it has got
47 * 7 (dev. avail.) - - The mouse shorts this one to pin 1.
49 * the mouse. To use it with the adaptor,
52 * So to get a working adaptor, you need to connect the mouse with three
111 static void vsxxxaa_drop_bytes(struct vsxxxaa *mouse, int num) in vsxxxaa_drop_bytes() argument
113 if (num >= mouse->count) { in vsxxxaa_drop_bytes()
114 mouse->count = 0; in vsxxxaa_drop_bytes()
[all …]
H A DKconfig3 # Mouse driver configuration
17 tristate "PS/2 mouse"
24 Say Y here if you have a PS/2 mouse connected to your system. This
25 includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
43 bool "ALPS PS/2 mouse protocol extension" if EXPERT
53 bool "BYD PS/2 mouse protocol extension" if EXPERT
63 bool "Logitech PS/2++ mouse protocol extension" if EXPERT
67 Say Y here if you have a Logitech PS/2++ mouse connected to
73 bool "Synaptics PS/2 mouse protocol extension" if EXPERT
95 bool "Cypress PS/2 mouse protocol extension" if EXPERT
[all …]
H A Dsermouse.c7 * Serial mouse driver for Linux
17 #define DRIVER_DESC "Serial mouse driver"
23 …atic const char *sermouse_protocols[] = { "None", "Mouse Systems Mouse", "Sun Mouse", "Microsoft M…
24 "Logitech M+ Mouse", "Microsoft MZ Mouse", "Logitech MZ+ Mouse",
25 "Logitech MZ++ Mouse"};
39 * second, which is as good as a PS/2 or USB mouse.
161 case 1: /* Extra mouse info */ in sermouse_process_ms()
209 * to the mouse anymore.
H A Datarimouse.c3 * Atari mouse driver for Linux/m68k
8 * Amiga mouse driver for Linux/m68k
14 * (the keyboard ACIA also handles the mouse and joystick data, and the keyboard
20 * Atari Mouse Driver for Linux
25 * Support for three button mouse (shamelessly stolen from MiNT)
51 MODULE_DESCRIPTION("Atari mouse driver");
123 atamouse_dev->name = "Atari mouse"; in atamouse_init()
/openbmc/qemu/chardev/
H A Dmsmouse.c2 * QEMU Microsoft serial mouse emulation
43 /* Mouse ID: Send "M3" cause we behave like a 3 button logitech mouse. */
75 MouseChardev *mouse = MOUSE_CHARDEV(chr); in DECLARE_INSTANCE_CHECKER() local
79 avail = fifo8_num_used(&mouse->outbuf); in DECLARE_INSTANCE_CHECKER()
84 buf = fifo8_pop_bufptr(&mouse->outbuf, MIN(len, avail), &size); in DECLARE_INSTANCE_CHECKER()
91 static void msmouse_queue_event(MouseChardev *mouse) in msmouse_queue_event() argument
96 dx = mouse->axis[INPUT_AXIS_X]; in msmouse_queue_event()
97 mouse->axis[INPUT_AXIS_X] = 0; in msmouse_queue_event()
99 dy = mouse->axis[INPUT_AXIS_Y]; in msmouse_queue_event()
100 mouse->axis[INPUT_AXIS_Y] = 0; in msmouse_queue_event()
[all …]
/openbmc/linux/Documentation/input/devices/
H A Datarikbd.rst12 provides a convenient connection point for a mouse and switch-type joysticks.
17 keyswitches, mouse resolution, etc. can be accommodated.
20 different applications of the keyboard, joysticks, or mouse. Limited use of
40 0xF7 absolute mouse position record
41 0xF8-0xFB relative mouse position records (lsbs determined by
42 mouse button states)
52 Mouse chapter
55 The mouse port should be capable of supporting a mouse with resolution of
57 mouse should be scanned at a rate that will permit accurate tracking at
59 The ikbd can report mouse motion in three distinctly different ways. It can
[all …]
/openbmc/linux/Documentation/arch/x86/
H A Dusb-legacy-support.rst11 Also known as "USB Keyboard" or "USB Mouse support" in the BIOS Setup is a
12 feature that allows one to use the USB mouse and keyboard as if they were
18 1) On some machines, the emulated PS/2 mouse takes over even when no USB
19 mouse is present and a real PS/2 mouse is present. In that case the extra
20 features (wheel, extra buttons, touchpad mode) of the real PS/2 mouse may
23 2) If CONFIG_HIGHMEM64G is enabled, the PS/2 mouse emulation can cause
36 PS/2 mouse driver. Since the PS/2 mouse driver is in 2.6 compiled into
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-driver-hid-roccat-kone4 Description: It is possible to switch the dpi setting of the mouse with the
8 setting reported by the mouse. This number has to be further
37 firmware reported by the mouse. Using the integer value eases
48 Description: The mouse can store 5 profiles which can be switched by the
57 data back to the mouse. The data has to be 975 bytes long.
59 The mouse will reject invalid data, whereas the profile number
67 Description: When read, this file returns the settings stored in the mouse.
71 When written, this file lets write settings back to the mouse.
72 The data has to be 36 bytes long. The mouse will reject invalid
82 that's active when the mouse is powered on.
[all …]
/openbmc/linux/Documentation/ABI/obsolete/
H A Dsysfs-driver-hid-roccat-savu4 Description: The mouse can store 5 profiles which can be switched by the
8 respective profile buttons to the mouse. The data has to be
10 The mouse will reject invalid data.
28 Description: The mouse can store 5 profiles which can be switched by the
33 settings back to the mouse. The data has to be 43 bytes long.
34 The mouse will reject invalid data.
62 Description: The mouse can store 5 profiles which can be switched by the
65 that's active when the mouse is powered on next time.
66 When written, the mouse activates the set profile immediately.
68 The mouse will reject invalid data.
[all …]
H A Dsysfs-driver-hid-roccat-konepure4 Description: The mouse can store 5 profiles which can be switched by the
7 that's active when the mouse is powered on next time.
8 When written, the mouse activates the set profile immediately.
10 The mouse will reject invalid data.
32 Description: The mouse can store a macro with max 500 key/button strokes
43 Description: The mouse can store 5 profiles which can be switched by the
47 buttons back to the mouse. The data has to be 59 bytes long.
48 The mouse will reject invalid data.
58 Description: The mouse can store 5 profiles which can be switched by the
63 settings back to the mouse. The data has to be 31 bytes long.
[all …]
H A Dsysfs-driver-hid-roccat-pyra4 Description: It is possible to switch the cpi setting of the mouse with the
7 setting reported by the mouse. This number has to be further
35 firmware reported by the mouse. Using the integer value eases
54 Description: The mouse can store 5 profiles which can be switched by the
58 buttons back to the mouse. The data has to be 19 bytes long.
59 The mouse will reject invalid data.
69 Description: The mouse can store 5 profiles which can be switched by the
81 Description: The mouse can store 5 profiles which can be switched by the
86 settings back to the mouse. The data has to be 13 bytes long.
87 The mouse will reject invalid data.
[all …]
H A Dsysfs-driver-hid-roccat-koneplus7 profile that's active when the mouse is powered on next time.
9 and the mouse activates this profile immediately.
18 profile that's active when the mouse is powered on next time.
20 and the mouse activates this profile immediately.
28 firmware reported by the mouse. Using the integer value eases
47 Description: The mouse can store a macro with max 500 key/button strokes
58 Description: The mouse can store 5 profiles which can be switched by the
62 buttons back to the mouse. The data has to be 77 bytes long.
63 The mouse will reject invalid data.
73 Description: The mouse can store 5 profiles which can be switched by the
[all …]
H A Dsysfs-driver-hid-roccat-kovaplus17 When written, the mouse activates this profile immediately.
19 active when the mouse is powered on.
46 firmware reported by the mouse. Using the integer value eases
65 Description: The mouse can store 5 profiles which can be switched by the
69 buttons back to the mouse. The data has to be 23 bytes long.
70 The mouse will reject invalid data.
80 Description: The mouse can store 5 profiles which can be switched by the
92 Description: The mouse can store 5 profiles which can be switched by the
97 settings back to the mouse. The data has to be 16 bytes long.
98 The mouse will reject invalid data.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/input/
H A Dgpio-mouse.txt3 This simply uses standard GPIO handles to define a simple mouse connected
7 - compatible: must be "gpio-mouse"
15 - button-left-gpios: GPIO line handle to the left mouse button
16 - button-middle-gpios: GPIO line handle to the middle mouse button
17 - button-right-gpios: GPIO line handle to the right mouse button
22 gpio-mouse {
23 compatible = "gpio-mouse";
/openbmc/linux/drivers/input/
H A DKconfig9 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
12 Say Y here if you have any input device (mouse, keyboard, tablet,
15 keyboard and mouse.
90 tristate "Mouse interface"
92 Say Y here if you want your mouse to be accessible as char devices
94 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
96 mouse.
107 Say Y here if you want your mouse also be accessible as char device
119 it as a mouse then the mousedev driver needs to know the X window
129 it as a mouse then the mousedev driver needs to know the X window
[all …]
/openbmc/qemu/tests/qtest/
H A Ddevice-plug-test.c71 if (!qtest_has_device("virtio-mouse-pci")) { in test_pci_unplug_request()
72 g_test_skip("Device virtio-mouse-pci not available"); in test_pci_unplug_request()
80 qtest = qtest_initf("%s -device virtio-mouse-pci,id=dev0", in test_pci_unplug_request()
92 if (!qtest_has_device("virtio-mouse-pci")) { in test_q35_pci_unplug_request()
93 g_test_skip("Device virtio-mouse-pci not available"); in test_q35_pci_unplug_request()
100 "-device virtio-mouse-pci,bus=b1,id=dev0"); in test_q35_pci_unplug_request()
113 if (!qtest_has_device("virtio-mouse-pci")) { in test_pci_unplug_json_request()
114 g_test_skip("Device virtio-mouse-pci not available"); in test_pci_unplug_json_request()
123 "%s -device \"{'driver': 'virtio-mouse-pci', 'id': 'dev0'}\"", in test_pci_unplug_json_request()
141 const char *device = "-device \"{'driver': 'virtio-mouse-pci', " in test_q35_pci_unplug_json_request()
[all …]
/openbmc/linux/drivers/staging/nvec/
H A Dnvec_ps2.c3 * nvec_ps2: mouse driver for a NVIDIA compliant embedded controller
83 NVEC_PHD("ps/2 mouse event: ", &msg[2], msg[1]); in nvec_ps2_notifier()
90 NVEC_PHD("ps/2 mouse reply: ", &msg[4], msg[1] - 2); in nvec_ps2_notifier()
94 NVEC_PHD("unhandled mouse event: ", msg, msg[1] + 2); in nvec_ps2_notifier()
115 strscpy(ser_dev->name, "nvec mouse", sizeof(ser_dev->name)); in nvec_mouse_probe()
141 /* disable mouse */ in nvec_mouse_suspend()
155 /* enable mouse */ in nvec_mouse_resume()
169 .name = "nvec-mouse",
176 MODULE_DESCRIPTION("NVEC mouse driver");
178 MODULE_ALIAS("platform:nvec-mouse");
/openbmc/linux/Documentation/input/
H A Dinput.rst25 events (keystrokes, mouse movements) to the input module.
31 via various interfaces - keystrokes to the kernel, mouse movements via
37 For the most usual configuration, with one USB mouse and one USB keyboard,
48 After this, the USB keyboard will work straight away, and the USB mouse
60 After that you have to point GPM (the textmode mouse cut&paste tool) and
73 When you do all of the above, you can use your USB mouse and keyboard.
118 ``mousedev`` is a hack to make legacy programs that use mouse input
120 a PS/2-style (a la /dev/psaux) mouse device available to the
134 Each ``mouse`` device is assigned to a single mouse or digitizer, except
144 via a virtual PS/2 mouse and thus needs to be scaled
[all …]
/openbmc/qemu/hw/input/
H A Dadb-mouse.c2 * QEMU ADB mouse support
97 .name = "QEMU ADB Mouse",
102 * mouse events are sent over the serial port, an ADB mouse is constantly
157 /* flush mouse fifo */ in adb_mouse_request()
199 * 0x01: Classic Apple Mouse Protocol / 100 cpi operations in adb_mouse_request()
200 * 0x02: Classic Apple Mouse Protocol / 200 cpi operations in adb_mouse_request()
202 * 0x03: Mouse systems A3 trackball in adb_mouse_request()
203 * 0x04: Extended Apple Mouse Protocol in adb_mouse_request()
204 * 0x2f: Microspeed mouse in adb_mouse_request()
206 * 0x5f: Microspeed mouse in adb_mouse_request()
[all …]
/openbmc/linux/drivers/input/serio/
H A DKconfig11 * standard AT keyboard and PS/2 mouse *
25 communicate with keyboard, mouse, etc.
35 mouse are connected to the computer. If you use these devices,
48 Say Y here if you plan to use an input device (mouse, joystick,
63 equipped with the ct82c710 chip and want to use a mouse connected
80 an additional AT keyboard, XT keyboard or PS/2 mouse.
109 tristate "HP GSC PS/2 keyboard and PS/2 mouse controller"
149 tristate "PCI PS/2 keyboard and PS/2 mouse controller"
174 and you want to attach and use a keyboard, mouse, or both.
184 to a PS/2 port, such as PS/2 mouse or standard AT keyboard.
[all …]
/openbmc/qemu/include/hw/input/
H A Di8042.h47 * + Named GPIO input "ps2-mouse-input-irq": set to 1 if the downstream PS2
48 * mouse device has asserted its irq
50 * + Unnamed GPIO output 0-1: i8042 output irqs for keyboard (0) or mouse (1)
72 * + Named GPIO input "ps2-mouse-input-irq": set to 1 if the downstream PS2
73 * mouse device has asserted its irq
74 * + Unnamed GPIO output 0-1: i8042 output irqs for keyboard (0) or mouse (1)
/openbmc/linux/arch/m68k/atari/
H A Datakeyb.c41 /* Hook for mouse inputdev driver */
119 * This usually causes keyboards bytes to be interpreted as mouse movements
121 * bytes (that are usually mouse bytes) than to misinterpret them. Therefore I
123 * one that really looks like a key event (0x04..0xf2) or the start of a mouse
126 * mouse movement is lost. However, nothing is perfect. For bytes 0x01..0x03,
127 * it's really hard to decide whether they're mouse or keyboard bytes. Since
128 * overruns usually occur when moving the Atari mouse rapidly, they're seen as
129 * mouse bytes here. If this is wrong, only a make code of the keyboard gets
347 /* Set mouse button action */
355 /* Set relative mouse position reporting */
[all …]
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-driver/
H A Dxf86-input-mouse_1.9.5.bb3 SUMMARY = "X.Org X server -- mouse input driver"
5 DESCRIPTION = "mouse is an Xorg input driver for mice. The driver \
6 supports most available mouse types and interfaces. The mouse driver \
/openbmc/qemu/docs/system/
H A Dbarrier.rst4 Generally, mouse and keyboard are grabbed through the QEMU video
8 there is no way to provide the keyboard and mouse inputs to the VM
9 except by plugging a second set of mouse and keyboard to the host
16 is a KVM (Keyboard-Video-Mouse) software forked from Symless's
33 on the host providing the mouse and the keyboard events.

12345678910>>...23