| /openbmc/linux/drivers/input/mouse/ |
| H A D | vsxxxaa.c | 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()
116 memmove(mouse->buf, mouse->buf + num, BUFLEN - num); in vsxxxaa_drop_bytes()
117 mouse->count -= num; in vsxxxaa_drop_bytes()
121 static void vsxxxaa_queue_byte(struct vsxxxaa *mouse, unsigned char byte) in vsxxxaa_queue_byte() argument
123 if (mouse->count == BUFLEN) { in vsxxxaa_queue_byte()
125 mouse->name, mouse->phys); in vsxxxaa_queue_byte()
126 vsxxxaa_drop_bytes(mouse, 1); in vsxxxaa_queue_byte()
131 mouse->buf[mouse->count++] = byte; in vsxxxaa_queue_byte()
[all …]
|
| H A D | Kconfig | 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
105 bool "Fujitsu Lifebook PS/2 mouse protocol extension" if EXPERT
[all …]
|
| /openbmc/linux/drivers/hid/usbhid/ |
| H A D | usbmouse.c | 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()
93 if (usb_submit_urb(mouse->irq, GFP_KERNEL)) in usb_mouse_open()
101 struct usb_mouse *mouse = input_get_drvdata(dev); in usb_mouse_close() local
[all …]
|
| /openbmc/qemu/chardev/ |
| H A D | msmouse.c | 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()
108 bytes[0] |= (mouse->btns[INPUT_BUTTON_LEFT] ? 0x20 : 0x00); in msmouse_queue_event()
109 bytes[0] |= (mouse->btns[INPUT_BUTTON_RIGHT] ? 0x10 : 0x00); in msmouse_queue_event()
[all …]
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | atarikbd.rst | 12 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)
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
61 within the ikbd, or by converting mouse motion into keyboard cursor control
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | gpio-mouse.txt | 3 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/Documentation/ABI/testing/ |
| H A D | sysfs-driver-hid-roccat-kone | 4 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 …]
|
| H A D | sysfs-driver-hid-lenovo | 4 Description: This controls if mouse clicks should be generated if the trackpoint is quickly pressed…
30 Description: This setting controls if the mouse click events generated by pressing the trackpoint (…
31 a left or right mouse button click.
47 Description: This setting controls how fast the trackpoint needs to be pressed to generate a mouse …
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | usb-legacy-support.rst | 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/obsolete/ |
| H A D | sysfs-driver-hid-roccat-savu | 4 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 D | sysfs-driver-hid-roccat-konepure | 4 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 D | sysfs-driver-hid-roccat-koneplus | 7 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 D | sysfs-driver-hid-roccat-pyra | 4 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 D | sysfs-driver-hid-roccat-kovaplus | 17 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/openbmc/poky/meta/recipes-graphics/xorg-driver/ |
| H A D | xf86-input-mouse_1.9.5.bb | 3 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 \
|
| H A D | xf86-input-vmmouse_13.2.0.bb | 3 SUMMARY = "X.Org X server -- VMWare mouse input driver"
7 standard 'mouse' driver if a VMware virtual machine is not detected."
13 RDEPENDS:${PN} += "xf86-input-mouse"
|
| H A D | xf86-input-synaptics_1.9.2.bb | 7 operating in a compatibility mode emulating a standard mouse) can be \
8 handled by the normal evdev or mouse drivers, this driver allows more \
|
| /openbmc/linux/drivers/input/ |
| H A D | Kconfig | 9 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.
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
159 want all events (keypresses, mouse movements), to be output to
[all …]
|
| /openbmc/linux/Documentation/input/ |
| H A D | input.rst | 25 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/ui/ |
| H A D | ui-hmp-cmds.c | 82 MouseInfoList *mice_list, *mouse; in hmp_info_mice() local
90 for (mouse = mice_list; mouse; mouse = mouse->next) { in hmp_info_mice()
92 mouse->value->current ? '*' : ' ', in hmp_info_mice()
93 mouse->value->index, mouse->value->name, in hmp_info_mice()
94 mouse->value->absolute ? " (absolute)" : ""); in hmp_info_mice()
|
| H A D | vdagent.c | 39 bool mouse; member
197 if (vd->mouse) { in vdagent_send_caps()
217 return vd->mouse && in have_mouse()
225 VDAgentMouseState *mouse = (void *)msg->data; in vdagent_send_mouse() local
230 mouse->x = vd->mouse_x; in vdagent_send_mouse()
231 mouse->y = vd->mouse_y; in vdagent_send_mouse()
232 mouse->buttons = vd->mouse_btn; in vdagent_send_mouse()
233 mouse->display_id = vd->mouse_display; in vdagent_send_mouse()
679 vd->mouse = VDAGENT_MOUSE_DEFAULT; in vdagent_chr_open()
681 vd->mouse = cfg->mouse; in vdagent_chr_open()
[all …]
|
| H A D | spice-input.c | 108 SpiceMouseInstance mouse; member
146 QemuSpicePointer *pointer = container_of(sin, QemuSpicePointer, mouse); in mouse_motion()
155 QemuSpicePointer *pointer = container_of(sin, QemuSpicePointer, mouse); in mouse_buttons()
252 pointer->mouse.base.sif = &mouse_interface.base; in qemu_spice_input_init()
254 qemu_spice.add_interface(&pointer->mouse.base); in qemu_spice_input_init()
|
| /openbmc/qemu/docs/system/ |
| H A D | barrier.rst | 4 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
33 on the host providing the mouse and the keyboard events.
|
| /openbmc/linux/drivers/input/serio/ |
| H A D | Kconfig | 11 * 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/openbmc/poky/meta/recipes-graphics/xorg-app/ |
| H A D | xeyes_1.3.0.bb | 3 SUMMARY = "X11 eyes that follow the mouse cursor demo"
5 follow the location of the mouse cursor around the screen."
|