From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Andres Salomon <dilinger@collabora.co.uk>
Cc: cbou@mail.ru, dwmw2@infradead.org, linux-kernel@vger.kernel.org,
richard@laptop.org, Andrew Morton <akpm@linux-foundation.org>,
Paul Fox <pgf@laptop.org>,
dsaxena@laptop.org
Subject: Re: [PATCH 3/5] power_supply: add a TRICKLE_CHARGING status, and add it to the olpc driver
Date: Wed, 24 Jun 2009 18:40:00 +0400 [thread overview]
Message-ID: <20090624144000.GD9035@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20090622234607.11f61bec@mycelium.queued.net>
On Mon, Jun 22, 2009 at 11:46:07PM -0400, Andres Salomon wrote:
>
> The hardware has an extra bit that specifies that the battery is trickle
> charging, so when determining if the battery is present/charging the TRICKLE
> bit needs to be checked as well. Because battery diagnostics might want to
> know whether trickle charging is happening or not, and also because trickle
> charging falls somewhere between charging and not charging (read: Richard got
> mad at me when I tried to set CHARGING when in trickle charge. He gets so
> angry sometimes), we add a new TRICKLE status to sysfs.
:-)
Technically the patch looks OK. But are we sure that userspace
won't break when it'll see a new charging state?
To be on a safe side, and maybe it'll be a better idea anyway,
we could implement charging_mode property? With at least following
values: "N/A", "Trickle", "Slow", "Fast"?
Thanks!
> Signed-off-by: Andres Salomon <dilinger@collabora.co.uk>
> ---
> drivers/power/olpc_battery.c | 13 ++++++++++---
> drivers/power/power_supply_sysfs.c | 3 ++-
> include/linux/power_supply.h | 1 +
> 3 files changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/power/olpc_battery.c b/drivers/power/olpc_battery.c
> index f8d2d6b..3ecf484 100644
> --- a/drivers/power/olpc_battery.c
> +++ b/drivers/power/olpc_battery.c
> @@ -35,6 +35,7 @@
> #define BAT_STAT_AC 0x10
> #define BAT_STAT_CHARGING 0x20
> #define BAT_STAT_DISCHARGING 0x40
> +#define BAT_STAT_TRICKLE 0x80
>
> #define BAT_ERR_INFOFAIL 0x02
> #define BAT_ERR_OVERVOLTAGE 0x04
> @@ -89,7 +90,12 @@ static char bat_serial[17]; /* Ick */
> static int olpc_bat_get_status(union power_supply_propval *val, uint8_t ec_byte)
> {
> if (olpc_platform_info.ecver > 0x44) {
> - if (ec_byte & BAT_STAT_CHARGING)
> + if (ec_byte & BAT_STAT_TRICKLE)
> + /* Note that the order here is important; the EC sets
> + * both the CHARGING and TRICKLE bits at the same time
> + * to support older kernels. */
> + val->intval = POWER_SUPPLY_STATUS_TRICKLE_CHARGING;
> + else if (ec_byte & BAT_STAT_CHARGING)
> val->intval = POWER_SUPPLY_STATUS_CHARGING;
> else if (ec_byte & BAT_STAT_DISCHARGING)
> val->intval = POWER_SUPPLY_STATUS_DISCHARGING;
> @@ -219,7 +225,8 @@ static int olpc_bat_get_property(struct power_supply *psy,
> It doesn't matter though -- the EC will return the last-known
> information, and it's as if we just ran that _little_ bit faster
> and managed to read it out before the battery went away. */
> - if (!(ec_byte & BAT_STAT_PRESENT) && psp != POWER_SUPPLY_PROP_PRESENT)
> + if (!(ec_byte & (BAT_STAT_PRESENT|BAT_STAT_TRICKLE)) &&
> + psp != POWER_SUPPLY_PROP_PRESENT)
> return -ENODEV;
>
> switch (psp) {
> @@ -229,7 +236,7 @@ static int olpc_bat_get_property(struct power_supply *psy,
> return ret;
> break;
> case POWER_SUPPLY_PROP_PRESENT:
> - val->intval = !!(ec_byte & BAT_STAT_PRESENT);
> + val->intval = !!(ec_byte & (BAT_STAT_PRESENT|BAT_STAT_TRICKLE));
> break;
>
> case POWER_SUPPLY_PROP_HEALTH:
> diff --git a/drivers/power/power_supply_sysfs.c b/drivers/power/power_supply_sysfs.c
> index add5f39..eb1affc 100644
> --- a/drivers/power/power_supply_sysfs.c
> +++ b/drivers/power/power_supply_sysfs.c
> @@ -41,7 +41,8 @@ static ssize_t power_supply_show_property(struct device *dev,
> struct device_attribute *attr,
> char *buf) {
> static char *status_text[] = {
> - "Unknown", "Charging", "Discharging", "Not charging", "Full"
> + "Unknown", "Charging", "Charging (trickle)", "Discharging", "Not charging",
> + "Full",
> };
> static char *health_text[] = {
> "Unknown", "Good", "Overheat", "Dead", "Over voltage",
> diff --git a/include/linux/power_supply.h b/include/linux/power_supply.h
> index 1e45cbc..50ee079 100644
> --- a/include/linux/power_supply.h
> +++ b/include/linux/power_supply.h
> @@ -33,6 +33,7 @@
> enum {
> POWER_SUPPLY_STATUS_UNKNOWN = 0,
> POWER_SUPPLY_STATUS_CHARGING,
> + POWER_SUPPLY_STATUS_TRICKLE_CHARGING,
> POWER_SUPPLY_STATUS_DISCHARGING,
> POWER_SUPPLY_STATUS_NOT_CHARGING,
> POWER_SUPPLY_STATUS_FULL,
> --
> 1.5.6.5
>
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
prev parent reply other threads:[~2009-06-24 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 3:46 [PATCH 3/5] power_supply: add a TRICKLE_CHARGING status, and add it to the olpc driver Andres Salomon
2009-06-23 10:37 ` Mark Brown
2009-06-23 19:28 ` Richard A. Smith
2009-06-23 22:44 ` Mark Brown
2009-06-23 23:13 ` Richard A. Smith
2009-06-23 23:25 ` Mark Brown
2009-06-23 23:46 ` Richard A. Smith
2009-06-24 10:09 ` Mark Brown
2009-06-30 6:20 ` Andres Salomon
2009-06-24 14:40 ` Anton Vorontsov [this message]
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=20090624144000.GD9035@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=cbou@mail.ru \
--cc=dilinger@collabora.co.uk \
--cc=dsaxena@laptop.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgf@laptop.org \
--cc=richard@laptop.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