From: Jiawen Liu <1298662399@qq.com>
To: Deepak Saxena <dsaxena@plexity.net>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, Jiawen Liu <1298662399@qq.com>
Subject: [PATCH v2] char: omap-rng: fix runtime PM cleanup
Date: Fri, 4 Sep 2026 14:26:54 +0400 [thread overview]
Message-ID: <tencent_0D4EB3807DBF6095A7F5A9455D902DBA9708@qq.com> (raw)
In-Reply-To: <tencent_1DBD00BAFF365506D40F166D40DEE8F63B0A@qq.com>
omap_rng_probe() enables runtime PM before requesting its optional clocks.
If either devm_clk_get() returns -EPROBE_DEFER, the direct return leaves
the runtime PM usage count elevated and runtime PM enabled. The second
clock lookup can also leave the first clock enabled.
Route each deferred-probe path through resource-matched cleanup. Return
directly after cleanup so normal probe deferrals remain quiet.
Fixes: 43ec540e6f9b ("hwrng: omap - move clock related code to omap_rng_probe()")
Cc: stable@vger.kernel.org
Signed-off-by: Jiawen Liu <1298662399@qq.com>
---
Changes in v2:
- Use the full author name in From and Signed-off-by.
- Return directly after deferred-probe cleanup to keep deferrals quiet.
- Add Fixes and Cc stable tags.
v1: https://lore.kernel.org/all/tencent_1DBD00BAFF365506D40F166D40DEE8F63B0A@qq.com/
Sashiko review: https://sashiko.dev/#/patchset/tencent_1DBD00BAFF365506D40F166D40DEE8F63B0A%40qq.com
drivers/char/hw_random/omap-rng.c | 22 ++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/drivers/char/hw_random/omap-rng.c b/drivers/char/hw_random/omap-rng.c
index 5e8b50f15db7..c22d70a031e2 100644
--- a/drivers/char/hw_random/omap-rng.c
+++ b/drivers/char/hw_random/omap-rng.c
@@ -459,8 +459,10 @@ static int omap_rng_probe(struct platform_device *pdev)
}
priv->clk = devm_clk_get(&pdev->dev, NULL);
- if (PTR_ERR(priv->clk) == -EPROBE_DEFER)
- return -EPROBE_DEFER;
+ if (PTR_ERR(priv->clk) == -EPROBE_DEFER) {
+ ret = -EPROBE_DEFER;
+ goto err_pm_runtime;
+ }
if (!IS_ERR(priv->clk)) {
ret = clk_prepare_enable(priv->clk);
if (ret) {
@@ -471,8 +473,10 @@ static int omap_rng_probe(struct platform_device *pdev)
}
priv->clk_reg = devm_clk_get(&pdev->dev, "reg");
- if (PTR_ERR(priv->clk_reg) == -EPROBE_DEFER)
- return -EPROBE_DEFER;
+ if (PTR_ERR(priv->clk_reg) == -EPROBE_DEFER) {
+ ret = -EPROBE_DEFER;
+ goto err_pm_runtime_clock_1;
+ }
if (!IS_ERR(priv->clk_reg)) {
ret = clk_prepare_enable(priv->clk_reg);
if (ret) {
@@ -497,6 +501,16 @@ static int omap_rng_probe(struct platform_device *pdev)
return 0;
+err_pm_runtime_clock_1:
+ if (!IS_ERR(priv->clk))
+ clk_disable_unprepare(priv->clk);
+ goto err_pm_runtime;
+
+err_pm_runtime:
+ pm_runtime_put_sync(&pdev->dev);
+ pm_runtime_disable(&pdev->dev);
+ return ret;
+
err_register:
priv->base = NULL;
pm_runtime_put_sync(&pdev->dev);
--
2.34.1
prev parent reply other threads:[~2026-09-04 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 13:28 [PATCH] char: omap-rng: fix runtime PM cleanup Jiawen Liu
2026-09-04 9:46 ` Herbert Xu
2026-09-04 10:26 ` Jiawen Liu [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=tencent_0D4EB3807DBF6095A7F5A9455D902DBA9708@qq.com \
--to=1298662399@qq.com \
--cc=dsaxena@plexity.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
/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