From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Rhyland Klein <rklein@nvidia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] power: bq20z75: change to platform driver
Date: Mon, 28 Feb 2011 17:04:46 +0300 [thread overview]
Message-ID: <20110228140446.GA28312@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1298594977.30301.1.camel@rklein-linux2>
On Thu, Feb 24, 2011 at 04:49:37PM -0800, Rhyland Klein wrote:
> On Thu, 2011-02-24 at 15:48 -0800, Rhyland Klein wrote:
> > From: Rhyland Klein <rklein@nvidia.com>
> >
> > This change switches the bq20z75 i2c driver into a platform driver
> > and adds support for an optional battery detect gpio. Now the driver also
> > signals when the battery is inserted or removed.
> >
> > I also added a retry mechanism so that for boards where there may be
> > intermittent i2c issues, retries can be used to avoid spurious failures.
> >
> > Signed-off-by: Rhyland Klein <rklein@nvidia.com>
> > ---
[...]
> Anton, are you going to have a chance to review this? I have one more
> patch to submit but I was waiting for this to go in first.
Sorry for the delay.
The main problem with this patch is that it does too many things.
It should be separated into three patches:
1. Convert the driver into a platform driver;
2. Add support for detect gpio;
3. Add retry machanism.
But still, why are you converting the i2c driver into a platform driver?
To pass the GPIOs via platform data? You can do this with I2C driver as
well:
struct i2c_board_info {
....
void *platform_data;
Thanks,
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
prev parent reply other threads:[~2011-02-28 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 23:48 [PATCH v2] power: bq20z75: change to platform driver rklein
[not found] ` <1298594977.30301.1.camel@rklein-linux2>
2011-02-28 14:04 ` Anton Vorontsov [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=20110228140446.GA28312@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rklein@nvidia.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