diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2019-04-20 14:21:54 +0300 |
|---|---|---|
| committer | Benjamin Tissoires <benjamin.tissoires@redhat.com> | 2019-04-23 19:01:02 +0300 |
| commit | 74808f9115cee2bb53e7161432959f3e87b631e4 (patch) | |
| tree | 9e0d5416b6961af37062b101e5eee61310487151 /mm/gup_benchmark.c | |
| parent | b6aeeddef68deec9d603e455d163e3b41951f2d9 (diff) | |
| download | linux-74808f9115cee2bb53e7161432959f3e87b631e4.tar.xz | |
HID: logitech-dj: add support for non unifying receivers
We emulate the DJ functionality through the driver.
The receiver supports "fake device arrival" which behaves
like the probing of DJ devices.
A non-unifying receiver has 2 USB interfaces, the first one generates
standard keypresses and is compatible with the USB Keyboard Boot Subclass.
The second interface sends events for the mouse and special keys such as
the consumer-page keys. Events are split this way for BIOS / Windows /
generic-hid driver compatibility. This split does not actually match with
which device the event originate from, e.g. the consumer-page key events
originate from the keyboard but are delivered on the mouse interface.
To make sure the events are actually delivered to the dj_device
representing the originating device, we pick which dj_dev to forward
a "regular" input-report to based on the report-number, rather
then based on the originating interface.
Co-authored-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Diffstat (limited to 'mm/gup_benchmark.c')
0 files changed, 0 insertions, 0 deletions