From: Dmitry Torokhov <dtor@google.com>
To: Hans de Goede <hansg@kernel.org>
Cc: "Jiri Kosina" <jikos@kernel.org>,
"Mario Limonciello (AMD)" <superm1@kernel.org>,
mario.limonciello@amd.com, bentiss@kernel.org,
"André Barata" <andretiagob@protonmail.com>,
linux-input@vger.kernel.org,
"Kenneth Albanowski" <kenalba@google.com>
Subject: Re: [PATCH] HID: hid-input: Extend Elan ignore battery quirk to USB
Date: Thu, 6 Nov 2025 11:10:38 -0800 [thread overview]
Message-ID: <CAE_wzQ8U5mKgWvquM7BZeKcb4VxORK6DSaUsxoAnfZ9qQgHoRw@mail.gmail.com> (raw)
In-Reply-To: <CAE_wzQ_YvCh8a83mm3QG7LwMWo2CKEAMvRS7+CpJcq1r7MEBZA@mail.gmail.com>
On Fri, Oct 31, 2025 at 7:47 AM Dmitry Torokhov <dtor@google.com> wrote:
>
> Hi Hans,
>
> On Fri, Oct 31, 2025 at 2:13 AM Hans de Goede <hansg@kernel.org> wrote:
> >
> > Hi Jiri,
> >
> > On 31-Oct-25 10:07 AM, Jiri Kosina wrote:
> > > On Thu, 30 Oct 2025, Mario Limonciello (AMD) wrote:
> > >
> > >> USB Elan devices have the same problem as the I2C ones with a fake
> > >> battery device showing up.
> > >>
> > >> Reviewed-by: Hans de Goede <hansg@kernel.org>
> > >> Reported-by: André Barata <andretiagob@protonmail.com>
> > >> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220722
> > >> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
> > >
> > > Now applied.
> > >
> > > We'll have to come up with something more sophisticated once/if Elan ever
> > > starts producing devices with real battery ...
> >
> > Actually the provided HID battery is intended to be for
> > when a stylus is used and to report the stylus battery
> > values then.
> >
> > There is an email thread somewhere with some of the ChromeOS folks
> > talking about dropping the ELAN quirk for I2C touchscreens and
> > indeed replacing it with something more sophisticated. IIRC
> > the ChromeOS folks mentioned they would work on / provide patches.
> >
> > +To: Dmitry, Dmitry do you have any input on the ChromeOs issue ?
>
> +Kenneth Albanowski has been wrangling with support of Elan and other
> vendor styli, I'll let him comment.
Kenneth is currently busy with some internal projects and asked me to
pass the following:
We recommend that userspace components do not generate alerts for
power supplies that report "status" as "unknown". For a lot of styli
we start with "unknown" and 0 level until after we get a first real
report and update the state to "discharging" or "full" and only hen we
may start showing the indicator.
On ChromeOS we also have tech for clarifying "1%" and other bad
reports, currently specific to USI styluses using a S/N filter.
Kenneth will try to share more details next week hopefully.
Thanks,
Dmitry
prev parent reply other threads:[~2025-11-06 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 16:06 [PATCH] HID: hid-input: Extend Elan ignore battery quirk to USB Mario Limonciello (AMD)
2025-10-31 9:07 ` Jiri Kosina
2025-10-31 9:13 ` Hans de Goede
2025-10-31 14:47 ` Dmitry Torokhov
2025-11-06 19:10 ` Dmitry Torokhov [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=CAE_wzQ8U5mKgWvquM7BZeKcb4VxORK6DSaUsxoAnfZ9qQgHoRw@mail.gmail.com \
--to=dtor@google.com \
--cc=andretiagob@protonmail.com \
--cc=bentiss@kernel.org \
--cc=hansg@kernel.org \
--cc=jikos@kernel.org \
--cc=kenalba@google.com \
--cc=linux-input@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=superm1@kernel.org \
/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).