[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4990836470c5fb01babcf416ca6ccf9e5e21d152.camel@gmail.com>
Date: Wed, 06 Jan 2021 19:07:22 +0000
From: Filipe Laíns <filipe.lains@...il.com>
To: Jiri Kosina <jikos@...nel.org>,
Benjamin Tissoires <benjamin.tissoires@...hat.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Hans de Goede <hdegoede@...hat.com>
Subject: (hid-logitech) Support for non-DJ receivers
Hey,
Some of the new Logitech receivers do not have the DJ interface, this creates an
issue userspace applications like libratbag, as seen in [1], because we can't
identify the device based on the hidraw PID.
There are two solutions for this:
1) Implement device discovery via the internal Logitech ID in libratbag and all
other userspace apps.
2) Make hid-logitech-dj export a duplicated hidraw node with internal Logitech
ID as PID, just like it does for the DJ interface.
In case you aren't aware of what the DJ interface is, it is essentially a
multiplexing protocol that receivers support. 6 devices could be connected to
the same receiver, hid-logitech-dj enables the DJ mode and the receiver will
essentially perpend the device ID to each HID report. hid-logitech-dj then
creates a HID device for each connected device and routes the HID reports to the
correspondent HID device.
Option 2) would be the easier on userspace, as it keeps the same interface we
use for DJ receivers for other Logitech HID++ receivers and avoids all userspace
apps to have to reimplement the same discovery logic.
Any thoughts?
[1] https://github.com/libratbag/libratbag/pull/1071
Cheers,
Filipe Laíns
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists