From: Bastien Nocera <hadess@hadess.net>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Jiri Kosina" <jikos@kernel.org>,
"Filipe Laíns" <lains@riseup.net>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Thorsten Leemhuis" <regressions@leemhuis.info>
Subject: Re: [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8)
Date: Wed, 07 Dec 2022 10:58:53 +0100 [thread overview]
Message-ID: <8281ddcc16cc950f9cde4b196cf208adcc798319.camel@hadess.net> (raw)
In-Reply-To: <CAJZ5v0ic+pm+NWD8g4O2MwQEvi+xuB-W9Wpd6c1RhprhoxuK1g@mail.gmail.com>
On Wed, 2022-12-07 at 10:36 +0100, Rafael J. Wysocki wrote:
> On Wed, Dec 7, 2022 at 10:16 AM Rafael J. Wysocki <rjw@rjwysocki.net>
> wrote:
> >
> > On Wednesday, December 7, 2022 10:04:43 AM CET Bastien Nocera
> > wrote:
> > > On Tue, 2022-12-06 at 15:58 +0100, Rafael J. Wysocki wrote:
> > > > Bastien, Jiri,
> > > >
> > > > Commit 532223c8ac57 ("HID: logitech-hidpp: Enable HID++ for all
> > > > the
> > > > Logitech
> > > > Bluetooth devices") caused my Logitech Bluetooth mouse to
> > > > become
> > > > unusable.
> > > >
> > > > Appended is the change I need to make it work again (note that
> > > > adding
> > > > the
> > > > device ID to unhandled_hidpp_devices[] doesn't help, so there
> > > > must be
> > > > some
> > > > significant enough difference in how the two cases are handled
> > > > in the
> > > > stack).
> > > >
> > > > Here's what I get in the log without the patch below:
> > > >
> > > > [ 36.710574] Bluetooth: HIDP (Human Interface Emulation) ver
> > > > 1.2
> > > > [ 36.710592] Bluetooth: HIDP socket layer initialized
> > > > [ 36.724644] hid-generic 0005:046D:B016.0001: unknown main
> > > > item tag
> > > > 0x0
> > > > [ 36.725860] input: Bluetooth Mouse M336/M337/M535 Mouse as
> > > > /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-
> > > > 7:1.0/bluetooth/hci0/hci0:1/0005:046D:B016.0001/input/input14
> > > > [ 36.728036] input: Bluetooth Mouse M336/M337/M535 Consumer
> > > > Control
> > > > as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-
> > > > 7:1.0/bluetooth/hci0/hci0:1/0005:046D:B016.0001/input/input15
> > > > [ 36.728823] input: Bluetooth Mouse M336/M337/M535 Keyboard
> > > > as
> > > > /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-
> > > > 7:1.0/bluetooth/hci0/hci0:1/0005:046D:B016.0001/input/input18
> > > > [ 36.731550] hid-generic 0005:046D:B016.0001: input,hidraw0:
> > > > BLUETOOTH HID v12.03 Mouse [Bluetooth Mouse M336/M337/M535] on
> > > > 9c:b6:d0:96:8e:c8
> > > > [ 36.833039] logitech-hidpp-device 0005:046D:B016.0001:
> > > > unknown
> > > > main item tag 0x0
> > > > [ 36.999064] logitech-hidpp-device 0005:046D:B016.0001:
> > > > Device not
> > > > connected
> > > >
> > > > and here's what I get with it:
> > > >
> > > > [ 43.642546] Bluetooth: HIDP (Human Interface Emulation) ver
> > > > 1.2
> > > > [ 43.642559] Bluetooth: HIDP socket layer initialized
> > > > [ 43.652898] hid-generic 0005:046D:B016.0001: unknown main
> > > > item tag
> > > > 0x0
> > > > [ 43.653833] input: Bluetooth Mouse M336/M337/M535 Mouse as
> > > > /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-
> > > > 7:1.0/bluetooth/hci0/hci0:1/0005:046D:B016.0001/input/input14
> > > > [ 43.655025] input: Bluetooth Mouse M336/M337/M535 Consumer
> > > > Control
> > > > as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-
> > > > 7:1.0/bluetooth/hci0/hci0:1/0005:046D:B016.0001/input/input15
> > > > [ 43.655400] input: Bluetooth Mouse M336/M337/M535 Keyboard
> > > > as
> > > > /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-
> > > > 7:1.0/bluetooth/hci0/hci0:1/0005:046D:B016.0001/input/input18
> > > > [ 43.657521] hid-generic 0005:046D:B016.0001: input,hidraw0:
> > > > BLUETOOTH HID v12.03 Mouse [Bluetooth Mouse M336/M337/M535] on
> > > > 9c:b6:d0:96:8e:c8
> > > >
> > > > The only difference seems to be that in the former case the
> > > > logitech-
> > > > hidpp
> > > > driver tries to bind to the device, but I guess that is
> > > > expected.
> > >
> > > There really shouldn't be that much difference between the 2
> > > paths,
> > > except that hid-logitech-hidpp.c will check that the device
> > > supports
> > > HID++ in its report descriptors, and then start talking to it to
> > > check
> > > whether it's connected.
> > >
> > > Maybe the device doesn't support HID++?
> >
> > Quite possibly.
> >
> > > Can you try running src/tools/hidpp-list-features from
> > > https://github.com/cvuchener/hidpp on the hidraw device for the
> > > mouse?
> >
> > OK, I'll do that.
>
> Well, I would if I had a binary.
>
> Otherwise, I have cmake 3.17 which apparently is too old, sorry.
Revert 308f240585380dd0af4d9f5bbec5eb01e103deca and it will just
require 3.12.
Or use Solaar from your distribution or one of the prebuilt packages
(https://github.com/pwr-Solaar/Solaar/#prebuilt-packages):
solaar -D /dev/hidrawX show
next prev parent reply other threads:[~2022-12-07 9:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 14:58 [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8) Rafael J. Wysocki
2022-12-07 8:58 ` Rafael J. Wysocki
2022-12-07 9:07 ` Bastien Nocera
2022-12-07 9:04 ` Bastien Nocera
2022-12-07 9:16 ` Rafael J. Wysocki
2022-12-07 9:36 ` Rafael J. Wysocki
2022-12-07 9:58 ` Bastien Nocera [this message]
2022-12-07 10:07 ` Rafael J. Wysocki
2022-12-07 10:50 ` Bastien Nocera
2022-12-07 11:07 ` Rafael J. Wysocki
2022-12-07 17:19 ` Bastien Nocera
2022-12-07 17:44 ` Rafael J. Wysocki
2022-12-08 15:20 ` Bastien Nocera
2022-12-13 16:14 ` Bastien Nocera
2022-12-15 15:09 ` Rafael J. Wysocki
2022-12-07 9:10 ` [PATCH v1 0/2] HID: Fix regression resulting from commit 532223c8ac57 Rafael J. Wysocki
2022-12-07 9:11 ` [PATCH v1 1/2] HID: generic: Add ->match() check to __check_hid_generic() Rafael J. Wysocki
2022-12-07 9:27 ` Benjamin Tissoires
2022-12-07 9:54 ` Rafael J. Wysocki
2022-12-07 9:12 ` [PATCH v1 2/2] HID: logitech-hidpp: Add Bluetooth Mouse M336/M337/M535 to unhandled_hidpp_devices[] Rafael J. Wysocki
2022-12-07 9:29 ` Bastien Nocera
2022-12-07 9:47 ` Rafael J. Wysocki
2022-12-07 9:59 ` Bastien Nocera
2022-12-07 10:05 ` Benjamin Tissoires
2022-12-07 10:11 ` Rafael J. Wysocki
2022-12-07 10:19 ` Jiri Kosina
2022-12-07 12:43 ` Bastien Nocera
2022-12-07 13:00 ` Rafael J. Wysocki
2022-12-07 13:24 ` Benjamin Tissoires
2022-12-07 13:39 ` Rafael J. Wysocki
2022-12-07 14:24 ` Bastien Nocera
2022-12-08 13:32 ` Benjamin Tissoires
2022-12-07 9:48 ` Benjamin Tissoires
2022-12-07 9:59 ` Bastien Nocera
2022-12-08 7:03 ` [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8) #forregzbot Thorsten Leemhuis
2022-12-09 6:34 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8281ddcc16cc950f9cde4b196cf208adcc798319.camel@hadess.net \
--to=hadess@hadess.net \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox