From: Nicholas Miell <hidden> Date: 2021-01-11 06:10:09
The Logitech MX Ergo trackball supports HID++ 4.5 over Bluetooth. Add its
product ID to the table so we can get battery monitoring support.
(The hid-logitech-hidpp driver already recognizes it when connected via
a Unifying Receiver.)
Signed-off-by: Nicholas Miell <redacted>
---
drivers/hid/hid-logitech-hidpp.c | 2 ++
1 file changed, 2 insertions(+)
@@ -4053,6 +4053,8 @@ static const struct hid_device_id hidpp_devices[] = {{/* MX Master mouse over Bluetooth */HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH,0xb012),.driver_data=HIDPP_QUIRK_HI_RES_SCROLL_X2121},+{/* MX Ergo trackball over Bluetooth */+HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH,0xb01d)},{HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH,0xb01e),.driver_data=HIDPP_QUIRK_HI_RES_SCROLL_X2121},{/* MX Master 3 mouse over Bluetooth */
From: Hans de Goede <hidden> Date: 2021-01-11 10:52:13
Hi,
On 1/11/21 7:09 AM, Nicholas Miell wrote:
The Logitech MX Ergo trackball supports HID++ 4.5 over Bluetooth. Add its
product ID to the table so we can get battery monitoring support.
(The hid-logitech-hidpp driver already recognizes it when connected via
a Unifying Receiver.)
Signed-off-by: Nicholas Miell <redacted>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <redacted>
Regards,
Hans
@@ -4053,6 +4053,8 @@ static const struct hid_device_id hidpp_devices[] = {{/* MX Master mouse over Bluetooth */HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH,0xb012),.driver_data=HIDPP_QUIRK_HI_RES_SCROLL_X2121},+{/* MX Ergo trackball over Bluetooth */+HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH,0xb01d)},{HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH,0xb01e),.driver_data=HIDPP_QUIRK_HI_RES_SCROLL_X2121},{/* MX Master 3 mouse over Bluetooth */
The Logitech MX Ergo trackball supports HID++ 4.5 over Bluetooth. Add its
product ID to the table so we can get battery monitoring support.
(The hid-logitech-hidpp driver already recognizes it when connected via
a Unifying Receiver.)
Signed-off-by: Nicholas Miell <redacted>
Thanks for the patch. It was whitespace damaged by your mail client
though. I've fixed it manually and applied, but please look into fixing
this for any future patch submissions.
--
Jiri Kosina
SUSE Labs