From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 215531] Lenovo charge limit feature stops 1% short of the configured limit and says it's still charging
Date: Mon, 14 Feb 2022 09:41:53 +0000 [thread overview]
Message-ID: <bug-215531-215701-enHsJIPdRI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215531-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215531
Hans de Goede (jwrdegoede@fedoraproject.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jwrdegoede@fedoraproject.or
| |g
Resolution|--- |CODE_FIX
--- Comment #1 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
This has been fixed in kernels >= 5.16.3 with this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e96c1197aca628f7d2480a1cc3214912b40b3414
With these kernels:
cat /sys/class/power_supply/BAT0/status
Will now output "not charging" under these conditions. This is what the
device's firmware gives us, so this is the best the kernel can do. Translating
"not charging" + the capacity in % being more or less equal to the
charge_control_end_threshold(1) value to "full" is something for userspace
(upower) to sort out. Since we are looking on adding UI options to set
charge_control_end_threshold, it would be good if we can get upower reporting
"full" under these conditions.
Note the upower issue should be re-opened to track this.
--
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:[~2022-02-14 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215531-215701@https.bugzilla.kernel.org/>
2022-02-14 6:42 ` [Bug 215531] Lenovo charge limit feature stops 1% short of the configured limit and says it's still charging bugzilla-daemon
2022-02-14 9:41 ` bugzilla-daemon [this message]
2022-02-14 18:30 ` bugzilla-daemon
2022-02-14 20:02 ` bugzilla-daemon
2022-02-14 20:11 ` bugzilla-daemon
2022-02-14 20:17 ` bugzilla-daemon
2022-02-14 21:17 ` 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-215531-215701-enHsJIPdRI@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox