From: Chris Morgan <macroalpha82@gmail.com>
To: linux-rockchip@lists.infradead.org
Cc: linux-pm@vger.kernel.org, jonas@kwiboo.se, pgwipeout@gmail.com,
finley.xiao@rock-chips.com, kever.yang@rock-chips.com,
shawn.lin@rock-chips.com, sebastian.reichel@collabora.com,
heiko@sntech.de, ulf.hansson@linaro.org,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH] pmdomain: rockchip: quiet regulator error on -EPROBE_DEFER
Date: Wed, 19 Nov 2025 10:12:50 -0600 [thread overview]
Message-ID: <20251119161250.60885-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
Change the dev_err() to dev_err_probe() under rockchip_pd_power_on()
to prevent errors early in the boot process when the requested
regulator is not yet available. This converts errors like the following
to debug messages:
rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to enable supply: -517
Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
---
drivers/pmdomain/rockchip/pm-domains.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/pmdomain/rockchip/pm-domains.c b/drivers/pmdomain/rockchip/pm-domains.c
index 1955c6d453e4..3c84a65de1a5 100644
--- a/drivers/pmdomain/rockchip/pm-domains.c
+++ b/drivers/pmdomain/rockchip/pm-domains.c
@@ -688,7 +688,8 @@ static int rockchip_pd_power_on(struct generic_pm_domain *domain)
ret = rockchip_pd_regulator_enable(pd);
if (ret) {
- dev_err(pd->pmu->dev, "Failed to enable supply: %d\n", ret);
+ dev_err_probe(pd->pmu->dev, ret,
+ "Failed to enable supply: %d\n", ret);
return ret;
}
--
2.43.0
next reply other threads:[~2025-11-19 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 16:12 Chris Morgan [this message]
2025-11-20 0:34 ` [PATCH] pmdomain: rockchip: quiet regulator error on -EPROBE_DEFER Shawn Lin
2026-01-27 19:50 ` Diederik de Haas
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=20251119161250.60885-1-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=pgwipeout@gmail.com \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.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