LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: Grazvydas Ignotas <notasas@gmail.com>,
	Rodolfo Giometti <giometti@linux.it>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/14] POWER: BQ27x00: New Properties, fixes, bq27000 support
Date: Tue, 08 Feb 2011 18:09:07 +0100	[thread overview]
Message-ID: <4D5178B3.4050900@metafoo.de> (raw)
In-Reply-To: <20110208162802.GA29842@oksana.dev.rtsoft.ru>

On 02/08/2011 05:28 PM, Anton Vorontsov wrote:
> On Tue, Feb 08, 2011 at 05:13:47PM +0100, Lars-Peter Clausen wrote:
>> On 02/08/2011 12:40 PM, Grazvydas Ignotas wrote:
>>> That works. However I wonder about the delay, I've experimentally
>>> determined that bq27500 refreshes in about a second, so before this
>>> series I could for example run 'watch -n 1 cat current_now' and see
>>> current changes almost in realtime (when toggling backlight, for
>>> example). Maybe we could have different cache timeout for different
>>> chips or have quickly changing properties (like current and voltage)
>>> bypass the cache.
>>
>> Looking at the datasheet confirms that the bq27500 updates the current register
>> every second. The bq27000 updates it only every 5.12 seconds.
>> I think reducing the the cache time for bq27500 to 1 second would render the
>> cache mostly useless, but maybe it makes sense to bypass the cache for voltage
>> and current on the bq27500.
> 
> Nope, it's not useless. I.e. for `cat /sys/class/power_supply/*/*`.
> Actually, it was only the purpose for caching the battery values.
> 
> So, 1 second is OK.

Yes, the purpose of the register cache was that registers aren't read multiple
times if multiple properties are queried at once. Which is what I consider the
standard use case, since this is what a power monitor application would
normally do.
The other use case is constantly monitor a single property like CURRENT_NOW.
Since we would now read all properties instead of just one and would increase
the load on the bus by 12 times.

The other purpose of the register cache was to be able to tell whether
registers have changed when polling the battery. Since we already ignore the
*_NOW properties when comparing the the old and the new state it would make
sense to bypass the cache completely for them.
This would reduce the load when monitoring such a property and it would also
reduce the load when polling the battery since we would only read 8 instead of
12 registers.

> 
> p.s. Lars, on the next resend, can you please remove "POWER:"
> prefix from the patch description line, bound the commit message
> width to 76 symbols, and add all the collected Acked-by lines.
> That way I can just pull your tree.

Sure.

- Lars


      reply	other threads:[~2011-02-08 17:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06  0:47 Lars-Peter Clausen
2011-02-06  0:47 ` [PATCH 01/14] POWER: bq27x00: Add type property Lars-Peter Clausen
2011-02-06 16:43   ` Rodolfo Giometti
2011-02-06  0:47 ` [PATCH 02/14] POWER: bq27x00: Improve temperature precession Lars-Peter Clausen
2011-02-07  8:06   ` Rodolfo Giometti
2011-02-06  0:48 ` [PATCH 03/14] POWER: bq27x00: Fix current now property Lars-Peter Clausen
2011-02-07  8:07   ` Rodolfo Giometti
2011-02-06  0:48 ` [PATCH 04/14] POWER: bq27x00: Return -ENODEV for properties if the battery is not present Lars-Peter Clausen
2011-02-06 16:40   ` Rodolfo Giometti
2011-02-06  0:48 ` [PATCH 05/14] POWER: bq27x00: Prepare code for addition of bq27000 platform driver Lars-Peter Clausen
2011-02-07  8:09   ` Rodolfo Giometti
2011-02-06  0:48 ` [PATCH 06/14] POWER: bq27x00: Add bq27000 support Lars-Peter Clausen
2011-02-06  0:48 ` [PATCH 07/14] POWER: bq27X00: Cache battery registers Lars-Peter Clausen
2011-02-06  0:48 ` [PATCH 08/14] POWER: bq27x00: Poll battery state Lars-Peter Clausen
2011-02-06  0:48 ` [PATCH 09/14] POWER: bq27x00: Add new properties Lars-Peter Clausen
2011-02-06  0:48 ` [PATCH 10/14] POWER: bq27x00: Add MODULE_DEVICE_TABLE Lars-Peter Clausen
2011-02-06 16:49   ` Rodolfo Giometti
2011-02-06  0:48 ` [PATCH 11/14] POWER: bq27x00: Give more specific reports on battery status Lars-Peter Clausen
2011-02-06 16:38   ` Rodolfo Giometti
2011-02-06  0:48 ` [PATCH 12/14] POWER: bq27x00: Minor cleanups Lars-Peter Clausen
2011-02-06  0:48 ` [PATCH 13/14] POWER: bq27x00: Cleanup bq27x00_i2c_read Lars-Peter Clausen
2011-02-06  0:48 ` [PATCH 14/14] POWER: Ignore -ENODATA errors when generating a uevent Lars-Peter Clausen
2011-02-06 22:47 ` [PATCH 00/14] POWER: BQ27x00: New Properties, fixes, bq27000 support Felipe Contreras
2011-02-06 23:09   ` Lars-Peter Clausen
2011-02-07  0:00     ` Felipe Contreras
2011-02-07  0:12       ` Lars-Peter Clausen
2011-02-07 10:52     ` Pali Rohár
2011-02-07  0:58 ` Grazvydas Ignotas
2011-02-07  1:30   ` Lars-Peter Clausen
2011-02-08 11:40     ` Grazvydas Ignotas
2011-02-08 16:13       ` Lars-Peter Clausen
2011-02-08 16:28         ` Anton Vorontsov
2011-02-08 17:09           ` Lars-Peter Clausen [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=4D5178B3.4050900@metafoo.de \
    --to=lars@metafoo.de \
    --cc=cbouatmailru@gmail.com \
    --cc=giometti@linux.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=notasas@gmail.com \
    --subject='Re: [PATCH 00/14] POWER: BQ27x00: New Properties, fixes, bq27000 support' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).