From: Bastien Nocera <hadess@hadess.net>
To: "Nestor Lopez Casado" <nlopezcasad@logitech.com>,
"Filipe Laíns" <lains@archlinux.org>
Cc: Marcos Alano <marcoshalano@gmail.com>,
HID CORE LAYER <linux-input@vger.kernel.org>
Subject: Re: Battery indication for Logitech devices
Date: Mon, 04 Apr 2022 12:12:36 +0200 [thread overview]
Message-ID: <e987204d78c42ab3811d139daef43f9f31e65092.camel@hadess.net> (raw)
In-Reply-To: <CAE7qMrrOU4-qZZh_YoDXS__Xhh2cCJsnnJ-G245_ENrEEp0e3g@mail.gmail.com>
On Mon, 2022-04-04 at 09:10 +0200, Nestor Lopez Casado wrote:
> Hello,
>
> I've got this from asking internally:
>
> " The information should be accurate in both BAS and HIDPP
> interfaces.
> However, today the BAS interface is limited. Version 2.0 will be
> better but not yet released. As you have access to the HIDPP, I
> recommend using only this one. Like this, the type of connection can
> be ignored (BLE or USB dongle) "
As per the patch I just sent (HID: logitech-hidpp: Add Signature M650),
it will unfortunately be difficult to disable the battery reporting
directly from bluetoothd.
We can detect whether a Bluetooth device supports HID++, as it has a
GATT attribute with a Logitech specific UUID[1] (more info/specs
welcome), but not all the HID++ capable Bluetooth devices seem to be
detected by the kernel and they need to be added to a list.
Ideally, the kernel could enable HID++ support for all the Bluetooth
HID++-capable devices, and we could easily block reporting in upower or
bluetoothd without having to care at runtime about whether there's a
separate battery reporting interface because we could assume it was
always there.
Any ideas on how to do that?
[1]:
Device DE:1D:F3:3B:E4:B0 (random)
Name: Logi M650
Alias: Logi M650
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: no
WakeAllowed: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Logitech International SA (0000fd72-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
Modalias: usb:v046DpB02Ad0009
ManufacturerData Key: 0x0006
ManufacturerData Value:
03 00 80 ...
ServiceData Key: 0000fd72-0000-1000-8000-00805f9b34fb
ServiceData Value:
10 01 01 2a b0 02 02 09 ...*....
next prev parent reply other threads:[~2022-04-04 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:44 Battery indication for Logitech devices Marcos Alano
2022-04-01 16:08 ` Filipe Laíns
2022-04-04 7:10 ` Nestor Lopez Casado
2022-04-04 10:12 ` Bastien Nocera [this message]
2022-05-02 17:05 ` marcoshalano
2022-05-23 11:46 ` Bastien Nocera
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=e987204d78c42ab3811d139daef43f9f31e65092.camel@hadess.net \
--to=hadess@hadess.net \
--cc=lains@archlinux.org \
--cc=linux-input@vger.kernel.org \
--cc=marcoshalano@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.