Le jeu. 25 avr. 2019 à 10:45, Benjamin Tissoires <benjamin.tissoires@xxxxxxxxxx> a écrit : > > On Thu, Apr 25, 2019 at 10:25 AM Clément VUCHENER > <clement.vuchener@xxxxxxxxx> wrote: > > > > Le jeu. 25 avr. 2019 à 09:40, Benjamin Tissoires > > <benjamin.tissoires@xxxxxxxxxx> a écrit : > > > > > > Hi Clément, > > > > > > On Wed, Apr 24, 2019 at 5:34 PM Clément VUCHENER > > > <clement.vuchener@xxxxxxxxx> wrote: > > > > > > > > Hi Benjamin, > > > > > > > > I tried again to add hi-res wheel support for the G500 with Hans de > > > > Goede's latest patch series you've just merged in for-5.2/logitech, it > > > > is much better but there is still some issues. > > > > > > > > The first one is the device index, I need to use device index 0 > > > > instead 0xff. I added a quick and dirty quirk (stealing in the > > > > QUIRK_CLASS range since the normal quirk range looks full) to change > > > > the device index assigned in __hidpp_send_report. After that the > > > > device is correctly initialized and the wheel multiplier is set. > > > > > > Hmm, maybe we should restrain a little bit the reserved quirks... > > > But actually, .driver_data and .quirks are both unsigned long, so you > > > should be able to use the 64 bits. > > > > Only on 64 bits architectures, or is the kernel forcing long integers > > to be 64 bits everywhere? > > Damnit, you are correct, there is no such enforcement :/ > > > > > > > > > > > > > > The second issue is that wheel values are not actually scaled > > > > according to the multiplier. I get 7/8 full scroll event for each > > > > wheel step. I think it happens because the mouse is split in two > > > > devices. The first device has the wheel events, and the second device > > > > has the HID++ reports. The wheel multiplier is only set on the second > > > > device (where the hi-res mode is enabled) and does not affect the > > > > wheel events from the first one. > > > > > > I would think this have to do with the device not accepting the > > > command instead. Can you share some raw logs of the events (ideally > > > with hid-recorder from > > > https://gitlab.freedesktop.org/libevdev/hid-tools)? > > > > I already checked with usbmon and double-checked by querying the > > register. The flag is set and accepted by the device and it behaves > > accordingly: it sends about 8 wheel events per step. > > OK, that's what I wanted to see. > > > > > hid-recorder takes hidraw nodes as parameters, how do I use it to > > record the initialization by the driver? > > You can't. But it doesn't really matter here because I wanted to check > what your mouse is actually sending after the initialization. > > So if I read correctly: the mouse is sending high res data but > evemu-recorder shows one REL_WHEEL event every 7/8 clicks? It is HID++ 1.0, there is no special high res data report, it sends standard HID mouse wheel report, but more of them. To be clear, here is a recording using the modified kernel. I moved the wheel one step up (8 events are generated), then one step down (8 events again + a 2-event bump). # EVEMU 1.3 # Kernel: 5.0.0logitech+ # DMI: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd01/17/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: # Input device name: "Logitech G500" # Input device ID: bus 0x03 vendor 0x46d product 0xc068 version 0x111 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 272 (BTN_LEFT) # Event code 273 (BTN_RIGHT) # Event code 274 (BTN_MIDDLE) # Event code 275 (BTN_SIDE) # Event code 276 (BTN_EXTRA) # Event code 277 (BTN_FORWARD) # Event code 278 (BTN_BACK) # Event code 279 (BTN_TASK) # Event code 280 ((null)) # Event code 281 ((null)) # Event code 282 ((null)) # Event code 283 ((null)) # Event code 284 ((null)) # Event code 285 ((null)) # Event code 286 ((null)) # Event code 287 ((null)) # Event type 2 (EV_REL) # Event code 0 (REL_X) # Event code 1 (REL_Y) # Event code 6 (REL_HWHEEL) # Event code 8 (REL_WHEEL) # Event code 11 ((null)) # Event code 12 ((null)) # Event type 4 (EV_MSC) # Event code 4 (MSC_SCAN) # Properties: N: Logitech G500 I: 0003 046d c068 0111 P: 00 00 00 00 00 00 00 00 B: 00 0b 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 ff ff 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 02 43 19 00 00 00 00 00 00 B: 03 00 00 00 00 00 00 00 00 B: 04 10 00 00 00 00 00 00 00 B: 05 00 00 00 00 00 00 00 00 B: 11 00 00 00 00 00 00 00 00 B: 12 00 00 00 00 00 00 00 00 B: 14 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 ################################ # Waiting for events # ################################ E: 0.000001 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.000001 0002 000b 0120 # EV_REL / (null) 120 E: 0.000001 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +0ms E: 0.042009 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.042009 0002 000b 0120 # EV_REL / (null) 120 E: 0.042009 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +42ms E: 0.075016 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.075016 0002 000b 0120 # EV_REL / (null) 120 E: 0.075016 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +33ms E: 0.107977 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.107977 0002 000b 0120 # EV_REL / (null) 120 E: 0.107977 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +32ms E: 0.124979 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.124979 0002 000b 0120 # EV_REL / (null) 120 E: 0.124979 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +17ms E: 0.141950 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.141950 0002 000b 0120 # EV_REL / (null) 120 E: 0.141950 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +17ms E: 0.152950 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.152950 0002 000b 0120 # EV_REL / (null) 120 E: 0.152950 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +11ms E: 0.170943 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 0.170943 0002 000b 0120 # EV_REL / (null) 120 E: 0.170943 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +18ms E: 1.452035 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.452035 0002 000b -120 # EV_REL / (null) -120 E: 1.452035 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +1282ms E: 1.535031 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.535031 0002 000b -120 # EV_REL / (null) -120 E: 1.535031 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +83ms E: 1.574981 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.574981 0002 000b -120 # EV_REL / (null) -120 E: 1.574981 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +39ms E: 1.702039 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.702039 0002 000b -120 # EV_REL / (null) -120 E: 1.702039 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +128ms E: 1.713031 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.713031 0002 000b -120 # EV_REL / (null) -120 E: 1.713031 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +11ms E: 1.724036 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.724036 0002 000b -120 # EV_REL / (null) -120 E: 1.724036 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +11ms E: 1.731006 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.731006 0002 000b -120 # EV_REL / (null) -120 E: 1.731006 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +7ms E: 1.740043 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.740043 0002 000b -120 # EV_REL / (null) -120 E: 1.740043 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +9ms E: 1.765013 0002 0008 -001 # EV_REL / REL_WHEEL -1 E: 1.765013 0002 000b -120 # EV_REL / (null) -120 E: 1.765013 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +25ms E: 1.975044 0002 0008 0001 # EV_REL / REL_WHEEL 1 E: 1.975044 0002 000b 0120 # EV_REL / (null) 120 E: 1.975044 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +210ms Here is the corresponding hid-recorder: D: 0 R: 67 05 01 09 02 a1 01 09 01 a1 00 05 09 19 01 29 10 15 00 25 01 95 10 75 01 81 02 05 01 16 01 80 26 ff 7f 75 10 95 02 09 30 09 31 81 06 15 81 25 7f 75 08 95 01 09 38 81 06 05 0c 0a 38 02 95 01 81 06 c0 c0 N: Logitech G500 P: usb-0000:00:14.0-2/input0 I: 3 046d c068 D: 0 E: 0.000000 8 00 00 00 00 00 00 01 00 E: 0.041957 8 00 00 00 00 00 00 01 00 E: 0.074966 8 00 00 00 00 00 00 01 00 E: 0.107932 8 00 00 00 00 00 00 01 00 E: 0.124933 8 00 00 00 00 00 00 01 00 E: 0.141897 8 00 00 00 00 00 00 01 00 E: 0.152900 8 00 00 00 00 00 00 01 00 E: 0.170892 8 00 00 00 00 00 00 01 00 E: 1.452000 8 00 00 00 00 00 00 ff 00 E: 1.535009 8 00 00 00 00 00 00 ff 00 E: 1.574928 8 00 00 00 00 00 00 ff 00 E: 1.702009 8 00 00 00 00 00 00 ff 00 E: 1.713009 8 00 00 00 00 00 00 ff 00 E: 1.724001 8 00 00 00 00 00 00 ff 00 E: 1.730963 8 00 00 00 00 00 00 ff 00 E: 1.740005 8 00 00 00 00 00 00 ff 00 E: 1.764977 8 00 00 00 00 00 00 ff 00 E: 1.975014 8 00 00 00 00 00 00 01 00 The hi-res events should +/-15 instead of +/-120, and less REL_WHEEL events should be generated. This looks like the multiplier is set to 1 instead of 8. kernel log shows the multiplier is set but only for one of the two devices: input: Logitech G500 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C068.0006/input/input25 hid-generic 0003:046D:C068.0006: input,hidraw5: USB HID v1.11 Mouse [Logitech G500] on usb-0000:00:14.0-2/input0 input: Logitech G500 Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:046D:C068.0007/input/input26 input: Logitech G500 Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:046D:C068.0007/input/input27 hid-generic 0003:046D:C068.0007: input,hiddev97,hidraw6: USB HID v1.11 Keyboard [Logitech G500] on usb-0000:00:14.0-2/input1 input: Logitech G500 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C068.0006/input/input30 logitech-hidpp-device 0003:046D:C068.0006: input,hidraw5: USB HID v1.11 Mouse [Logitech G500] on usb-0000:00:14.0-2/input0 logitech-hidpp-device 0003:046D:C068.0007: HID++ 1.0 device connected. logitech-hidpp-device 0003:046D:C068.0007: multiplier = 8 input: Logitech G500 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:046D:C068.0007/input/input31 logitech-hidpp-device 0003:046D:C068.0007: input,hiddev97,hidraw6: USB HID v1.11 Keyboard [Logitech G500] on usb-0000:00:14.0-2/input1 > > Cheers, > Benjamin > > > > > Le mer. 19 déc. 2018 à 21:35, Benjamin Tissoires > > > > <benjamin.tissoires@xxxxxxxxxx> a écrit : > > > > > > > > > > On Wed, Dec 19, 2018 at 11:57 AM Clément VUCHENER > > > > > <clement.vuchener@xxxxxxxxx> wrote: > > > > > > > > > > > > Le sam. 15 déc. 2018 à 15:45, Clément VUCHENER > > > > > > <clement.vuchener@xxxxxxxxx> a écrit : > > > > > > > > > > > > > > Le ven. 14 déc. 2018 à 19:37, Harry Cutts <hcutts@xxxxxxxxxxxx> a écrit : > > > > > > > > > > > > > > > > Hi Clement, > > > > > > > > > > > > > > > > On Fri, 14 Dec 2018 at 05:47, Clément VUCHENER > > > > > > > > <clement.vuchener@xxxxxxxxx> wrote: > > > > > > > > > Hi, The G500s (and the G500 too, I think) does support the "scrolling > > > > > > > > > acceleration" bit. If I set it, I get around 8 events for each wheel > > > > > > > > > "click", this is what this driver expects, right? If I understood > > > > > > > > > correctly, I should try this patch with the > > > > > > > > > HIDPP_QUIRK_HI_RES_SCROLL_1P0 quirk set for my mouse. > > > > > > > > > > > > > > > > Thanks for the info! Yes, that should work. > > > > > > > > > > > > > > Well, it is not that simple. I get "Device not connected" errors for > > > > > > > both interfaces of the mouse. > > > > > > > > > > > > I suspect the device is not responding because the hid device is not > > > > > > started. When is hid_hw_start supposed to be called? It is called > > > > > > early for HID_QUIRK_CLASS_G920 but later for other device. So the > > > > > > device is not started when hidpp_is_connected is called. Is this > > > > > > because most of the device in this driver are not real HID devices but > > > > > > DJ devices? How should non-DJ devices be treated? > > > > > > > > > > Hi Clement, > > > > > > > > > > I have a series I sent last September that allows to support non DJ > > > > > devices on logitech-hidpp > > > > > (https://patchwork.kernel.org/project/linux-input/list/?series=16359). > > > > > > > > > > In its current form, with the latest upstream kernel, the series will > > > > > oops during the .event() callback, which is easy enough to fix. > > > > > However, I am currently trying to make it better as a second or third > > > > > reading made me realized that there was a bunch of non-sense in it and > > > > > a proper support would require slightly more work for the non unifying > > > > > receiver case. > > > > > > > > > > I hope I'll be able to send out something by the end of the week. > > > > > > > > > > Cheers, > > > > > Benjamin
