public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org,
	"Sven Van Asbroeck" <TheSven73@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 3/8] pwm: pca9685: Improve runtime PM behavior
Date: Fri, 9 Apr 2021 18:08:10 +0200	[thread overview]
Message-ID: <YHB76i7IcVAqvTQm@workstation.tuxnet> (raw)
In-Reply-To: <YHBQmGJIsa6sNRIg@orome.fritz.box>

On Fri, Apr 09, 2021 at 03:03:20PM +0200, Thierry Reding wrote:
> On Tue, Apr 06, 2021 at 06:41:35PM +0200, Clemens Gruber wrote:
> > The chip does not come out of POR in active state but in sleep state.
> > To be sure (in case the bootloader woke it up) we force it to sleep in
> > probe.
> > 
> > On kernels without CONFIG_PM, we wake the chip in .probe and put it to
> > sleep in .remove.
> > 
> > Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
> > ---
> > Changes since v6:
> > - Improved !CONFIG_PM handling (wake it up without putting it to sleep
> >   first)
> > 
> >  drivers/pwm/pwm-pca9685.c | 26 +++++++++++++++++++-------
> >  1 file changed, 19 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/pwm/pwm-pca9685.c b/drivers/pwm/pwm-pca9685.c
> > index d4474c5ff96f..0bcec04b138a 100644
> > --- a/drivers/pwm/pwm-pca9685.c
> > +++ b/drivers/pwm/pwm-pca9685.c
> > @@ -474,13 +474,18 @@ static int pca9685_pwm_probe(struct i2c_client *client,
> >  		return ret;
> >  	}
> >  
> > -	/* The chip comes out of power-up in the active state */
> > -	pm_runtime_set_active(&client->dev);
> > -	/*
> > -	 * Enable will put the chip into suspend, which is what we
> > -	 * want as all outputs are disabled at this point
> > -	 */
> > -	pm_runtime_enable(&client->dev);
> > +	if (IS_ENABLED(CONFIG_PM)) {
> 
> This looks odd to me. I've seen similar constructs, but they usually go
> something like this (I think):
> 
> 	pm_runtime_enable(&client->dev);
> 
> 	if (!pm_runtime_enabled(&client->dev)) {
> 		/* resume device */
> 	}
> 
> Which I guess in your would be somewhat the opposite and it wouldn't
> actually resume the device but rather put it to sleep.

Yes, I wanted to keep it in sleep mode if runtime PM is supported (to be
woken up later) and otherwise just wake it up in probe.

> 
> Perhaps something like this:
> 
> 	pm_runtime_enable(&client->dev);
> 
> 	if (pm_runtime_enabled(&client->dev)) {
> 		pca9685_set_sleep_mode(pca, true);
> 		pm_runtime_set_suspended(&client->dev);
> 	} else {
> 		/* wake the chip up on non-PM environments */
> 		pca9685_set_sleep_mode(pca, false);
> 	}
> 
> ? I think that's slightly more correct than your original because it
> takes into account things like sysfs power control and such. It also
> doesn't rely on the config option alone but instead uses the runtime
> PM API to achieve this more transparently.

Ah, yes, I missed the fact that runtime could be disabled 'at runtime'
via sysfs as well, so yes, that's more correct and pm_runtime_enabled
will just return false if !CONFIG_PM, so that should work as well.

Thanks,
Clemens

  reply	other threads:[~2021-04-09 16:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 16:41 [PATCH v7 1/8] pwm: pca9685: Switch to atomic API Clemens Gruber
2021-04-06 16:41 ` [PATCH v7 2/8] pwm: pca9685: Support hardware readout Clemens Gruber
2021-04-07  5:31   ` Uwe Kleine-König
2021-04-07  7:33     ` Clemens Gruber
2021-04-07  9:09       ` Uwe Kleine-König
2021-04-07  9:53         ` Clemens Gruber
2021-04-06 16:41 ` [PATCH v7 3/8] pwm: pca9685: Improve runtime PM behavior Clemens Gruber
2021-04-09 13:03   ` Thierry Reding
2021-04-09 16:08     ` Clemens Gruber [this message]
2021-04-06 16:41 ` [PATCH v7 4/8] dt-bindings: pwm: Support new PWM_STAGGERING_ALLOWED flag Clemens Gruber
2021-04-07  5:33   ` Uwe Kleine-König
2021-04-09 12:27     ` Thierry Reding
2021-04-10 14:01       ` Uwe Kleine-König
2021-04-10 14:02   ` Uwe Kleine-König
2021-04-06 16:41 ` [PATCH v7 5/8] pwm: core: " Clemens Gruber
2021-04-07  5:46   ` Uwe Kleine-König
2021-04-07 20:21     ` Clemens Gruber
2021-04-07 21:34       ` Uwe Kleine-König
2021-04-08 12:50         ` Thierry Reding
2021-04-08 15:51           ` Clemens Gruber
2021-04-08 17:36             ` Uwe Kleine-König
2021-04-08 18:14               ` Clemens Gruber
2021-04-09 11:25               ` Thierry Reding
2021-04-09 16:02                 ` Clemens Gruber
2021-04-09 21:35                 ` Uwe Kleine-König
2021-04-09 11:10             ` Thierry Reding
2021-04-06 16:41 ` [PATCH v7 6/8] pwm: pca9685: " Clemens Gruber
2021-04-06 16:41 ` [PATCH v7 7/8] pwm: pca9685: Restrict period change for enabled PWMs Clemens Gruber
2021-04-07  6:12   ` Uwe Kleine-König
2021-04-07 20:41     ` Clemens Gruber
2021-04-07 21:38       ` Uwe Kleine-König
2021-04-06 16:41 ` [PATCH v7 8/8] pwm: pca9685: Add error messages for failed regmap calls Clemens Gruber
2021-04-07  6:16   ` Uwe Kleine-König
2021-04-07 20:47     ` Clemens Gruber
2021-04-07 21:41       ` Uwe Kleine-König
2021-04-07  5:24 ` [PATCH v7 1/8] pwm: pca9685: Switch to atomic API Uwe Kleine-König
2021-04-07  7:26   ` Clemens Gruber

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=YHB76i7IcVAqvTQm@workstation.tuxnet \
    --to=clemens.gruber@pqgruber.com \
    --cc=TheSven73@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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