From: Sebastian Reichel <sre@kernel.org>
To: Evgeniy Polyakov <zbr@ioremap.net>, "Andrew F. Davis" <afd@ti.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/6] Add support for additional bq27xxx devices
Date: Thu, 24 Sep 2015 00:43:04 +0200 [thread overview]
Message-ID: <20150923224304.GB4024@earth> (raw)
In-Reply-To: <5602F23D.80700@ti.com>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
[updated receiver list]
Hi,
On Wed, Sep 23, 2015 at 01:41:01PM -0500, Andrew F. Davis wrote:
> On 09/23/2015 11:42 AM, Sebastian Reichel wrote:
> >On Tue, Sep 22, 2015 at 02:35:05PM -0500, Andrew F. Davis wrote:
> >>This series adds support for several additional bq27xxx devices and
> >>makes a few related fixes.
> >
> >Thanks, I queued all remaining patches. I wonder if this driver
> >should be converted to regmap. It supports lots of chips now and
> >it might be useful to get register dumps from debugfs.
> >
>
> I was thinking the same thing, but this driver can also communicate
> over the w1 bus which doesn't look like it has the regmap hooks yet.
> So I never really found a clean way, outside of bringing up regmap
> on w1, to convert this driver over.
Right, I assumed there was regmap support for w1 :(
Evgeniy, are there plans to add 1-wire regmap support?
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-09-23 22:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 19:35 [PATCH v5 0/6] Add support for additional bq27xxx devices Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 1/6] power: bq27x00_battery: Renaming for consistency Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis
2015-09-22 21:00 ` Sebastian Reichel
2015-09-23 1:07 ` Tony Lindgren
2015-09-23 6:03 ` 答复: " GUAN Xuetao
2015-09-22 19:35 ` [PATCH v5 2/6] power: bq27xxx_battery: Platform initialization must declare a device Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 3/6] power: bq27xxx_battery: Fix typos and change naming for state of charge functions Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 4/6] power: bq27xxx_battery: Add support for additional bq27xxx family devices Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 5/6] power: bq27xxx_battery: Cleanup health checking Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 6/6] power: bq27xxx_battery: Add interrupt handling support Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis
2015-09-23 16:42 ` [PATCH v5 0/6] Add support for additional bq27xxx devices Sebastian Reichel
2015-09-23 18:41 ` Andrew F. Davis
2015-09-23 22:43 ` Sebastian Reichel [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=20150923224304.GB4024@earth \
--to=sre@kernel.org \
--cc=afd@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=zbr@ioremap.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.