public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Andy Green <andy@warmcat.com>
Cc: Stanislav Brabec <utx@penguin.cz>,
	Aras Vaichas <arasv@magellan-technology.com>,
	Bill Gatliff <bgat@billgatliff.com>,
	thommycheck@gmail.com,
	Linus Walleij <linus.walleij@stericsson.com>,
	linux-embedded@vger.kernel.org, lenz@cs.wisc.edu,
	dbaryshkov@gmail.com, Brian Swetland <swetland@google.com>,
	arminlitzel@web.de,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Dirk@opfer-online.de, cbou@mail.ru, rpurdie@rpsys.net,
	omegamoon@gmail.com, Cyril Hrubis <metan@ucw.cz>,
	eric.y.miao@gmail.com, dwmw2@infradead.org,
	zaurus-devel@www.linuxtogo.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [POWER] battery calibration parameters from sysfs
Date: Fri, 18 Dec 2009 09:48:50 +0100	[thread overview]
Message-ID: <20091218084850.GA1513@ucw.cz> (raw)
In-Reply-To: <4B28AAFC.5010108@warmcat.com>

Hi!1


>>> Yes, but in that case you might as well just purchase a coulomb
>>> counter with a built-in accumulator and an I2C/SPI/microwire interface
>>> save yourself some PCB space and cost (maybe)

Hardware is already given.

>> Well, Pavel attempts to implement a "poor man's Coulomb counter" or at
>> least "poor man's Ampere meter" for devices that are not equipped with
>> any of it.
>
> I think the "poor man's Coulomb counter" is a loser, the errors will  
> overwhelm you too rapidly.  The estimated rate of discharge could
>> work,  

Actually android phones do "poor man's Coulomb counter", and it seems
to mostly work.

> based on what clocks, regulators and so on are running, but I am not  
> sure how useful that number is really given you can't realistically  
> integrate it due to the big error it is bound to have.
...
> Otherwise for L-ion batteries, looking at the voltage level alone,  
> filtered to remove GSM transmit slots etc, is really quite workable for  
> estimating charge status.

Well, you have to compensate for backlight power; and yes, that's what
I'm trying to do.
								Pavel 

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-12-18  8:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 10:42 [POWER] battery calibration parameters from sysfs Linus Walleij
2009-12-04 10:49 ` Mark Brown
2009-12-04 14:17   ` Mark Brown
2009-12-05 13:08   ` Linus Walleij
2009-12-05 17:45     ` Mark Brown
2009-12-07 11:48     ` Mark Brown
2009-12-07 14:07       ` Linus Walleij
2009-12-07 16:56         ` Mark Brown
2009-12-08  5:27           ` Brian Swetland
2009-12-08 10:28             ` Mark Brown
2009-12-13 13:24           ` Pavel Machek
2009-12-14 12:12             ` Mark Brown
2009-12-14 21:22               ` Pavel Machek
2009-12-14 23:43                 ` Aras Vaichas
2009-12-15  3:02                   ` Bill Gatliff
2009-12-15 22:58                     ` Aras Vaichas
2009-12-15 23:32                       ` Stanislav Brabec
2009-12-16  9:40                         ` Andy Green
2009-12-18  8:48                           ` Pavel Machek [this message]
2009-12-16 22:53               ` Pavel Machek
2009-12-13 13:19         ` Pavel Machek
2009-12-14 11:50           ` Mark Brown
2009-12-14 11:58             ` Pavel Machek
2009-12-14 12:14               ` Mark Brown
2009-12-04 11:34 ` Alexander Clouter
2009-12-06 20:52 ` Greg KH

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=20091218084850.GA1513@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Dirk@opfer-online.de \
    --cc=andy@warmcat.com \
    --cc=arasv@magellan-technology.com \
    --cc=arminlitzel@web.de \
    --cc=bgat@billgatliff.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cbou@mail.ru \
    --cc=dbaryshkov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=eric.y.miao@gmail.com \
    --cc=lenz@cs.wisc.edu \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metan@ucw.cz \
    --cc=omegamoon@gmail.com \
    --cc=rpurdie@rpsys.net \
    --cc=swetland@google.com \
    --cc=thommycheck@gmail.com \
    --cc=utx@penguin.cz \
    --cc=zaurus-devel@www.linuxtogo.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