From: Liam Breck <liam@networkimprov.net>
To: Sebastian Reichel <sre@kernel.org>
Cc: Matt Ranostay <matt@ranostay.consulting>,
linux-pm@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH v4 6/8] power: bq27xxx_battery: add i2c bulk read/write functions
Date: Sun, 29 Jan 2017 12:08:25 -0800 [thread overview]
Message-ID: <20170129200825.32648-1-liam@networkimprov.net> (raw)
In-Reply-To: 20170129183826.cyysprznipidkttb@earth
On Sun, 2017-01-29 at 18:38:26, Sebastian Reichel wrote:
>> diff --git a/include/linux/power/bq27xxx_battery.h b/include/linux/power/bq27xxx_battery.h
>> index 3f265dbf11af..581402380d6e 100644
>> --- a/include/linux/power/bq27xxx_battery.h
>> +++ b/include/linux/power/bq27xxx_battery.h
>> @@ -41,6 +41,9 @@ struct bq27xxx_platform_data {
>> struct bq27xxx_device_info;
>> struct bq27xxx_access_methods {
>> int (*read)(struct bq27xxx_device_info *di, u8 reg, bool single);
>> + int (*write)(struct bq27xxx_device_info *di, u8 reg, int value, bool single);
>> + int (*read_bulk)(struct bq27xxx_device_info *di, u8 reg, u8 *data, int len);
>> + int (*write_bulk)(struct bq27xxx_device_info *di, u8 reg, u8 *data, int len);
>
>So I had a look at patch 8 and I think we should start with finally
>converting bq27xxx to regmap API and probably a second regmap for
>the block data stuff. That way you get all the debugging info in
>debugfs and the driver looks much cleaner.
Could we complete this patchset using the I2C api? We haven't added to it
extensively, and regmap is unrelated to the purpose of this patchset.
Also maybe the primary maintainers of BQ27xxx should be on the hook for
that api change :-)
Plus we're blocked here on devicetree support for BQ24190 waiting for
power_supply_battery_info.
Thanks
next reply other threads:[~2017-01-29 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 20:08 Liam Breck [this message]
2017-01-29 22:22 ` [PATCH v4 6/8] power: bq27xxx_battery: add i2c bulk read/write functions Sebastian Reichel
2017-01-29 23:02 ` Liam Breck
-- strict thread matches above, loose matches on Subject: below --
2017-01-22 7:13 [PATCH v4 0/8] power: bq27xxx: add support for NVRAM R/W access Matt Ranostay
2017-01-22 7:14 ` [PATCH v4 6/8] power: bq27xxx_battery: add i2c bulk read/write functions Matt Ranostay
2017-01-29 18:38 ` Sebastian Reichel
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=20170129200825.32648-1-liam@networkimprov.net \
--to=liam@networkimprov.net \
--cc=linux-pm@vger.kernel.org \
--cc=matt@ranostay.consulting \
--cc=sre@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).