From: Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
To: <sre@kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Cc: Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
Subject: [PATCH v3 3/3] ABI: testing: sysfs-class-power: Adds "Long Life" entry
Date: Mon, 14 Feb 2022 18:07:58 -0600 [thread overview]
Message-ID: <20220215000758.803501-4-rriveram@opensource.cirrus.com> (raw)
In-Reply-To: <20220215000758.803501-1-rriveram@opensource.cirrus.com>
Adds a brief desciption of the "Long Life" charge type and adds "Long Life"
to the list of valid values.
Signed-off-by: Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
---
Documentation/ABI/testing/sysfs-class-power | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power
index 8e3bf1aa6268..b304fa9c1482 100644
--- a/Documentation/ABI/testing/sysfs-class-power
+++ b/Documentation/ABI/testing/sysfs-class-power
@@ -380,16 +380,17 @@ Description:
algorithm to adjust the charge rate dynamically, without
any user configuration required. "Custom" means that the charger
uses the charge_control_* properties as configuration for some
- different algorithm. "Bypass" means the charger bypasses the
- charging path around the integrated converter allowing for a
- "smart" wall adaptor to perform the power conversion
- externally.
+ different algorithm. "Long Life" means the charger reduces its
+ charging rate in order to prolong the battery health. "Bypass"
+ means the charger bypasses the charging path around the
+ integrated converter allowing for a "smart" wall adaptor to
+ perform the power conversion externally.
Access: Read, Write
Valid values:
"Unknown", "N/A", "Trickle", "Fast", "Standard",
- "Adaptive", "Custom", "Bypass"
+ "Adaptive", "Custom", "Long Life", "Bypass"
What: /sys/class/power_supply/<supply_name>/charge_term_current
Date: July 2014
--
2.25.1
next prev parent reply other threads:[~2022-02-15 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 0:07 [PATCH v3 0/3] Introduces bypass charge type property Ricardo Rivera-Matos
2022-02-15 0:07 ` [PATCH v3 1/3] power: supply: Introduces bypass charging property Ricardo Rivera-Matos
2022-02-15 0:07 ` [PATCH v3 2/3] power: supply: bq25980: Implements POWER_SUPPLY_CHARGE_TYPE_BYPASS Ricardo Rivera-Matos
2022-02-15 0:07 ` Ricardo Rivera-Matos [this message]
2022-02-24 11:15 ` [PATCH v3 0/3] Introduces bypass charge type property Sebastian Reichel
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=20220215000758.803501-4-rriveram@opensource.cirrus.com \
--to=rriveram@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--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
all inboxes | Powered by JetHome®