linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: <sebastian.reichel@collabora.com>, <linux-pm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v3 1/4] power: supply: core: Update sysfs-class-power ABI document
Date: Wed, 8 Jan 2020 14:23:11 -0600	[thread overview]
Message-ID: <20200108202314.11791-2-dmurphy@ti.com> (raw)
In-Reply-To: <20200108202314.11791-1-dmurphy@ti.com>

Add the "Over Current" string to /sys/class/power_supply/<supply_name>/health
description.

Fixes: e3e83cc601e57 ("power: supply: core: Add POWER_SUPPLY_HEALTH_OVERCURRENT constant")
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
 Documentation/ABI/testing/sysfs-class-power | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power
index 27edc06e2495..bf3b48f022dc 100644
--- a/Documentation/ABI/testing/sysfs-class-power
+++ b/Documentation/ABI/testing/sysfs-class-power
@@ -189,7 +189,8 @@ Description:
 		Access: Read
 		Valid values: "Unknown", "Good", "Overheat", "Dead",
 			      "Over voltage", "Unspecified failure", "Cold",
-			      "Watchdog timer expire", "Safety timer expire"
+			      "Watchdog timer expire", "Safety timer expire",
+			      "Over current"
 
 What:		/sys/class/power_supply/<supply_name>/precharge_current
 Date:		June 2017
-- 
2.23.0


  reply	other threads:[~2020-01-08 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 20:23 [PATCH v3 0/4] BQ25150/155 Charger Dan Murphy
2020-01-08 20:23 ` Dan Murphy [this message]
2020-01-08 20:23 ` [PATCH v3 2/4] power_supply: Add additional health properties to the header Dan Murphy
2020-01-08 20:23 ` [PATCH v3 3/4] dt-bindings: power: Add the bq2515x family dt bindings Dan Murphy
2020-01-08 20:23 ` [PATCH v3 4/4] power: supply: bq2515x: Introduce the bq2515x family Dan Murphy
2020-01-13 10:33   ` Dan Carpenter

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=20200108202314.11791-2-dmurphy@ti.com \
    --to=dmurphy@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sebastian.reichel@collabora.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).