| /linux/drivers/hid/usbhid/ |
| H A D | usbmouse.c | 5 * 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 …]
|
| H A D | Kconfig | 16 and mouse drivers at the same time. More information is available: 67 tristate "USB HIDBP Mouse (simple Boot) support" 71 to use the generic HID driver for your USB mouse and prefer 72 to use the mouse in its limited Boot Protocol mode instead.
|
| /linux/drivers/input/mouse/ |
| H A D | vsxxxaa.c | 3 * 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 D | sermouse.c | 7 * 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 D | atarimouse.c | 3 * 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()
|
| H A D | logips2pp.c | 3 * Logitech PS/2++ mouse driver 17 /* Logitech mouse types */ 23 /* Logitech mouse features */ 58 case 0x0d: /* Mouse extra info */ in ps2pp_process_byte() 181 * reasons to not use it even if the mouse supports it, and of course there are 210 { 1, 0, 0 }, /* Simple 2-button mouse */ in get_model_info() 267 * Set up input device's properties based on the detected mouse model. 299 psmouse->name = "Wheel Mouse"; in ps2pp_set_model_properties() 303 psmouse->name = "MX Mouse"; in ps2pp_set_model_properties() 316 * Set name to "Mouse" only when using PS2++, in ps2pp_set_model_properties() [all …]
|
| H A D | rpcmouse.c | 3 * Acorn RiscPC mouse driver for Linux/ARM 11 * This handles the Acorn RiscPCs mouse. We basically have a couple of 29 MODULE_DESCRIPTION("Acorn RiscPC mouse driver"); 71 rpcmouse_dev->name = "Acorn RiscPC Mouse"; in rpcmouse_init()
|
| /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) 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 …]
|
| /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 …]
|
| /linux/Documentation/ABI/obsolete/ |
| 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-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-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-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-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 …]
|
| /linux/Documentation/devicetree/bindings/input/ |
| H A D | gpio-mouse.yaml | 4 $id: http://devicetree.org/schemas/input/gpio-mouse.yaml# 7 title: GPIO attached mouse 10 This simply uses standard GPIO handles to define a simple mouse connected 18 const: gpio-mouse 58 gpio-mouse { 59 compatible = "gpio-mouse";
|
| /linux/drivers/hid/bpf/progs/ |
| H A D | HP__Elite-Presenter.bpf.c | 19 * HP Elite Presenter Mouse") in the kernel, but this is a slightly better 22 * The HP Elite Presenter Mouse HID Record Descriptor shows 25 * Prior to these fixes it registers one mouse, one keypad 28 * We replace the second mouse collection with a pointer collection, 29 * allowing to use the device both as a mouse and a digital laser 41 /* replace application mouse by application pointer on the second collection */ in SEC()
|
| /linux/arch/m68k/atari/ |
| H A D | atakeyb.c | 41 /* 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 …]
|
| /linux/drivers/staging/nvec/ |
| H A D | nvec_ps2.c | 3 * nvec_ps2: mouse driver for a NVIDIA compliant embedded controller 114 strscpy(ser_dev->name, "nvec mouse", sizeof(ser_dev->name)); in nvec_mouse_probe() 140 /* disable mouse */ in nvec_mouse_suspend() 154 /* enable mouse */ in nvec_mouse_resume() 168 .name = "nvec-mouse", 175 MODULE_DESCRIPTION("NVEC mouse driver"); 177 MODULE_ALIAS("platform:nvec-mouse");
|
| /linux/drivers/media/rc/ |
| H A D | ir-mce_kbd-decoder.c | 2 /* ir-mce_kbd-decoder.c - A decoder for the RC6-ish keyboard/mouse IR protocol 15 * - MCIR-2 29-bit IR signals used for mouse movement and buttons 21 * input device for the remote, rather than the keyboard/mouse one. 182 /* raw mouse coordinates */ in ir_mce_kbd_process_mouse_data() 186 /* mouse buttons */ in ir_mce_kbd_process_mouse_data() 200 dev_dbg(&dev->dev, "mouse: x = %d, y = %d, btns = %s%s\n", in ir_mce_kbd_process_mouse_data() 284 dev_dbg(&dev->dev, "not keyboard or mouse data\n"); in ir_mce_kbd_decode() 337 dev_dbg(&dev->dev, "mouse data 0x%06x\n", scancode); in ir_mce_kbd_decode() 338 /* Pass data to mouse buffer parser */ in ir_mce_kbd_decode() 343 dev_dbg(&dev->dev, "not keyboard or mouse data\n"); in ir_mce_kbd_decode() [all …]
|
| /linux/drivers/macintosh/ |
| H A D | adbhid.c | 19 * - Standard 1 button mouse 23 * - MicroSpeed mouse & trackball (needs testing) 25 * - Contour Design (Contour Mouse) 28 * - Mouse Systems A3 mice and trackballs <aidan@kublai.com> 29 * - MacAlly 2-buttons mouse (needs testing) <pochini@denise.shiny.it> 34 * Split mouse/kbd 63 #define MOUSE_DATAREG 0 /* reg# for movement/button codes from mouse */ 253 /* Kind of mouse */ 254 #define ADBMOUSE_STANDARD_100 0 /* Standard 100cpi mouse (handler 1) */ 255 #define ADBMOUSE_STANDARD_200 1 /* Standard 200cpi mouse (handler 2) */ [all …]
|
| /linux/Documentation/hid/ |
| H A D | hidintro.rst | 25 are using to interact with a computer, be it a mouse, a touchpad, a 32 need to have specialized code in the kernel for every mouse model 40 bits from 8 to 15 is the delta x coordinate of a mouse". 113 Parsing the mouse HID report descriptor with `hid-tools 120 # 0x09, 0x02, // Usage (Mouse) 2 170 The mouse has also two physical positions (Usage (X), Usage (Y)) 199 This Report Descriptor tells us that the mouse input will be 201 bits used, five for padding), the last three for the mouse X, Y and 204 Indeed, for any event, the mouse will send a *report* of four bytes. 252 HID devices can have Input Reports, like in the mouse example, Output [all …]
|
| /linux/drivers/hid/ |
| H A D | hid-roccat-kone.c | 12 * Roccat Kone is a gamer mouse which consists of a mouse part and a keyboard 13 * part. The keyboard part enables the mouse to execute stored macros with mixed 104 * Checks success after writing data to mouse 115 * Mouse needs 50 msecs until it says ok, but there are in kone_check_write() 141 * Reads settings from mouse and stores it in @buf 153 * Writes settings from @buf to mouse 170 * Reads profile data from mouse and stores it in @buf 196 * Writes profile data to mouse. 245 * Reads firmware_version of mouse and stores it in @result 467 * mouse, so this data needs to be reread [all …]
|
| H A D | hid-xiaomi.c | 3 * HID driver for Xiaomi Mi Dual Mode Wireless Mouse Silent Edition 14 /* Fixed Mi Silent Mouse report descriptor */ 19 0x09, 0x02, /* Usage (Mouse), */ 70 hid_info(hdev, "fixing up Mi Silent Mouse report descriptor\n"); in xiaomi_report_fixup() 94 MODULE_DESCRIPTION("Fixing side buttons of Xiaomi Mi Silent Mouse");
|
| /linux/samples/uhid/ |
| H A D | uhid-example.c | 14 * This example emulates a basic 3 buttons mouse with wheel over UHID. Run this 15 * program as root and then use the following keys to control the mouse: 20 * a: Move mouse left 21 * d: Move mouse right 22 * w: Move mouse up 23 * s: Move mouse down 27 * Additionally to 3 button mouse, 3 keyboard LEDs are also supported (LED_NUML, 53 * We emulate a basic 3 button mouse with wheel and 3 keyboard LEDs. This is 59 * Application(GenericDesktop.Mouse) 72 * Application(GenericDesktop.Mouse) [all …]
|
| /linux/drivers/misc/ibmasm/ |
| H A D | remote.c | 11 /* Remote mouse and keyboard event handling functions */ 126 dbg("remote mouse movement: (x,y)=(%d,%d)%s%s%s%s\n", in print_input() 127 input->data.mouse.x, input->data.mouse.y, in print_input() 148 input_report_abs(dev, ABS_X, input->data.mouse.x); in send_mouse_event() 149 input_report_abs(dev, ABS_Y, input->data.mouse.y); in send_mouse_event() 203 /* set up the mouse input device */ in ibmasm_init_remote_input_dev() 224 mouse_dev->name = "ibmasm RSA I remote mouse"; in ibmasm_init_remote_input_dev()
|