From: Liam Breck <liam@networkimprov.net>
To: "Andrew F. Davis" <afd@ti.com>, linux-pm@vger.kernel.org
Cc: Liam Breck <kernel@networkimprov.net>
Subject: [PATCH v12.7 09/10] power: bq27xxx_battery: Flag identical register maps when in debug mode
Date: Fri, 21 Apr 2017 02:59:58 -0700 [thread overview]
Message-ID: <20170421095959.14151-7-liam@networkimprov.net> (raw)
In-Reply-To: <20170421095959.14151-1-liam@networkimprov.net>
From: Liam Breck <kernel@networkimprov.net>
We tie multiple chips to unique register maps. When supporting a new chip,
it's easy to add a duplicate map by mistake.
In debug mode we now scan the register maps for duplicates.
Signed-off-by: Liam Breck <kernel@networkimprov.net>
---
drivers/power/supply/bq27xxx_battery.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/drivers/power/supply/bq27xxx_battery.c b/drivers/power/supply/bq27xxx_battery.c
index 4497bc0..ae4a759 100644
--- a/drivers/power/supply/bq27xxx_battery.c
+++ b/drivers/power/supply/bq27xxx_battery.c
@@ -1932,6 +1932,25 @@ static void bq27xxx_external_power_changed(struct power_supply *psy)
schedule_delayed_work(&di->work, 0);
}
+#ifdef DEBUG
+static void bq27xxx_battery_dbg_regs_dupes(struct bq27xxx_device_info *di)
+{
+ const size_t max = ARRAY_SIZE(bq27xxx_regs);
+ int a, b;
+
+ for (a = 1; a < max-1; a++) {
+ for (b = a+1; b < max; b++) {
+ if (!memcmp(bq27xxx_regs[a], bq27xxx_regs[b],
+ sizeof(bq27xxx_regs[0])))
+ dev_warn(di->dev,
+ "bq27xxx_regs[%d] & [%d] are identical\n", a, b);
+ }
+ }
+}
+#else
+static inline void bq27xxx_battery_dbg_regs_dupes(struct bq27xxx_device_info *di) {}
+#endif
+
int bq27xxx_battery_setup(struct bq27xxx_device_info *di)
{
struct power_supply_desc *psy_desc;
@@ -1940,6 +1959,8 @@ int bq27xxx_battery_setup(struct bq27xxx_device_info *di)
.drv_data = di,
};
+ bq27xxx_battery_dbg_regs_dupes(di);
+
di->ram_chip = di->chip == BQ27421 || di->chip == BQ27441 || di->chip == BQ27621;
di->unseal_key = bq27xxx_unseal_keys[di->chip];
--
2.9.3
next prev parent reply other threads:[~2017-04-21 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 9:59 [PATCH v12.7 0/10] bq27xxx_battery partial series Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 03/10] power: power_supply: Add power_supply_battery_info and API Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 05/10] power: bq27xxx_battery: Add bulk transfer bus methods Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 06/10] power: bq27xxx_battery: Add chip data memory read/write support Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 07/10] power: bq27xxx_battery: Add power_supply_battery_info support Liam Breck
2017-04-21 9:59 ` [PATCH v12.7 08/10] power: bq27xxx_battery: Enable data memory update for certain chips Liam Breck
2017-04-21 9:59 ` Liam Breck [this message]
2017-04-21 9:59 ` [PATCH v12.7 10/10] power: bq27xxx_battery: Remove duplicate register arrays Liam Breck
2017-05-01 15:22 ` [PATCH v12.7 0/10] bq27xxx_battery partial series Sebastian Reichel
2017-05-01 17:46 ` 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=20170421095959.14151-7-liam@networkimprov.net \
--to=liam@networkimprov.net \
--cc=afd@ti.com \
--cc=kernel@networkimprov.net \
--cc=linux-pm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).