Linux Power Management development
 help / color / mirror / Atom feed
From: Jelle van der Waa <jvanderw@redhat.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Hans de Goede" <hdegoede@redhat.com>,
	linux-pm@vger.kernel.org,
	"Jelle van der Waa" <jvanderwaa@redhat.com>
Subject: [PATCH 0/1] support charge_types in the extensions API
Date: Mon,  7 Apr 2025 22:18:44 +0200	[thread overview]
Message-ID: <20250407201845.332348-1-jvanderw@redhat.com> (raw)

From: Jelle van der Waa <jvanderwaa@redhat.com>

The goal of this patch is to make it possible for the ideapad-laptop
driver to move from its custom conservation_mode sysfs attribute to the
standardised charge_types sysfs attribute with a power_supply extension.
Along with other laptop models which support an end charge threshold
which limits it to a fixed value such as some Toshiba and LG models.

User space, in this case UPower would then be detect 'Long Life' as
charge_types option and set it.

This patch should also allow the "dell-laptop" driver to move over to
the extensions API.

Jelle van der Waa (1):
  power: supply: support charge_types in extensions

 drivers/power/supply/power_supply_sysfs.c | 23 ++++++++++++++++++++++-
 drivers/power/supply/test_power.c         | 20 ++++++++++++++++++--
 include/linux/power_supply.h              |  1 +
 3 files changed, 41 insertions(+), 3 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-04-07 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 20:18 Jelle van der Waa [this message]
2025-04-07 20:18 ` [PATCH 1/1] power: supply: support charge_types in extensions Jelle van der Waa
2025-04-08  8:07   ` Hans de Goede
2025-04-08 23:03   ` kernel test robot
2025-04-09  2:11   ` kernel test robot

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=20250407201845.332348-1-jvanderw@redhat.com \
    --to=jvanderw@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=jvanderwaa@redhat.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=sre@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