From: Arvid Norlander <lkml@vorpal.se>
To: platform-driver-x86@vger.kernel.org, linux-pm@vger.kernel.org
Cc: Sebastian Reichel <sre@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Azael Avalos <coproscefalo@gmail.com>,
Arvid Norlander <lkml@vorpal.se>
Subject: [PATCH 3/3] docs: ABI: charge_control_end_threshold may not support all values
Date: Sun, 28 Aug 2022 21:29:20 +0200 [thread overview]
Message-ID: <20220828192920.805253-4-lkml@vorpal.se> (raw)
In-Reply-To: <20220828192920.805253-1-lkml@vorpal.se>
Some laptops (for example Toshiba Satellite Z830) only supports some fixed
values. Allow for this and document the expected behaviour in such cases.
Wording suggested by Hans de Goede.
Signed-off-by: Arvid Norlander <lkml@vorpal.se>
---
Documentation/ABI/testing/sysfs-class-power | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power
index a9ce63cfbe87..e434fc523291 100644
--- a/Documentation/ABI/testing/sysfs-class-power
+++ b/Documentation/ABI/testing/sysfs-class-power
@@ -364,7 +364,10 @@ Date: April 2019
Contact: linux-pm@vger.kernel.org
Description:
Represents a battery percentage level, above which charging will
- stop.
+ stop. Not all hardware is capable of setting this to an arbitrary
+ percentage. Drivers will round written values to the nearest
+ supported value. Reading back the value will show the actual
+ threshold set by the driver.
Access: Read, Write
--
2.37.2
next prev parent reply other threads:[~2022-08-28 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 19:29 [PATCH 0/3] platform/x86: Battery charge mode in toshiba_acpi Arvid Norlander
2022-08-28 19:29 ` [PATCH 1/3] platform/x86: Battery charge mode in toshiba_acpi (internals) Arvid Norlander
2022-08-28 19:29 ` [PATCH 2/3] platform/x86: Battery charge mode in toshiba_acpi (sysfs) Arvid Norlander
2022-08-28 22:15 ` kernel test robot
2022-08-28 22:44 ` Arvid Norlander
2022-08-28 22:44 ` Arvid Norlander
2022-08-29 8:16 ` Miguel Ojeda
2022-08-29 8:16 ` Miguel Ojeda
2022-08-29 16:59 ` Nick Desaulniers
2022-08-29 16:59 ` Nick Desaulniers
2022-08-28 22:36 ` kernel test robot
2022-08-28 19:29 ` Arvid Norlander [this message]
2022-09-01 21:14 ` [PATCH 3/3] docs: ABI: charge_control_end_threshold may not support all values Sebastian Reichel
2022-09-01 15:27 ` [PATCH 0/3] platform/x86: Battery charge mode in toshiba_acpi Hans de Goede
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=20220828192920.805253-4-lkml@vorpal.se \
--to=lkml@vorpal.se \
--cc=coproscefalo@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.