[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090623103717.GH5422@sirena.org.uk>
Date: Tue, 23 Jun 2009 11:37:17 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Andres Salomon <dilinger@...labora.co.uk>
Cc: cbou@...l.ru, dwmw2@...radead.org, linux-kernel@...r.kernel.org,
richard@...top.org, Andrew Morton <akpm@...ux-foundation.org>,
Paul Fox <pgf@...top.org>, dsaxena@...top.org
Subject: Re: [PATCH 3/5] power_supply: add a TRICKLE_CHARGING status, and
add it to the olpc driver
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.
To avoid confusing usere applications might it be better to add another
piece of information with detail on the charger status rather than a new
state? The fact that the new state name shares a prefix with the
regular charging state does help here but you might still confuse things
and it makes the name of the new state in sysfs a bit awkward.
I'd also be tempted to do this the other way around and add a fast
charge status; certainly in embedded cases trickle charging is more of a
default state since it requires less incoming power (important if you're
using USB) and there's less risk of damage to the battery.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists