linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: "Filipe Laíns" <lains@riseup.net>,
	"Jiri Kosina" <jikos@kernel.org>,
	"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org,
	"Nestor Lopez Casado" <nlopezcasad@logitech.com>
Subject: Re: [PATCH] HID: logitech-hidpp: Enable HID++ for all the Logitech Bluetooth devices
Date: Tue, 30 Aug 2022 13:37:12 +0200	[thread overview]
Message-ID: <3ddfd0be624f0ec6a56e4a8601c828b4513d2fe7.camel@hadess.net> (raw)
In-Reply-To: <4542beb149883ab5dfdcfd7f6bb4b516e5c1bcdb.camel@hadess.net>

On Thu, 2022-08-25 at 14:29 +0200, Bastien Nocera wrote:
> Probe for HID++ support over Bluetooth for all the Logitech Bluetooth
> devices. As Logitech doesn't have a list of Bluetooth devices that
> support HID++ over Bluetooth, probe every device. The HID++ driver
> will fall back to plain HID if the device does not support HID++.
> 
> Note that this change might cause upower to export 2 batteries for
> certain Bluetooth LE devices which export their battery information
> through the Bluetooth BATT profile. This particular bug is tracked
> at:
> https://gitlab.freedesktop.org/upower/upower/-/issues/166
> 
> Tested with a Logitech Signature M650 mouse, over Bluetooth
> 
> Signed-off-by: Bastien Nocera <hadess@hadess.net>
> ---
> 
> Note that I could not test whether the Harmony PS3 (handled in hid-
> sony.c)
> or DiNovo Edge keyboard (handled in hid-input.c) devices would
> correctly fallback
> to those drivers in that case.

The special case of the DiNovo Edge keyboard and Harmony remote should
be fixed in the v2 version.

      parent reply	other threads:[~2022-08-30 11:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 12:29 [PATCH] HID: logitech-hidpp: Enable HID++ for all the Logitech Bluetooth devices Bastien Nocera
2022-08-25 15:59 ` Nestor Lopez Casado
2022-08-25 16:27   ` Bastien Nocera
2022-08-25 20:47   ` Peter F. Patel-Schneider
2022-08-26 14:35     ` Bastien Nocera
2022-08-26 15:31       ` Peter F. Patel-Schneider
2022-08-26 15:37       ` Peter F. Patel-Schneider
2022-08-29 13:41         ` Bastien Nocera
2022-08-29 14:20           ` Peter F. Patel-Schneider
2022-08-29 11:52     ` Bastien Nocera
2022-08-29 13:45     ` Bastien Nocera
2022-08-29 14:01       ` Peter F. Patel-Schneider
2022-08-30 11:37 ` Bastien Nocera [this message]

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=3ddfd0be624f0ec6a56e4a8601c828b4513d2fe7.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=nlopezcasad@logitech.com \
    /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;
as well as URLs for NNTP newsgroup(s).