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

Aras Vaichas wrote:
> Unfortunately the simple coulomb counting chips have the disadvantage
> that the CPU has to be running to accumulate the pulses. Of course,
> the pulses could wake the CPU from a suspend mode, but I'd rather not
> do that just to add "one" to a counter ...
>   

Could you have the coulomb-counting chip connected to a tiny
microcontroller, or even a dedicated hardware counter?  Then the main
CPU wouldn't need to wake as often, it could just ask the
microcontroller over I2C, or read/reset the hardware counter.


b.g.

-- 
Bill Gatliff
bgat@billgatliff.com


  reply	other threads:[~2009-12-15  3:02 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 [this message]
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
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=4B26FC52.6060307@billgatliff.com \
    --to=bgat@billgatliff.com \
    --cc=Dirk@opfer-online.de \
    --cc=arasv@magellan-technology.com \
    --cc=arminlitzel@web.de \
    --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=pavel@ucw.cz \
    --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