Re: [PATCH v1 2/2] HID: logitech-hidpp: Add Bluetooth Mouse M336/M337/M535 to unhandled_hidpp_devices[]
From: Bastien Nocera <hadess@hadess.net>
Date: 2022-12-07 09:29:40
Also in:
lkml
On Wed, 2022-12-07 at 10:12 +0100, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki <redacted> Evidently, Logitech Bluetooth Mouse M336/M337/M535 (0xb016) does not work when HID++ is enabled for it,
This needs the output of the hidpp-list-features tool mentioned earlier in the thread so we can avoid words like "evidently" and provide concrete proof. But why is it needed in this case? We purposefully try to avoid blanket blocklists. The lack of HID++ can be probed, so the device should work just as it used to (if the fallback code works). We should only list devices that need special handling, and the ones that don't work once HID++ was probed unsuccessfully.
quoted hunk ↗ jump to hunk
so add it to the list of devices that are not handled by logitech-hidpp. Fixes: 532223c8ac57 ("HID: logitech-hidpp: Enable HID++ for all the Logitech Bluetooth devices") Signed-off-by: Rafael J. Wysocki <redacted> --- drivers/hid/hid-logitech-hidpp.c | 1 + 1 file changed, 1 insertion(+) Index: linux-pm/drivers/hid/hid-logitech-hidpp.c ===================================================================--- linux-pm.orig/drivers/hid/hid-logitech-hidpp.c +++ linux-pm/drivers/hid/hid-logitech-hidpp.c@@ -4274,6 +4274,7 @@ static const struct hid_device_id unhand{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_HARMONY_PS3) }, /* Handled in hid-generic */ { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_DINOVO_EDGE_KBD) }, + { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH, 0xb016) }, {} };