From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ike Panhc <ikepanhc@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
Jelle van der Waa <jvanderwaa@redhat.com>
Cc: platform-driver-x86@vger.kernel.org,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Armin Wolf" <W_Armin@gmx.de>
Subject: Re: [PATCH v3] platform/x86: ideapad: Expose charge_types
Date: Wed, 21 May 2025 14:16:06 +0300 [thread overview]
Message-ID: <174782616614.1966.2869615592949298081.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250514201054.381320-1-jvanderwaa@redhat.com>
On Wed, 14 May 2025 22:10:52 +0200, Jelle van der Waa wrote:
> Some Ideapad models support a battery conservation mode which limits the
> battery charge threshold for longer battery longevity. This is currently
> exposed via a custom conservation_mode attribute in sysfs.
>
> The newly introduced charge_types sysfs attribute is a standardized
> replacement for laptops with a fixed end charge threshold. Setting it to
> `Long Life` would enable battery conservation mode. The standardized
> user space API would allow applications such as UPower to detect laptops
> which support this battery longevity mode and set it.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86: ideapad: Expose charge_types
commit: b2012b38080e2f92d43eca59e8249c174a27527c
--
i.
next prev parent reply other threads:[~2025-05-21 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 20:10 [PATCH v3] platform/x86: ideapad: Expose charge_types Jelle van der Waa
2025-05-21 11:16 ` Ilpo Järvinen [this message]
2025-06-09 9:46 ` Ilpo Järvinen
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=174782616614.1966.2869615592949298081.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ikepanhc@gmail.com \
--cc=jvanderwaa@redhat.com \
--cc=linux@weissschuh.net \
--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