From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH v2 3/5] pmdomain: warn if deep probe enabled and driver missing
Date: Mon, 27 Oct 2025 20:28:18 +0100 [thread overview]
Message-ID: <20251027192938.2586566-3-a.fatoum@barebox.org> (raw)
In-Reply-To: <20251027192938.2586566-1-a.fatoum@barebox.org>
We shall require any deep probe platforms to have a power domain driver,
even if just a dummy. Otherwise a warning will be printed.
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
v1 -> v2:
- no change
---
drivers/base/power.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/drivers/base/power.c b/drivers/base/power.c
index 0cdece210d94..c291f8657cbb 100644
--- a/drivers/base/power.c
+++ b/drivers/base/power.c
@@ -385,8 +385,18 @@ static int __genpd_dev_pm_attach(struct device *dev,
if (ret == -ENOENT)
ret = -EPROBE_DEFER;
- if (!have_genpd_providers && ret == -EPROBE_DEFER)
- return 0;
+ if (ret == -EPROBE_DEFER) {
+ /*
+ * New platforms should have power domain drivers, even if
+ * they don't do anything.
+ */
+ if (deep_probe_is_supported()) {
+ dev_warn(dev, "power domain not found (ignoring)\n");
+ return 0;
+ }
+ if (!have_genpd_providers)
+ return 0;
+ }
/*
* Assume that missing genpds are unresolved
--
2.47.3
next prev parent reply other threads:[~2025-10-27 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:28 [PATCH v2 1/5] regulator: implement dev_of_regulator_get Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 2/5] pmdomain: look up pmdomain even if not have_genpd_providers Ahmad Fatoum
2025-10-27 19:28 ` Ahmad Fatoum [this message]
2025-10-27 19:28 ` [PATCH v2 4/5] pmdomain: allow callback for when devices are attached Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 5/5] pmdomain: add Rockchip power domain support Ahmad Fatoum
2025-10-28 8:57 ` Sascha Hauer
2025-10-28 9:04 ` Ahmad Fatoum
2025-10-28 9:48 ` Sascha Hauer
2025-10-28 10:41 ` Ahmad Fatoum
2025-10-28 10:46 ` Sascha Hauer
2025-10-28 11:01 ` Ahmad Fatoum
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=20251027192938.2586566-3-a.fatoum@barebox.org \
--to=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.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