From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Can Peng <pengcan@kylinos.cn>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
rajat.khandelwal@linux.intel.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] iio: pressure: mpl115: Fix runtime PM cleanup on probe failure
Date: Sat, 18 Jul 2026 23:14:25 +0100 [thread overview]
Message-ID: <20260718231414.07ead912@jic23-huawei> (raw)
In-Reply-To: <20260718061909.428476-1-pengcan@kylinos.cn>
On Sat, 18 Jul 2026 14:19:09 +0800
Can Peng <pengcan@kylinos.cn> wrote:
> mpl115_probe() enables runtime PM when a shutdown GPIO is present and
> then returns the result of devm_iio_device_register(). If registration
> fails, runtime PM remains enabled and autosuspend remains selected.
>
> The same unmanaged runtime PM state is also left behind on driver
> unbind, as the IIO device registration is managed but the runtime PM
> setup is not.
>
> Use devm_pm_runtime_enable() so runtime PM is disabled automatically
> on probe failure and driver unbind. Also unwind the initial
> pm_runtime_get_noresume() reference if setting up runtime PM fails
> before the matching put.
>
> Fixes: 0c3a333524a3 ("iio: pressure: mpl115: Implementing low power mode by shutdown gpio")
> Cc: stable@vger.kernel.org
> Signed-off-by: Can Peng <pengcan@kylinos.cn>
Hi Can Peng,
A similar code pattern came up recently based as bold claim from sashiko
that autosuspend won't kick in if we don't do a get / put pair.
Turned out not to be true. If no one touches the runtime pm counts
and turns runtime pm on, then this line:
https://elixir.bootlin.com/linux/v7.1.3/source/drivers/base/dd.c#L872
becomes relevant. That ends up calling auto suspend.
Please chase through this call sequence just in case we got it wrong!
Hence I believe this is a simplification change that can be made here.
> ---
> drivers/iio/pressure/mpl115.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/pressure/mpl115.c b/drivers/iio/pressure/mpl115.c
> index 16e112b796ba..9e77b76bd1fa 100644
> --- a/drivers/iio/pressure/mpl115.c
> +++ b/drivers/iio/pressure/mpl115.c
> @@ -204,8 +204,17 @@ int mpl115_probe(struct device *dev, const char *name,
> if (data->shutdown) {
> /* Enable runtime PM */
> pm_runtime_get_noresume(dev);
Drop this get_noresume()
> - pm_runtime_set_active(dev);
> - pm_runtime_enable(dev);
> + ret = pm_runtime_set_active(dev);
> + if (ret) {
> + pm_runtime_put_noidle(dev);
No need for the put here
> + return ret;
> + }
> +
> + ret = devm_pm_runtime_enable(dev);
> + if (ret) {
> + pm_runtime_put_noidle(dev);
or here.
The switch to devm_pm_runtime_enable() and error checks all look good
to me.
> + return ret;
> + }
>
> /*
> * As the device takes 3 ms to come up with a fresh
and the pm_runtime_put() at end of this block
We don't mind if auto runtime suspend happens a tiny bit later.
prev parent reply other threads:[~2026-07-18 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 6:19 [PATCH] iio: pressure: mpl115: Fix runtime PM cleanup on probe failure Can Peng
2026-07-18 22:14 ` Jonathan Cameron [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=20260718231414.07ead912@jic23-huawei \
--to=jonathan.cameron@oss.qualcomm.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pengcan@kylinos.cn \
--cc=rajat.khandelwal@linux.intel.com \
--cc=stable@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