From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220722] Non existent battery reporting for a laptop with touchscreen MSI
Date: Mon, 23 Feb 2026 16:59:34 +0000 [thread overview]
Message-ID: <bug-220722-215701-1cIM1xMJZC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220722-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220722
--- Comment #13 from ggrundik@gmail.com ---
Best solution could have been to hotplug the stylus battery device when stylus
comes in range first time, but that would be quite a trick for the driver.
Less convenient solution could be to hide this battery readings, if stylus is
not in use. This is a userspace solution.
But current solution, to hide this battery always and from everyone, seems like
a worst one. At least there should be some override of this behavior apart of
recompiling the module.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-02-23 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 16:18 [Bug 220722] New: Non existent battery reporting for a laptop with touchscreen MSI bugzilla-daemon
2025-10-30 15:02 ` [Bug 220722] " bugzilla-daemon
2025-10-30 15:19 ` bugzilla-daemon
2025-10-30 15:38 ` bugzilla-daemon
2025-10-30 15:41 ` bugzilla-daemon
2025-10-30 15:41 ` bugzilla-daemon
2025-10-30 15:45 ` bugzilla-daemon
2025-10-30 15:47 ` bugzilla-daemon
2025-10-30 15:58 ` bugzilla-daemon
2025-10-30 20:05 ` bugzilla-daemon
2025-10-31 11:02 ` bugzilla-daemon
2026-02-22 13:54 ` bugzilla-daemon
2026-02-23 10:45 ` bugzilla-daemon
2026-02-23 16:43 ` bugzilla-daemon
2026-02-23 16:59 ` bugzilla-daemon [this message]
2026-02-23 17:12 ` bugzilla-daemon
2026-02-23 17:37 ` bugzilla-daemon
2026-02-23 18:31 ` bugzilla-daemon
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=bug-220722-215701-1cIM1xMJZC@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.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 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.