From: Todd E Brandt <todd.e.brandt@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, lee.jones@linaro.org,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH 0/2] axp20x fuel gauge support
Date: Mon, 5 Jan 2015 13:09:22 -0800 [thread overview]
Message-ID: <20150105210922.GA6630@linux.intel.com> (raw)
In-Reply-To: <54A9750A.2090306@kernel.org>
On Sun, Jan 04, 2015 at 05:14:50PM +0000, Jonathan Cameron wrote:
> On 17/12/14 21:07, Todd E Brandt wrote:
> > Add fuel gauge support to the axp20x driver
> >
> > axp20x.c (1/2): change the battery cell name to fuel_gauge
> > axp20x.h (2/2): add the register defs and platform struct for fuel gauge
> >
> > drivers/mfd/axp20x.c | 10 +++++-----
> > include/linux/mfd/axp20x.h | 43 +++++++++++++++++++++++++++++++++++++++++--
> > 2 files changed, 46 insertions(+), 7 deletions(-)
> >
> Hi Todd,
>
> I'm a little confused by this series. We have an ACPI name change
> (dropping the original - which I'd imagine will causes regressions?)
> Also we have some header elements that look to be getting ready for
> some driver support. But no driver?
Sorry for the confusion, I do indeed have a fuel gauge driver ready to go
but I thought I'd start by sending out only the changes I need to the base axp20x code.
I'm probing to see if there are any issues or conflicts. I don't think there will
be issues changing the cell name since the only cell device ATM is the ADC, but I could
be wrong.
I'll send out the full patch set with the new AXP288 fuel gauge driver ASAP.
>
> Jonathan
>
>
prev parent reply other threads:[~2015-01-05 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 21:07 [PATCH 0/2] axp20x fuel gauge support Todd E Brandt
2015-01-04 17:14 ` Jonathan Cameron
2015-01-05 21:09 ` Todd E Brandt [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=20150105210922.GA6630@linux.intel.com \
--to=todd.e.brandt@linux.intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jic23@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-iio@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).