diff options
| author | Benjamin Tissoires <benjamin.tissoires@redhat.com> | 2022-12-07 17:24:33 +0300 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2022-12-08 22:18:11 +0300 |
| commit | a9d9e46c755a189ccb44d91b8cf737742a975de8 (patch) | |
| tree | f9f314b58c1f5c9858293e7b4569a333919994a4 /drivers/gpu/drm/amd/pm/swsmu/smu13/aldebaran_ppt.c | |
| parent | 40f2432b53a01b6d5e3a9057f1d5c406930e1360 (diff) | |
| download | linux-a9d9e46c755a189ccb44d91b8cf737742a975de8.tar.xz | |
Revert "HID: logitech-hidpp: Enable HID++ for all the Logitech Bluetooth devices"
This reverts commit 532223c8ac57605a10e46dc0ab23dcf01c9acb43.
As reported in [0], hid-logitech-hidpp now binds on all bluetooth mice,
but there are corner cases where hid-logitech-hidpp just gives up on
the mouse. This leads the end user with a dead mouse.
Given that we are at -rc8, we are definitively too late to find a proper
fix. We already identified 2 issues less than 24 hours after the bug
report. One in that ->match() was never designed to be used anywhere else
than in hid-generic, and the other that hid-logitech-hidpp has corner
cases where it gives up on devices it is not supposed to.
So we have no choice but postpone this patch to the next kernel release.
[0] https://lore.kernel.org/linux-input/CAJZ5v0g-_o4AqMgNwihCb0jrwrcJZfRrX=jv8aH54WNKO7QB8A@mail.gmail.com/
Reported-by: Rafael J . Wysocki <rjw@rjwysocki.net>
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/gpu/drm/amd/pm/swsmu/smu13/aldebaran_ppt.c')
0 files changed, 0 insertions, 0 deletions