From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: Andres Salomon <dilinger@collabora.co.uk>,
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 5/5] power_supply: add a charge_type status to the api, and use it for olpc driver
Date: Tue, 30 Jun 2009 20:15:47 +0100 [thread overview]
Message-ID: <20090630191547.GA24002@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20090630190239.GA21667@oksana.dev.rtsoft.ru>
On Tue, Jun 30, 2009 at 11:02:39PM +0400, Anton Vorontsov wrote:
> On Tue, Jun 30, 2009 at 04:57:14PM +0100, Mark Brown wrote:
> > I strongly suspect you will find that the "slow" mode there is actually
> > a trickle charge. It's a lot more practical to trickle charge in mobile
> > phone sized systems since the batteries are so much smaller than laptop
> > batteries.
...
> For a Li-ion battery, the precharge current is typically 0.1C
> (C = charge rate = the charge current which will fully charge the
> battery in one hour)."
Yup, that sounds like a trickle charge all right.
> There is also precharge-wait and fastcharge-wait modes, FWIW.
> But we don't expose this information to the userspace.
Those *probably* boil down to one of the other states - without looking
at the datasheet they sound like waiting for the conditions required to
do one of the other charges to be satisfied.
> Probably not, Fast/Slow/Trickle are quite vague terms anyway.
> I'd prefer if we could measure this in some real units, but alas...
Fast and trickle charge are fairly well understood terms, I think. For
specific numbers you'd need to look at the particular batteries
involved, unfortunately, but they do tend to be fairly obvious when
looking at a particular charger and/or battery.
next prev parent reply other threads:[~2009-06-30 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 6:17 [PATCH 5/5] power_supply: add a charge_type status to the api, and use it for olpc driver Andres Salomon
2009-06-30 11:31 ` Mark Brown
2009-06-30 15:04 ` Andres Salomon
2009-06-30 15:37 ` Anton Vorontsov
2009-06-30 15:57 ` Mark Brown
2009-06-30 19:02 ` Anton Vorontsov
2009-06-30 19:15 ` Mark Brown [this message]
2009-06-30 23:14 ` Anton Vorontsov
2009-07-02 13:45 ` Andres Salomon
2009-07-02 14:06 ` Mark Brown
2009-07-02 14:26 ` Anton Vorontsov
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=20090630191547.GA24002@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=avorontsov@ru.mvista.com \
--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 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.