From: Nicolo' Piazzalunga <nicolopiazzalunga@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: jwrdegoede@fedoraproject.org, smclt30p@gmail.com, linrunner@gmx.net
Subject: [PATCH 3/3] thinkpad_acpi: document force_discharge and, inhibit_charge
Date: Wed, 17 Mar 2021 15:05:37 +0100 [thread overview]
Message-ID: <05bb641c-0390-bbd6-56bf-4871e65e4f20@gmail.com> (raw)
Describe the additional sysfs attributes for
forced discharging and charge inhibiting.
Improve description of charge_control_{start,end}_threshold.
Signed-off-by: Ognjen Galic <smclt30p@gmail.com>
Signed-off-by: Thomas Koch <linrunner@gmx.net>
Signed-off-by: Nicolo' Piazzalunga <nicolopiazzalunga@gmail.com>
---
.../admin-guide/laptops/thinkpad-acpi.rst | 30 +++++++++++++++----
1 file changed, 25 insertions(+), 5 deletions(-)
diff --git a/Documentation/admin-guide/laptops/thinkpad-acpi.rst b/Documentation/admin-guide/laptops/thinkpad-acpi.rst
index 5e477869df18..e71bc74d69dc 100644
--- a/Documentation/admin-guide/laptops/thinkpad-acpi.rst
+++ b/Documentation/admin-guide/laptops/thinkpad-acpi.rst
@@ -1493,15 +1493,35 @@ sysfs attributes:
These two attributes are created for those batteries that are supported by the
driver. They enable the user to control the battery charge thresholds of the
-given battery. Both values may be read and set. `charge_control_start_threshold`
-accepts an integer between 0 and 99 (inclusive); this value represents a battery
-percentage level, below which charging will begin. `charge_control_end_threshold`
-accepts an integer between 1 and 100 (inclusive); this value represents a battery
-percentage level, above which charging will stop.
+given battery. Both values may be read and set.
+
+`charge_control_start_threshold` accepts an integer between 0 and 99 (inclusive).
+This value represents the battery percentage level below which charging will begin.
+
+`charge_control_end_threshold` accepts an integer between 1 and 100 (inclusive).
+This value represents the battery percentage level where charging will stop.
The exact semantics of the attributes may be found in
Documentation/ABI/testing/sysfs-class-power.
+Battery forced discharging
+--------------------------
+
+sysfs attribute:
+/sys/class/power_supply/BATx/force_discharge
+
+Setting this attribute to 1 forces the battery to discharge while AC is attached.
+Setting it to 0 terminates forced discharging.
+
+Battery charge inhibiting
+--------------------------
+
+sysfs attribute:
+/sys/class/power_supply/BATx/inhibit_discharge
+
+Setting this attribute to 1 stops charging of the battery as a manual override
+over the threshold attributes. Setting it to 0 terminates the override.
+
Multiple Commands, Module Parameters
------------------------------------
--
2.25.1
reply other threads:[~2021-03-17 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=05bb641c-0390-bbd6-56bf-4871e65e4f20@gmail.com \
--to=nicolopiazzalunga@gmail.com \
--cc=jwrdegoede@fedoraproject.org \
--cc=linrunner@gmx.net \
--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