From: Peng Fan <peng.fan@oss.nxp.com>
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
linux-clk@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] clk: imx: scu: fix autosuspend cleanup on probe failure
Date: Mon, 10 Aug 2026 21:03:24 +0800 [thread overview]
Message-ID: <annMHHQGlxTgzRkp@shlinux89> (raw)
In-Reply-To: <20260808082933.2692878-1-lgs201920130244@gmail.com>
Hi,
On Sat, Aug 08, 2026 at 04:29:33PM +0800, Guangshuo Li wrote:
>imx_clk_scu_probe() calls pm_runtime_use_autosuspend() for non-CPU
>clocks, but its probe failure paths do not call the matching
>pm_runtime_dont_use_autosuspend() before disabling runtime PM.
>
>If the autosuspend delay is set to a negative value while autosuspend
>is enabled, the runtime PM core increments usage_count to prevent
>runtime suspend. Without calling pm_runtime_dont_use_autosuspend()
>during cleanup, this reference is not dropped and usage_count remains
>unbalanced.
>
>Add the missing pm_runtime_dont_use_autosuspend() calls to the probe
>failure paths before disabling runtime PM.
>
>This issue was found by manual code inspection.
>
>Fixes: 78edeb080330 ("clk: imx: scu: add runtime pm support")
>Cc: stable@vger.kernel.org
>Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
>---
> drivers/clk/imx/clk-scu.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
>diff --git a/drivers/clk/imx/clk-scu.c b/drivers/clk/imx/clk-scu.c
>index 9b33df9967ec..6d29fcc2306d 100644
>--- a/drivers/clk/imx/clk-scu.c
>+++ b/drivers/clk/imx/clk-scu.c
>@@ -542,6 +542,7 @@ static int imx_clk_scu_probe(struct platform_device *pdev)
> ret = pm_runtime_resume_and_get(dev);
> if (ret) {
> pm_genpd_remove_device(dev);
>+ pm_runtime_dont_use_autosuspend(dev);
> pm_runtime_disable(dev);
> return ret;
> }
>@@ -550,6 +551,9 @@ static int imx_clk_scu_probe(struct platform_device *pdev)
> hw = __imx_clk_scu(dev, clk->name, clk->parents, clk->num_parents,
> clk->rsrc, clk->clk_type);
> if (IS_ERR(hw)) {
>+ if (!(clk->rsrc == IMX_SC_R_A35 || clk->rsrc == IMX_SC_R_A53 ||
>+ clk->rsrc == IMX_SC_R_A72))
>+ pm_runtime_dont_use_autosuspend(dev);
> pm_runtime_disable(dev);
> return PTR_ERR(hw);
This is not complete fix. I just write one, see below:
imx_clk_scu_probe() sets up runtime PM for non-CPU clocks by calling
pm_runtime_use_autosuspend(), pm_runtime_enable(), and
pm_runtime_resume_and_get(). The probe failure paths do not properly
undo these operations:
1. When pm_runtime_resume_and_get() fails, pm_runtime_dont_use_autosuspend()
is not called before pm_runtime_disable(), leaving the autosuspend
setting unbalanced.
2. When __imx_clk_scu() fails, pm_runtime_disable() is called
unconditionally even for CPU clocks, which never had pm_runtime_enable()
called, causing an unbalanced disable depth. For non-CPU clocks,
neither pm_runtime_put_noidle() nor pm_runtime_dont_use_autosuspend()
are called, leaving both the usage count and autosuspend setting
unbalanced.
Fix the first path by adding pm_runtime_dont_use_autosuspend() before
pm_runtime_disable(). Fix the second path by guarding all three cleanup
calls — pm_runtime_put_noidle(), pm_runtime_dont_use_autosuspend(), and
pm_runtime_disable() — with the non-CPU clock check.
Fixes: 78edeb080330 ("clk: imx: scu: add runtime pm support")
Signed-off-by: Peng Fan <peng.fan@nxp.com>
diff --git a/drivers/clk/imx/clk-scu.c b/drivers/clk/imx/clk-scu.c
index 9b33df9967ece..63ab4801ddaa7 100644
--- a/drivers/clk/imx/clk-scu.c
+++ b/drivers/clk/imx/clk-scu.c
@@ -542,6 +542,7 @@ static int imx_clk_scu_probe(struct platform_device *pdev)
ret = pm_runtime_resume_and_get(dev);
if (ret) {
pm_genpd_remove_device(dev);
+ pm_runtime_dont_use_autosuspend(dev);
pm_runtime_disable(dev);
return ret;
}
@@ -550,7 +551,12 @@ static int imx_clk_scu_probe(struct platform_device *pdev)
hw = __imx_clk_scu(dev, clk->name, clk->parents, clk->num_parents,
clk->rsrc, clk->clk_type);
if (IS_ERR(hw)) {
- pm_runtime_disable(dev);
+ if (!((clk->rsrc == IMX_SC_R_A35) || (clk->rsrc == IMX_SC_R_A53) ||
+ (clk->rsrc == IMX_SC_R_A72))) {
+ pm_runtime_put_noidle(dev);
+ pm_runtime_dont_use_autosuspend(dev);
+ pm_runtime_disable(dev);
+ }
return PTR_ERR(hw);
}
Regards,
Peng
> }
>--
>2.43.0
>
prev parent reply other threads:[~2026-08-10 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 8:29 [PATCH] clk: imx: scu: fix autosuspend cleanup on probe failure Guangshuo Li
2026-08-10 13:03 ` Peng Fan [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=annMHHQGlxTgzRkp@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=abelvesa@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=bmasney@redhat.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=lgs201920130244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--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