linux-kernel - Re: [PATCH 07/14] bq27x00: Cache battery registers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTiks6Dy8az8qxNJm4UPzJSRSmFU0b+M6ipjSey3f@mail.gmail.com>
Date:	Sun, 13 Feb 2011 17:14:32 +0200
From:	Grazvydas Ignotas <notasas@...il.com>
To:	Lars-Peter Clausen <lars@...afoo.de>
Cc:	Anton Vorontsov <cbouatmailru@...il.com>,
	Rodolfo Giometti <giometti@...ux.it>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/14] bq27x00: Cache battery registers

On Sat, Feb 12, 2011 at 9:39 PM, Lars-Peter Clausen <lars@...afoo.de> wrote:
> This patch adds a register cache to the bq27x00 battery driver.
> Usually multiple, if not all, power_supply properties are queried at once,
> for example when an uevent is generated. Since some registers are used by
> multiple properties caching the registers should reduce the number of
> reads.
>
> The cache is valid for 5 seconds this roughly matches the internal update
> interval of the current register for the bq27000/bq27200.
>
> Fast changing properties(*_NOW) which can be obtained by reading a single
> register are not cached.
>
> It will also be used in the follow up patch to check if the battery status
> has been changed since the last update to emit power_supply_changed events.
>
> Signed-off-by: Lars-Peter Clausen <lars@...afoo.de>
> ---
>  drivers/power/bq27x00_battery.c |  272 +++++++++++++++++++++-----------------
>  1 files changed, 150 insertions(+), 122 deletions(-)
>
> diff --git a/drivers/power/bq27x00_battery.c b/drivers/power/bq27x00_battery.c
> index 44bc76b..0c94693 100644
> --- a/drivers/power/bq27x00_battery.c
> +++ b/drivers/power/bq27x00_battery.c
> @@ -19,7 +19,6 @@

<snip>

> +static void bq27x00_update(struct bq27x00_device_info *di)
> +{
> +       struct bq27x00_reg_cache cache = {0, };
> +       bool is_bq27500 = di->chip == BQ27500;
> +
> +       cache.flags = bq27x00_read(di, BQ27x00_REG_FLAGS, is_bq27500);
> +       if (cache.flags >= 0) {
> +               cache.capacity = bq27x00_battery_read_rsoc(di);
> +               cache.temperature = bq27x00_read(di, BQ27x00_REG_TEMP, false);
> +               cache.time_to_empty = bq27x00_battery_read_time(di, BQ27x00_REG_TTE);
> +               cache.time_to_empty_avg = bq27x00_battery_read_time(di, BQ27x00_REG_TTECP);
> +               cache.time_to_full = bq27x00_battery_read_time(di, BQ27x00_REG_TTF);
> +
> +               if (!is_bq27500)
> +                       cache.current_now = bq27x00_read(di, BQ27x00_REG_AI, false);
>        }
>

<snip>

> -static int bq27x00_battery_current(struct bq27x00_device_info *di)
> +static int bq27x00_battery_current(struct bq27x00_device_info *di,
> +       union power_supply_propval *val)
>  {
> -       int ret;
> -       int curr = 0;
> -       int flags = 0;
> +       int curr;
>
> -       ret = bq27x00_read(di, BQ27x00_REG_AI, &curr, false);
> -       if (ret) {
> -               dev_err(di->dev, "error reading current\n");
> -               return 0;
> -       }
> +       if (di->chip == BQ27000)
> +           curr = bq27x00_read(di, BQ27x00_REG_AI, false);
> +       else
> +           curr = di->cache.current_now;

You're updating current_now in cache if it's not bq27500, but
bypassing cache for bq27000?

Why do you still want to cache the current while you are no longer
caching voltage, because it needs 2 register reads I guess?
--
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/