From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-pm@vger.kernel.org, nicolopiazzalunga@gmail.com,
linrunner@gmx.net, platform-driver-x86@vger.kernel.org,
smclt30p@gmail.com
Subject: Re: [RFC v2] standardized attributes for powersupply charge behaviour
Date: Fri, 12 Nov 2021 19:10:42 +0100 [thread overview]
Message-ID: <20211112181042.jk63p5dm2ty3kxd5@earth.universe> (raw)
In-Reply-To: <20211108192852.357473-1-linux@weissschuh.net>
[-- Attachment #1: Type: text/plain, Size: 3703 bytes --]
Hi,
On Mon, Nov 08, 2021 at 08:28:52PM +0100, Thomas Weißschuh wrote:
> This a revised version of
> "[RFC] add standardized attributes for force_discharge and inhibit_charge" [0],
> incorporating discussion results.
>
> The biggest change is the switch from two boolean attributes to a single
> enum attribute.
>
> [0] https://lore.kernel.org/platform-driver-x86/21569a89-8303-8573-05fb-c2fec29983d1@gmail.com/
> ---
> Documentation/ABI/testing/sysfs-class-power | 14 ++++++++++++++
> drivers/power/supply/power_supply_sysfs.c | 1 +
> include/linux/power_supply.h | 7 +++++++
> 3 files changed, 22 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power
> index ca830c6cd809..2f58cfc91420 100644
> --- a/Documentation/ABI/testing/sysfs-class-power
> +++ b/Documentation/ABI/testing/sysfs-class-power
> @@ -455,6 +455,20 @@ Description:
> "Unknown", "Charging", "Discharging",
> "Not charging", "Full"
>
> +What: /sys/class/power_supply/<supply_name>/charge_behaviour
> +Date: November 2021
> +Contact: linux-pm@vger.kernel.org
> +Description:
> + Represents the charging behaviour.
> +
> + Access: Read, Write
> +
> + Valid values:
> + ================ ====================================
> + auto: Charge normally, respect thresholds
> + inhibit-charge: Do not charge while AC is attached
> + force-discharge: Force discharge while AC is attached
> +
> What: /sys/class/power_supply/<supply_name>/technology
> Date: May 2007
> Contact: linux-pm@vger.kernel.org
> diff --git a/drivers/power/supply/power_supply_sysfs.c b/drivers/power/supply/power_supply_sysfs.c
> index c3d7cbcd4fad..26c60587dca1 100644
> --- a/drivers/power/supply/power_supply_sysfs.c
> +++ b/drivers/power/supply/power_supply_sysfs.c
> @@ -172,6 +172,7 @@ static struct power_supply_attr power_supply_attrs[] = {
> POWER_SUPPLY_ATTR(CHARGE_CONTROL_LIMIT_MAX),
> POWER_SUPPLY_ATTR(CHARGE_CONTROL_START_THRESHOLD),
> POWER_SUPPLY_ATTR(CHARGE_CONTROL_END_THRESHOLD),
> + POWER_SUPPLY_ENUM_ATTR(CHARGE_BEHAVIOUR),
> POWER_SUPPLY_ATTR(INPUT_CURRENT_LIMIT),
> POWER_SUPPLY_ATTR(INPUT_VOLTAGE_LIMIT),
> POWER_SUPPLY_ATTR(INPUT_POWER_LIMIT),
this is missing (and should not compile without it):
static const char * const POWER_SUPPLY_CHARGE_BEHAVIOUR_TEXT[] = { ... };
Otherwise LGTM. But you need to send API changes with an API user (i.e. the
patch updating acpi battery driver using this).
-- Sebastian
> diff --git a/include/linux/power_supply.h b/include/linux/power_supply.h
> index 9ca1f120a211..70c333e86293 100644
> --- a/include/linux/power_supply.h
> +++ b/include/linux/power_supply.h
> @@ -132,6 +132,7 @@ enum power_supply_property {
> POWER_SUPPLY_PROP_CHARGE_CONTROL_LIMIT_MAX,
> POWER_SUPPLY_PROP_CHARGE_CONTROL_START_THRESHOLD, /* in percents! */
> POWER_SUPPLY_PROP_CHARGE_CONTROL_END_THRESHOLD, /* in percents! */
> + POWER_SUPPLY_PROP_CHARGE_BEHAVIOUR,
> POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT,
> POWER_SUPPLY_PROP_INPUT_VOLTAGE_LIMIT,
> POWER_SUPPLY_PROP_INPUT_POWER_LIMIT,
> @@ -202,6 +203,12 @@ enum power_supply_usb_type {
> POWER_SUPPLY_USB_TYPE_APPLE_BRICK_ID, /* Apple Charging Method */
> };
>
> +enum power_supply_charge_behaviour {
> + POWER_SUPPLY_CHARGE_BEHAVIOUR_AUTO = 0,
> + POWER_SUPPLY_CHARGE_BEHAVIOUR_INHIBIT_CHARGE,
> + POWER_SUPPLY_CHARGE_BEHAVIOUR_FORCE_DISCHARGE,
> +};
> +
> enum power_supply_notifier_events {
> PSY_EVENT_PROP_CHANGED,
> };
>
> base-commit: 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f
> --
> 2.33.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-11-12 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 19:28 [RFC v2] standardized attributes for powersupply charge behaviour Thomas Weißschuh
2021-11-11 9:53 ` Hans de Goede
2021-11-12 18:10 ` Sebastian Reichel [this message]
2021-11-12 18:26 ` 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=20211112181042.jk63p5dm2ty3kxd5@earth.universe \
--to=sebastian.reichel@collabora.com \
--cc=linrunner@gmx.net \
--cc=linux-pm@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=nicolopiazzalunga@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=smclt30p@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).