Home
last modified time | relevance | path

Searched full:wheel (Results 1 – 25 of 95) sorted by relevance

1234

/linux-6.12.1/drivers/hid/
Dhid-thrustmaster.c4 * a «generic» hid gamepad called "Thrustmaster FFB Wheel".
6 * When in this mode not every functionality of the wheel, like the force feedback,
7 * are available. To enable all functionalities of a Thrustmaster wheel we have to send
8 * to it a specific USB CONTROL request with a code different for each wheel.
10 * This driver tries to understand which model of Thrustmaster wheel the generic
11 * "Thrustmaster FFB Wheel" really is and then sends the appropriate control code.
41 * Thrustmaster wheel
69 {0x0209, 0x0005, "Thrustmaster T300RS (Open Wheel Attachment)"},
80 * of the wheel to the request 73
100 * Seems to be the model code of the wheel
[all …]
Dhid-creative-sb0540.c21 KEY_RESERVED, /* 24bit wheel up */
22 KEY_RESERVED, /* 24bit wheel down */
24 KEY_RESERVED, /* CMSS wheel Up */
25 KEY_RESERVED, /* CMSS wheel Down */
27 KEY_RESERVED, /* EAX wheel up */
28 KEY_RESERVED, /* EAX wheel down */
30 KEY_RESERVED, /* 3D Midi wheel up */
31 KEY_RESERVED, /* 3D Midi wheel down */
Dhid-lg4ff.c50 #define LG4FF_G25_NAME "G25 Racing Wheel"
52 #define LG4FF_G27_NAME "G27 Racing Wheel"
54 #define LG4FF_G29_NAME "G29 Racing Wheel"
173 /* Multimode wheel identificators */
216 /* Multimode wheel identification checklists */
368 /* Compute a combined axis when wheel does not supply it */ in lg4ff_raw_event()
377 … void lg4ff_init_wheel_data(struct lg4ff_wheel_data * const wdata, const struct lg4ff_wheel *wheel, in lg4ff_init_wheel_data() argument
392 struct lg4ff_wheel_data t_wdata = { .product_id = wheel->product_id, in lg4ff_init_wheel_data()
395 .min_range = wheel->min_range, in lg4ff_init_wheel_data()
396 .max_range = wheel->max_range, in lg4ff_init_wheel_data()
[all …]
Dhid-tmff.c247 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb605), /* NASCAR PRO FF2 Wheel */
249 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb651), /* FGT Rumble Force Wheel */
251 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb653), /* RGT Force Feedback CLUTCH Raging Wheel */
253 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb654), /* FGT Force Feedback Wheel */
255 { HID_USB_DEVICE(USB_VENDOR_ID_THRUSTMASTER, 0xb65a), /* F430 Force Feedback Wheel */
Dhid-roccat-kone.h23 kone_keystroke_button_3 = 0xf2, /* wheel */
47 kone_button_info_type_button_3 = 0x3, /* scroll (wheel) */
154 uint8_t wheel; /* up = 1, down = -1 */ member
Dwacom.h31 * Fix Wacom Graphire mouse wheel
32 * v1.18 (vp) - Fix mouse wheel direction
38 * - Fix Wacom Graphire mouse wheel again
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-driver-hid-logitech-lg4ff6 wheel. Writing a value within min and max boundaries sets the
7 range of the wheel.
13 Description: Displays a set of alternate modes supported by a wheel. Each
20 native mode of the wheel. Echoing the mode tag switches the
21 wheel into the corresponding mode. Depending on the exact model
22 of the wheel not all listed modes might always be selectable.
23 If a wheel cannot be switched into the desired mode, -EINVAL
63 Description: Displays the real model of the wheel regardless of any
64 alternate mode the wheel might be switched to.
Dsysfs-driver-hid-logitech-hidpp7 Logitech G920 wheel. Reading from the file shows the current
8 range of the steering wheel. Writing a value within the min and
9 max boundary sets the range of the wheel.
/linux-6.12.1/Documentation/timers/
Dhrtimers.rst12 conclusion that the timer wheel code is fundamentally not suitable for
15 things into the timer wheel, but we failed. In hindsight, there are
24 the wheel concept, leading to even worse compromises. The timer wheel
33 wheel concept, it cannot be 'designed out' without inevitably
37 the timer wheel has already introduced a quite complex handling of
40 example: that the timer wheel data structure is too rigid for high-res
43 - the timer wheel code is most optimal for use cases which can be
48 can be removed from the timer wheel before any further processing of
50 the granularity and precision tradeoffs of the timer wheel, and
72 special-purpose optimization of the existing timer wheel for the low
[all …]
/linux-6.12.1/drivers/hid/bpf/progs/
DHuion__Inspiroy-2-S.bpf.c191 // Byte 4 in report is the wheel
337 // Byte 5 is the wheel
424 * Wheel down: 03 01 2d 00 00 00 00 00 -> Ctrl - in SEC()
425 * Wheel up: 03 01 2e 00 00 00 00 00 -> Ctrl = in SEC()
428 __u8 wheel = 0; in SEC() local
452 wheel = -1; in SEC()
455 wheel = 1; in SEC()
460 __u8 report[6] = {PAD_REPORT_ID, 0x0, 0x0, 0x0, wheel, button}; in SEC()
479 __u8 wheel; in SEC() member
481 __u8 wheel = 0; in SEC() local
[all …]
/linux-6.12.1/samples/uhid/
Duhid-example.c14 * This example emulates a basic 3 buttons mouse with wheel over UHID. Run this
24 * r: Move wheel up
25 * f: Move wheel down
53 * We emulate a basic 3 button mouse with wheel and 3 keyboard LEDs. This is
76 * GenericDesktop.Wheel
103 * GenericDesktop.Wheel ---> Relative.Wheel
133 0x09, 0x38, /* USAGE (WHEEL) */
276 static signed char wheel; variable
296 ev.u.input.data[4] = wheel; in send_event()
364 wheel = 1; in keyboard()
[all …]
/linux-6.12.1/drivers/input/joystick/iforce/
DKconfig9 Say Y here if you have an I-Force joystick or steering wheel
20 Say Y here if you have an I-Force joystick or steering wheel
27 Say Y here if you have an I-Force joystick or steering wheel
Diforce-main.c53 { 0x05ef, 0x8886, "Boeder Force Feedback Wheel", btn_wheel, abs_wheel, ff_iforce },
54 …{ 0x05ef, 0x8888, "AVB Top Shot Force Feedback Racing Wheel", btn_wheel, abs_wheel, ff_iforce }, /…
57 { 0x06a3, 0xff04, "Saitek R440 Force Wheel", btn_wheel, abs_wheel, ff_iforce }, //?
60 { 0x06f8, 0x0004, "Guillemot Force Feedback Racing Wheel", btn_wheel, abs_wheel, ff_iforce }, //?
Diforce-usb.c275 { USB_DEVICE(0x05ef, 0x8888) }, /* AVB Top Shot FFB Racing Wheel */
278 { USB_DEVICE(0x06a3, 0xff04) }, /* Saitek R440 Force Wheel */
281 { USB_DEVICE(0x06f8, 0x0004) }, /* Guillemot Force Feedback Racing Wheel */
/linux-6.12.1/Documentation/hid/
Dhidintro.rst30 wheel; movement sensitivity differs between different models, and so
168 # 0x09, 0x38, // Usage (Wheel) 38
171 and a wheel (Usage (Wheel)) ::
184 and there are three of those eight bits, matching X, Y and Wheel. ::
202 wheel changes, respectively.
215 # Button: 1 0 0 | # | X: 0 | Y: 0 | Wheel: 0
217 # Button: 0 0 0 | # | X: 0 | Y: 0 | Wheel: 0
219 # Button: 0 1 0 | # | X: 0 | Y: 0 | Wheel: 0
221 # Button: 0 0 0 | # | X: 0 | Y: 0 | Wheel: 0
223 # Button: 0 0 1 | # | X: 0 | Y: 0 | Wheel: 0
[all …]
/linux-6.12.1/drivers/input/misc/
Dad714x.c108 * Unlike slider/wheel/touchpad, all buttons point to
116 struct ad714x_wheel_drv *wheel; member
401 * When the scroll wheel is activated, we compute the absolute position based
409 struct ad714x_wheel_plat *hw = &ad714x->hw->wheel[idx]; in ad714x_wheel_cal_highest_stage()
410 struct ad714x_wheel_drv *sw = &ad714x->sw->wheel[idx]; in ad714x_wheel_cal_highest_stage()
416 dev_dbg(ad714x->dev, "wheel %d highest_stage:%d\n", idx, in ad714x_wheel_cal_highest_stage()
422 struct ad714x_wheel_plat *hw = &ad714x->hw->wheel[idx]; in ad714x_wheel_cal_sensor_val()
441 * When the scroll wheel is activated, we compute the absolute position based
451 struct ad714x_wheel_plat *hw = &ad714x->hw->wheel[idx]; in ad714x_wheel_cal_abs_pos()
452 struct ad714x_wheel_drv *sw = &ad714x->sw->wheel[idx]; in ad714x_wheel_cal_abs_pos()
[all …]
/linux-6.12.1/tools/testing/selftests/hid/tests/
Dtest_mouse.py50 :param wheels: a single value for the vertical wheel or a (vertical, horizontal) tuple for
65 # Note: the BaseMouse doesn't actually have a wheel but the
68 wheel, acpan = 0, 0
71 wheel = wheels[0]
74 wheel = wheels
84 mouse.wheel = wheel
96 :param wheels: a single value for the vertical wheel or a (vertical, horizontal) tuple for
192 0x09, 0x38, # .Usage (Wheel) 49
235 0x09, 0x38, # ..Usage (Wheel) 52
274 0x09, 0x38, # ..Usage (Wheel)
[all …]
/linux-6.12.1/drivers/input/tablet/
Daiptek.c34 * Wheel command. Bryan W. Headley July-15-2003.
194 /* Wheel values
278 int wheel; /* synthetic wheel amount */ member
484 /* Wheel support is in the form of a single-event in aiptek_irq()
487 if (aiptek->curSetting.wheel != AIPTEK_WHEEL_DISABLE) { in aiptek_irq()
489 aiptek->curSetting.wheel); in aiptek_irq()
490 aiptek->curSetting.wheel = AIPTEK_WHEEL_DISABLE; in aiptek_irq()
565 /* Wheel support is in the form of a single-event in aiptek_irq()
568 if (aiptek->curSetting.wheel != in aiptek_irq()
572 aiptek->curSetting.wheel); in aiptek_irq()
[all …]
/linux-6.12.1/sound/isa/gus/
Dgus_volume.c151 int wheel, sensitivity;
159 wheel = (int) pitchbend - 8192;
160 sensitivity = ((int) sens * wheel) / 128;
/linux-6.12.1/Documentation/input/devices/
Diforce-protocol.rst62 OP= 01 for a joystick, 03 for a wheel
66 02 Y-Axis lsb, or gas pedal for a wheel
67 03 Y-Axis msb, or brake pedal for a wheel
366 joystick/wheel). I used ComPortSpy from fCoder (alpha version!)
/linux-6.12.1/Documentation/input/joydev/
Djoystick.rst233 * Microsoft SideWinder Force Feedback Wheel
519 * AVB Top Shot Force Feedback Racing Wheel
520 * Boeder Force Feedback Wheel
522 * Logitech WingMan Force Wheel
524 * Guillemot Force Feedback Racing Wheel
/linux-6.12.1/kernel/time/
Dtimer.c66 * The timer wheel has LVL_DEPTH array levels. Each level provides an array of
77 * Contrary to the original timer wheel implementation, which aims for 'exact'
79 * the timers into the lower array levels. The previous 'classic' timer wheel
84 * This is an optimization of the original timer wheel implementation for the
85 * majority of the timer wheel use cases: timeouts. The vast majority of
91 * time. They rely on the granularity. Those fit into the first wheel level,
95 * capacity of the last wheel level are force expired at the maximum timeout
96 * value of the last wheel level. From data sampling we know that the maximum
180 /* The cutoff (max. capacity of the wheel) */
185 * The resulting wheel size. If NOHZ is configured we allocate two
[all …]
/linux-6.12.1/drivers/gpu/drm/ci/xfails/
Drequirements.txt17 wheel==0.41.1
/linux-6.12.1/Documentation/input/
Devent-codes.rst197 respectively. The value is the number of detents moved on the wheel, the
206 - High-resolution scroll wheel data. The accumulated value 120 represents
211 If a vertical scroll wheel supports high-resolution scrolling, this code
416 scroll wheel events where available.
/linux-6.12.1/drivers/input/mouse/
Dvmmouse.c154 * This doesn't work well with the mouse wheel, though. See in vmmouse_report_events()
168 /* Xorg seems to ignore wheel events on absolute devices */ in vmmouse_report_events()
450 /* Add wheel capability to the relative device */ in vmmouse_init()

1234