From: Guenter Roeck <linux@roeck-us.net>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: linux-pm@vger.kernel.org, Chris Health <cphealy@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Sebastian Reichel <sre@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] power: supply: core: Add POWER_SUPPLY_HEALTH_OVERCURRENT constant
Date: Fri, 26 Apr 2019 09:12:39 -0700 [thread overview]
Message-ID: <20190426161239.GA7128@roeck-us.net> (raw)
In-Reply-To: <20190417084457.28747-2-andrew.smirnov@gmail.com>
On Wed, Apr 17, 2019 at 01:44:55AM -0700, Andrey Smirnov wrote:
> Add POWER_SUPPLY_HEALTH_OVERCURRENT constant in order to allow
> singalling overcurrent condition via power supply health information.
>
> Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
> Cc: Chris Health <cphealy@gmail.com>
> Cc: Lucas Stach <l.stach@pengutronix.de>
> Cc: Fabio Estevam <fabio.estevam@nxp.com>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Sebastian Reichel <sre@kernel.org>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-pm@vger.kernel.org
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/power/supply/power_supply_sysfs.c | 2 +-
> include/linux/power_supply.h | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/power/supply/power_supply_sysfs.c b/drivers/power/supply/power_supply_sysfs.c
> index 5e91946731fd..464f4e837601 100644
> --- a/drivers/power/supply/power_supply_sysfs.c
> +++ b/drivers/power/supply/power_supply_sysfs.c
> @@ -62,7 +62,7 @@ static const char * const power_supply_charge_type_text[] = {
> static const char * const power_supply_health_text[] = {
> "Unknown", "Good", "Overheat", "Dead", "Over voltage",
> "Unspecified failure", "Cold", "Watchdog timer expire",
> - "Safety timer expire"
> + "Safety timer expire", "Over current"
> };
>
> static const char * const power_supply_technology_text[] = {
> diff --git a/include/linux/power_supply.h b/include/linux/power_supply.h
> index 2f9c201a54d1..bdab14c7ca4d 100644
> --- a/include/linux/power_supply.h
> +++ b/include/linux/power_supply.h
> @@ -57,6 +57,7 @@ enum {
> POWER_SUPPLY_HEALTH_COLD,
> POWER_SUPPLY_HEALTH_WATCHDOG_TIMER_EXPIRE,
> POWER_SUPPLY_HEALTH_SAFETY_TIMER_EXPIRE,
> + POWER_SUPPLY_HEALTH_OVERCURRENT,
> };
>
> enum {
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-04-26 16:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 8:44 [PATCH 0/3] Driver for UCS1002 Andrey Smirnov
2019-04-17 8:44 ` [PATCH 1/3] power: supply: core: Add POWER_SUPPLY_HEALTH_OVERCURRENT constant Andrey Smirnov
2019-04-26 16:12 ` Guenter Roeck [this message]
2019-04-17 8:44 ` [PATCH 2/3] power: supply: Add driver for Microchip UCS1002 Andrey Smirnov
2019-04-26 14:43 ` Lucas Stach
2019-04-28 22:24 ` Andrey Smirnov
2019-04-26 16:10 ` Guenter Roeck
2019-04-27 0:16 ` Andrey Smirnov
2019-04-26 16:51 ` Enric Balletbo Serra
2019-04-26 17:04 ` Guenter Roeck
2019-04-27 0:29 ` Andrey Smirnov
2019-04-17 8:44 ` [PATCH 3/3] dt-bindings: power: supply: Add bindings " Andrey Smirnov
2019-04-17 19:05 ` Fabio Estevam
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=20190426161239.GA7128@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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 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®