From: Jelle van der Waa <jvanderw@redhat.com>
To: "Armin Wolf" <W_Armin@gmx.de>,
"Jelle van der Waa" <jvanderw@redhat.com>,
"Ike Panhc" <ikepanhc@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/1] platform/x86: ideapad: Expose charge_types
Date: Tue, 13 May 2025 10:38:04 +0200 [thread overview]
Message-ID: <e6cbd30b-5e97-49ba-9f62-2e7e1fe835fc@redhat.com> (raw)
In-Reply-To: <964a9e0b-8901-4f50-a725-9f841fa6914d@gmx.de>
On 5/12/25 00:54, Armin Wolf wrote:
> Am 11.05.25 um 13:30 schrieb Jelle van der Waa:
>
>> From: Jelle van der Waa <jvanderwaa@redhat.com>
>>
>> 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.
>>
>> Tested on an Lenovo ideapad U330p.
>
> Hi,
>
> i like the idea behind this patch series, the charge_types attribute is
> indeed
> exactly what we need in this case.
Thanks! Credit where credit is due, this idea came from Hans de Goede
(who also added charge_types). I only wrote the code.
>> ---
>> .../ABI/testing/sysfs-platform-ideapad-laptop | 2 +
>> drivers/platform/x86/ideapad-laptop.c | 126 +++++++++++++++++-
>> 2 files changed, 125 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop
>> b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop
>> index 4989ab266682..83eca4c14503 100644
>> --- a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop
>> +++ b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop
>> @@ -32,6 +32,8 @@ Date: Aug 2017
>> KernelVersion: 4.14
>> Contact: platform-driver-x86@vger.kernel.org
>> Description:
>> + This interface is deprecated; please use /sys/class/
>> power_supply/*/charge_types.
>> +
>
> Maybe it would make sense to move this attribute to Documentation/ABI/
> obsolete?
I am not sure what the normal workflow is so I've applied this
suggestion in v2.
>> + void *ext_data,
>> + enum power_supply_property psp,
>> + const union power_supply_propval *val)
>> +{
>> + struct ideapad_private *priv = ext_data;
>> + int err;
>> +
>> + if (psp != POWER_SUPPLY_PROP_CHARGE_TYPES)
>> + return -EINVAL;
>> +
>> + err = exec_sbmc(priv->adev->handle,
>> + (val->intval == POWER_SUPPLY_CHARGE_TYPE_LONGLIFE ?
>> + SBMC_CONSERVATION_ON : SBMC_CONSERVATION_OFF));
>
> AFAIK the power supply core does not check if val->intval holds a
> supported charge type value.
> Please use a switch case to return -EINVAL in such cases.
From my testing checking val->intval wasn't needed, you'll get an
"write error: invalid argument" when trying to set "Long lifeee".
I believe that is handled in power_supply_store_property, but reading
the code I don't really believe that's true? So I've simply switched it
over to a switch/case.
Thanks,
Jelle
next prev parent reply other threads:[~2025-05-13 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 11:30 [PATCH 0/1] platform/x86: ideapad: Expose charge_types Jelle van der Waa
2025-05-11 11:30 ` [PATCH 1/1] " Jelle van der Waa
2025-05-11 22:54 ` Armin Wolf
2025-05-13 8:38 ` Jelle van der Waa [this message]
2025-05-14 10:24 ` Ilpo Järvinen
2025-05-12 6:53 ` Thomas Weißschuh
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=e6cbd30b-5e97-49ba-9f62-2e7e1fe835fc@redhat.com \
--to=jvanderw@redhat.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ikepanhc@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--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