linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "Popa, Stefan Serban" <StefanSerban.Popa@analog.com>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
	"knaack.h@gmx.de" <knaack.h@gmx.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 3/3] iio: adc: ad799x: add pm_ops to disable the device completely
Date: Wed, 18 Sep 2019 10:37:52 +0200	[thread overview]
Message-ID: <20190918083752.nj5vtmixzvisiukn@pengutronix.de> (raw)
In-Reply-To: <b09de11deacc5486fefdab0e69b94d14596e541f.camel@analog.com>

Hi Alex,

On 19-09-18 06:59, Ardelean, Alexandru wrote:
> On Tue, 2019-09-17 at 18:09 +0200, Marco Felsch wrote:
> > [External]
> > 
> 
> Comments inline
> 
> > The device is always in a low-power state due to the hardware design. It
> > wakes up upon a conversion request and goes back into the low-power
> > state. The pm ops are added to disable the device completely and to free
> > the regulator. Disbaling the device completely should be not that
> > notable but freeing the regulator is important. Because if it is a shared
> > power-rail the regulator won't be disabled during suspend-to-ram/disk
> > and so all devices connected to that rail keeps on.
> > 
> > Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> > ---
> >  drivers/iio/adc/ad799x.c | 45 ++++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 45 insertions(+)
> > 
> > diff --git a/drivers/iio/adc/ad799x.c b/drivers/iio/adc/ad799x.c
> > index af5a2de9c22f..32d242ecb12c 100644
> > --- a/drivers/iio/adc/ad799x.c
> > +++ b/drivers/iio/adc/ad799x.c
> > @@ -875,6 +875,50 @@ static int ad799x_remove(struct i2c_client *client)
> >  	return 0;
> >  }
> >  
> > +static int __maybe_unused ad799x_suspend(struct device *dev)
> > +{
> > +	struct iio_dev *indio_dev = i2c_get_clientdata(to_i2c_client(dev));
> > +	struct ad799x_state *st = iio_priv(indio_dev);
> > +	int ret;
> > +
> > +	ret = regulator_disable(st->vref);
> > +	if (ret) {
> > +		dev_err(dev, "Unable to disable vref regulator\n");
> 
> Exiting here will leave st->reg undisabled.
> I don't know if this should do more that just disable the regulators.
> 
> I am not sure if we should print anything here if regulator_disable()
> errors. Usually (in this case) the system would go to sleep, and that's it.
> Errors would be more important in the ad799x_resume() case (than here).
> 
> But, if these messages are important, you could maybe print with
> "dev_warn()" instead of "dev_err()".
> I am not sure if errors when disabling regulators (in this case here)
> classify as errors (instead of warnings).

Yes, you're right. I will change that in such a case to disable the
regulators without checking the return val and I will change dev_err to
dev_dbg. IMHO a developer should be informed about such a case at least
during a debug session. This will help them to limit the possible
failures why a voltage rail can't be disabled.

Regards,
  Marco

> 
> > +		return ret;
> > +	}
> > +	ret = regulator_disable(st->reg);
> > +	if (ret) {
> > > +		dev_err(dev, "Unable to disable vcc regulator\n");
> > +		return ret;
> > +	}
> > +
> > +	return 0;
> > +}
> > +
> > +static int __maybe_unused ad799x_resume(struct device *dev)
> > +{
> > +	struct iio_dev *indio_dev = i2c_get_clientdata(to_i2c_client(dev));
> > +	struct ad799x_state *st = iio_priv(indio_dev);
> > +	int ret;
> > +
> > +	ret = regulator_enable(st->reg);
> > +	if (ret) {
> > +		dev_err(dev, "Unable to enable vcc regulator\n");
> > +		return ret;
> > +	}
> > +	ret = regulator_enable(st->vref);
> > +	if (ret) {
> 
> Should there be a "regulator_disable(st->reg);" call here ?
> 
> > +		dev_err(dev, "Unable to enable vref regulator\n");
> > +		return ret;
> > +	}
> > +	/* resync config */
> > +	ad799x_update_config(st, st->config);
> > +
> > +	return 0;
> > +}
> > +
> > +static SIMPLE_DEV_PM_OPS(ad799x_pm_ops, ad799x_suspend, ad799x_resume);
> > +
> >  static const struct i2c_device_id ad799x_id[] = {
> >  	{ "ad7991", ad7991 },
> >  	{ "ad7995", ad7995 },
> > @@ -892,6 +936,7 @@ MODULE_DEVICE_TABLE(i2c, ad799x_id);
> >  static struct i2c_driver ad799x_driver = {
> >  	.driver = {
> >  		.name = "ad799x",
> > +		.pm = &ad799x_pm_ops,
> >  	},
> >  	.probe = ad799x_probe,
> >  	.remove = ad799x_remove,

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2019-09-18  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 16:09 [PATCH 0/3] ADC AD799x improvements Marco Felsch
2019-09-17 16:09 ` [PATCH 1/3] iio: adc: ad799x: fix probe error handling Marco Felsch
2019-09-18  6:29   ` Ardelean, Alexandru
2019-10-05 12:38     ` Jonathan Cameron
2019-09-17 16:09 ` [PATCH 2/3] iio: adc: ad799x: factor out config register update Marco Felsch
2019-09-18  6:51   ` Ardelean, Alexandru
2019-09-18  8:52     ` Marco Felsch
2019-09-18 10:17       ` Ardelean, Alexandru
2019-09-17 16:09 ` [PATCH 3/3] iio: adc: ad799x: add pm_ops to disable the device completely Marco Felsch
2019-09-18  6:59   ` Ardelean, Alexandru
2019-09-18  8:37     ` Marco Felsch [this message]
2019-09-18  7:00 ` [PATCH 0/3] ADC AD799x improvements Ardelean, Alexandru
2019-09-18  8:22   ` Marco Felsch

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=20190918083752.nj5vtmixzvisiukn@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=StefanSerban.Popa@analog.com \
    --cc=alexandru.Ardelean@analog.com \
    --cc=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.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 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).