From: Mike Gleason jr Couturier <mikegleasonjr@gmail.com>
To: basti@thomae-home.info
Cc: linux-input@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>
Subject: Re: Logitech G502 X (046d:c099): REL_WHEEL_HI_RES always reports ±120
Date: Sat, 17 Oct 2026 21:15:57 +0000 [thread overview]
Message-ID: <20261017211557.64095-1-mikegleasonjr@users.noreply.github.com> (raw)
In-Reply-To: <504f3ea7-fd23-428b-873b-12ed8bbce3ca@thomae-home.info>
Hi,
I see the same behavior with a wired G502 X (046d:c099) and tried
binding hid-logitech-hidpp to it, which nobody had reported yet.
Environment:
Fedora 44, kernel 7.2.10-200.fc44.x86_64
libinput 1.31.3, Solaar 1.1.20, GNOME on Wayland
By default both interfaces bind to hid-generic and every wheel event
is REL_WHEEL ±1 / REL_WHEEL_HI_RES ±120, one per detent.
I then forced hid-logitech-hidpp onto the device:
modprobe hid-logitech-hidpp
echo "0003 046d c099" > /sys/bus/hid/drivers/logitech-hidpp-device/new_id
(replug)
Both interfaces bind to logitech-hidpp-device:
logitech-hidpp-device 0003:046D:C099.0013: input,hidraw0: USB HID v1.11 Mouse [Logitech G502 X] on usb-0000:10:00.4-1/input0
logitech-hidpp-device 0003:046D:C099.0014: input,hiddev96,hidraw1: USB HID v1.11 Keyboard [Logitech G502 X] on usb-0000:10:00.4-1/input1
logitech-hidpp-device 0003:046D:C099.0014: HID++ 4.2 device connected.
Only the second interface (input1) reports HID++. Solaar shows the
device has feature 0x2121 (HIRES WHEEL v1), and I set it to high
resolution mode (Onboard Profiles disabled).
With high resolution mode on, libinput still sees 15.00/120 per
event, but there are now roughly 8 events per detent:
POINTER_SCROLL_WHEEL +22.240s vert 15.00/120.0* horiz 0.00/0.0 (wheel)
POINTER_SCROLL_WHEEL +22.310s vert 15.00/120.0* horiz 0.00/0.0 (wheel)
POINTER_SCROLL_WHEEL +22.339s vert 15.00/120.0* horiz 0.00/0.0 (wheel)
POINTER_SCROLL_WHEEL +22.405s vert 15.00/120.0* horiz 0.00/0.0 (wheel)
...
So the device does send high-resolution deltas once 0x2121 is in
high resolution mode, but they come in through the mouse interface
(input0), which does not apply the resolution multiplier. The
interface that negotiates HID++ (input1) is not the one that
generates the wheel events.
It looks like the G502 X needs a proper entry in hidpp_devices[] that
handles the split interfaces, not just its ID added. I'm happy to
test patches on this hardware.
Thanks,
Mike
prev parent reply other threads:[~2026-10-17 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 5:46 Logitech G502 X (046d:c099): REL_WHEEL_HI_RES always reports ±120 Sebastian Thomae
2026-10-17 21:15 ` Mike Gleason jr Couturier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261017211557.64095-1-mikegleasonjr@users.noreply.github.com \
--to=mikegleasonjr@gmail.com \
--cc=basti@thomae-home.info \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox