All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nestor Lopez Casado <nlopezcasad@logitech.com>
To: "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, 4 Apr 2022 09:10:17 +0200	[thread overview]
Message-ID: <CAE7qMrrOU4-qZZh_YoDXS__Xhh2cCJsnnJ-G245_ENrEEp0e3g@mail.gmail.com> (raw)
In-Reply-To: <a2ccd37e20b210a1a35188c949d5658314a22c86.camel@archlinux.org>

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) "

-nestor


On Fri, Apr 1, 2022 at 6:08 PM Filipe Laíns <lains@archlinux.org> wrote:
>
> On Fri, 2022-04-01 at 06:44 -0300, Marcos Alano wrote:
> > Hello fellow developers!
> >
> > We are having a discussion about a question and I think we can get
> > help here. The discussion is
> > https://gitlab.freedesktop.org/upower/upower/-/issues/166#note_1322354
> > The problem is when we use a Logitech device, we get two discrepant
> > information about battery level, one from Bluetooth stack and another
> > one from HID++ module.
> > The question here is: what is the most precise information, so we can
> > deduplicate but keep the indicator precise?
> >
> > Thank you.
> >
>
> Hi Marcos,
>
> I think the battery reported by the HID++ driver should be more accurate in
> certain devices.
>
> CCing Nestor as he may be able to clarify this further.
>
> Cheers,
> Filipe Laíns

  reply	other threads:[~2022-04-04  7:10 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 [this message]
2022-04-04 10:12     ` Bastien Nocera
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=CAE7qMrrOU4-qZZh_YoDXS__Xhh2cCJsnnJ-G245_ENrEEp0e3g@mail.gmail.com \
    --to=nlopezcasad@logitech.com \
    --cc=lains@archlinux.org \
    --cc=linux-input@vger.kernel.org \
    --cc=marcoshalano@gmail.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.