From: Andreas Kemnade <andreas@kemnade.info>
To: paul@pwsan.com, aaro.koskinen@iki.fi, andreas@kemnade.info,
khilman@baylibre.com, rogerq@kernel.org, tony@atomide.com,
linux@armlinux.org.uk, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] ARM: omap: omap_hwmod: do not WARN() on missing nodes for hwmods
Date: Sat, 31 Oct 2026 13:05:19 +0100 [thread overview]
Message-ID: <20261031120519.655248-1-andreas@kemnade.info> (raw)
If devices are converted from hwmod to ti-sysc, there might be an interim
state with the hwmod data still present but the devicetree not referencing
the hwmod. In such cases, the hwmod device data is still there,
the hwmod infrastructure does ignore that device but prints out a big
alarming WARN().
Be more silent in that case to avoid needing putting devicetree and
code changes into one patch but into one series, only require the
hwmod cleanup to come after the devicetree conversion.
Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
---
arch/arm/mach-omap2/omap_hwmod.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
index 03cd523dff87..a67442a6a2c6 100644
--- a/arch/arm/mach-omap2/omap_hwmod.c
+++ b/arch/arm/mach-omap2/omap_hwmod.c
@@ -2329,8 +2329,10 @@ static int __init _init(struct omap_hwmod *oh, void *data)
r = _init_mpu_rt_base(oh, NULL, index, np);
if (r < 0) {
- WARN(1, "omap_hwmod: %s: doesn't have mpu register target base\n",
- oh->name);
+ /* there might be a transition ongoing from hwmod to ti-sys */
+ if (np)
+ WARN(1, "omap_hwmod: %s: doesn't have mpu register target base\n",
+ oh->name);
r = 0;
goto out_put_node;
}
--
2.47.3
reply other threads:[~2026-10-31 12:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261031120519.655248-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=paul@pwsan.com \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®