X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216176] ideapad-laptop doesn't expose rapid charge
Date: Mon, 27 Jun 2022 19:47:59 +0000	[thread overview]
Message-ID: <bug-216176-215701-vrvFSou6Ab@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216176-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216176

--- Comment #4 from tinozzo123@tutanota.com ---
My take on where it should be exposed.

Something related to the battery, which are charge thresholds, are supported in
multiple laptop brands (Lenovo ThinkPad, ASUS, System76...) and are thus are
exposed in the battery power supply device
(/sys/class/power_supply/BAT0/charge_control_{start,end}_threshold)

conservation_mode is basically an equivalent with a fixed value (60%) that is
exclusive to IdeaPads, and it's exposed in the platform device
(/sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode).

I guess that my the verdict is that, because rapid charging is supported on
multiple laptop series (both ThinkPads and IdeaPads, which use different
drivers, and maybe there are more brands, though I couldn't find anything on
Google), so it should be exposed in the battery power supply device.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-06-27 19:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 15:56 [Bug 216176] New: ideapad-laptop doesn't expose rapid charge bugzilla-daemon
2022-06-26 19:34 ` [Bug 216176] " bugzilla-daemon
2022-06-26 19:44 ` bugzilla-daemon
2022-06-27 13:49 ` bugzilla-daemon
2022-06-27 19:47 ` bugzilla-daemon [this message]
2022-06-29 19:49 ` bugzilla-daemon
2022-06-29 20:04 ` bugzilla-daemon
2022-06-29 21:10 ` bugzilla-daemon
2022-09-19  9:07 ` bugzilla-daemon
2023-07-20 21:16 ` bugzilla-daemon
2024-02-06 14:34 ` 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-216176-215701-vrvFSou6Ab@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