From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: Liam Breck <liam@networkimprov.net>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
linux-pm@vger.kernel.org, "Paul Kocialkowski" <contact@paulk.fr>,
"Liam Breck" <kernel@networkimprov.net>
Subject: Re: [RFC v1 5/6] power: supply: bq27xxx: Flag identical chip data when in debug mode
Date: Tue, 25 Jul 2017 15:04:42 +0200 [thread overview]
Message-ID: <20170725130441.xejsh6yuubzqaclr@earth> (raw)
In-Reply-To: <20170709021700.14354-6-liam@networkimprov.net>
[-- Attachment #1: Type: text/plain, Size: 3180 bytes --]
Hi,
On Sat, Jul 08, 2017 at 07:16:59PM -0700, Liam Breck wrote:
> From: Liam Breck <kernel@networkimprov.net>
>
> The driver has 13 unique register maps, several of which are shared
> by multiple chips. When adding support for a new chip, it's easy to
> add a duplicate map by mistake.
Which is not that bad. Sure, some bytes wasted, but your code also
wastes some bytes. This is something, that should normally tested
@ compile time using static checkers. Independently the patch has
some issues:
> In debug mode we now scan bq27xxx_chip_data[n].regs/props/dm_regs for
> duplicates.
>
> Signed-off-by: Liam Breck <kernel@networkimprov.net>
> ---
> drivers/power/supply/bq27xxx_battery.c | 36 +++++++++++++++++++++++++++++++++-
> 1 file changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/power/supply/bq27xxx_battery.c b/drivers/power/supply/bq27xxx_battery.c
> index 5d3893a9..54755c88 100644
> --- a/drivers/power/supply/bq27xxx_battery.c
> +++ b/drivers/power/supply/bq27xxx_battery.c
> @@ -883,7 +883,7 @@ static struct bq27xxx_dm_reg bq27621_dm_regs[] = {
> .props = bq27##ref##_props, \
> .props_size = ARRAY_SIZE(bq27##ref##_props) }
>
> -static struct {
> +static struct bq27xxx_chip_datum {
> u32 opts;
> int acts_like; //todo drop this when opts fully implemented
> u32 unseal_key;
> @@ -918,6 +918,38 @@ static struct {
> [BQ27621] = BQ27XXX_DATA(621, BQ27421, 0x80008000, BQ27XXX_O_CFGUP | BQ27XXX_O_RAM),
> };
>
> +static void __maybe_unused bq27xxx_battery_dbg_dupes(struct bq27xxx_device_info *di)
If there are multiple bq27xxx batteries installed in the system the
code is executed multiple times, so let's modify this a bit:
> +{
> + const size_t max = ARRAY_SIZE(bq27xxx_chip_data);
> + const char * const msg = "bq27xxx_chip_data[%d].%s & [%d].%s are identical\n";
> + struct bq27xxx_chip_datum *a, *b;
> + int i, j;
static checked = false;
if (checked)
return;
> + for (i = 1; i < max-1; i++) {
> + a = bq27xxx_chip_data + i;
> +
> + for (j = i+1; j < max; j++) {
> + b = bq27xxx_chip_data + j;
> +
> + if (a->regs != b->regs &&
> + !memcmp(a->regs, b->regs, sizeof(bq27000_regs)))
> + dev_warn(di->dev, msg, i, "regs", j, "regs");
> +
> + if (a->props != b->props &&
> + a->props_size == b->props_size &&
> + !memcmp(a->props, b->props, a->props_size))
> + dev_warn(di->dev, msg, i, "props", j, "props");
> +
> + if (a->dm_regs != b->dm_regs &&
> + !memcmp(a->dm_regs, b->dm_regs, sizeof(bq27500_dm_regs)))
> + dev_warn(di->dev, msg, i, "dm_regs", j, "dm_regs");
> + }
> + }
checked = true;
> +}
> +#ifndef DEBUG
> +#define bq27xxx_battery_dbg_dupes(di)
> +#endif
> +
> static DEFINE_MUTEX(bq27xxx_list_lock);
> static LIST_HEAD(bq27xxx_battery_devices);
>
> @@ -1989,6 +2021,8 @@ int bq27xxx_battery_setup(struct bq27xxx_device_info *di)
> .drv_data = di,
> };
>
> + bq27xxx_battery_dbg_dupes(di);
Add #ifdef DEBUG here and drop the above.
> INIT_DELAYED_WORK(&di->work, bq27xxx_battery_poll);
> mutex_init(&di->lock);
>
> --
> 2.13.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-25 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 2:16 [RFC v1 0/6] bq27xxx_battery data memory update Liam Breck
2017-07-09 2:16 ` [RFC v1 1/6] power: supply: bq27xxx: Create single chip data table Liam Breck
2017-07-25 11:21 ` Sebastian Reichel
2017-07-09 2:16 ` [RFC v1 2/6] power: supply: bq27xxx: Add chip IDs for previously shadowed chips Liam Breck
2017-07-25 12:52 ` Sebastian Reichel
2017-07-09 2:16 ` [RFC v1 3/6] power: supply: bq27xxx: Enable data memory update for certain chips Liam Breck
2017-07-09 9:07 ` Pali Rohár
2017-07-09 14:13 ` Liam Breck
2017-07-09 15:12 ` Pali Rohár
2017-07-25 11:17 ` Sebastian Reichel
2017-07-09 2:16 ` [RFC v1 4/6] power: supply: bq27xxx: Add chip data options for cfgupdate & ram-only Liam Breck
2017-07-25 11:24 ` Sebastian Reichel
2017-07-09 2:16 ` [RFC v1 5/6] power: supply: bq27xxx: Flag identical chip data when in debug mode Liam Breck
2017-07-25 13:04 ` Sebastian Reichel [this message]
2017-07-09 2:17 ` [RFC v1 6/6] power: supply: bq27xxx: Remove duplicate chip data arrays Liam Breck
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=20170725130441.xejsh6yuubzqaclr@earth \
--to=sebastian.reichel@collabora.co.uk \
--cc=contact@paulk.fr \
--cc=kernel@networkimprov.net \
--cc=liam@networkimprov.net \
--cc=linux-pm@vger.kernel.org \
--cc=pali.rohar@gmail.com \
/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