From: Bibby Hsieh <bibby.hsieh@mediatek.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
<linux-i2c@vger.kernel.org>, <tfiga@chromium.org>,
<drinkcat@chromium.org>, <srv_heupstream@mediatek.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<devicetree@vger.kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v14 2/2] i2c: core: support bus regulator controlling in adapter
Date: Tue, 19 May 2020 15:26:13 +0800 [thread overview]
Message-ID: <1589873173.513.0.camel@mtksdaap41> (raw)
In-Reply-To: <20200519065937.GD1094@ninjato>
Hi, Wolfram,
Thanks for the reviewing, I will sent next version for fixing up them.
Bibby
On Tue, 2020-05-19 at 08:59 +0200, Wolfram Sang wrote:
> On Tue, Apr 28, 2020 at 02:18:13PM +0800, Bibby Hsieh wrote:
> > Although in the most platforms, the bus power of i2c
> > are alway on, some platforms disable the i2c bus power
> > in order to meet low power request.
> >
> > We get and enable bulk regulator in i2c adapter device.
> >
> > Signed-off-by: Bibby Hsieh <bibby.hsieh@mediatek.com>
> > ---
> > drivers/i2c/i2c-core-base.c | 82 +++++++++++++++++++++++++++++++++++++
> > include/linux/i2c.h | 2 +
> > 2 files changed, 84 insertions(+)
> >
> > diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
> > index 5cc0b0ec5570..f81b42a4ed07 100644
> > --- a/drivers/i2c/i2c-core-base.c
> > +++ b/drivers/i2c/i2c-core-base.c
> > @@ -313,6 +313,7 @@ static int i2c_smbus_host_notify_to_irq(const struct i2c_client *client)
> > static int i2c_device_probe(struct device *dev)
> > {
> > struct i2c_client *client = i2c_verify_client(dev);
> > + struct i2c_adapter *adap = client->adapter;
>
> You are accessing client before the NULL pointer check.
>
>
> > @@ -414,6 +421,7 @@ static int i2c_device_probe(struct device *dev)
> > static int i2c_device_remove(struct device *dev)
> > {
> > struct i2c_client *client = i2c_verify_client(dev);
> > + struct i2c_adapter *adap = client->adapter;
>
> Same here.
>
> > +static int i2c_suspend_late(struct device *dev)
> > +{
> > + struct i2c_client *client = i2c_verify_client(dev);
> > + struct i2c_adapter *adap = client->adapter;
> > + int err;
> > +
> > + err = pm_generic_suspend_late(&client->dev);
> > + if (err)
> > + return err;
> > +
> > + if (!pm_runtime_status_suspended(&client->dev))
> > + return regulator_disable(adap->bus_regulator);
> > +
> > + return err;
>
> Can be 'return 0'.
>
prev parent reply other threads:[~2020-05-19 7:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 6:18 [PATCH v14 0/2] add power control in i2c Bibby Hsieh
2020-04-28 6:18 ` [PATCH v14 1/2] dt-binding: i2c: add bus-supply property Bibby Hsieh
2020-04-28 15:02 ` Rob Herring
2020-05-19 6:53 ` Wolfram Sang
2020-05-19 7:00 ` Wolfram Sang
2020-04-28 6:18 ` [PATCH v14 2/2] i2c: core: support bus regulator controlling in adapter Bibby Hsieh
2020-04-28 11:25 ` Grygorii Strashko
2020-04-28 11:44 ` Tomasz Figa
2020-04-28 12:15 ` Grygorii Strashko
2020-04-28 11:45 ` Tomasz Figa
2020-05-19 6:59 ` Wolfram Sang
2020-05-19 7:26 ` Bibby Hsieh [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=1589873173.513.0.camel@mtksdaap41 \
--to=bibby.hsieh@mediatek.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=wsa@the-dreams.de \
/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).