From: Wagner Popov dos Santos <wpopov@gmail.com>
To: AaroKoskinenaaro.koskinen@iki.fi
Cc: AndreasKemnadeandreas@kemnade.info,
KevinHilmankhilman@baylibre.com, RogerQuadrosrogerq@kernel.org,
TonyLindgrentony@atomide.com, RobHerringrobh@kernel.org,
KrzysztofKozlowskikrzk+dt@kernel.org,
ConorDooleyconor+dt@kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] ARM: dts: am33xx: avoid invalid OCP device-link for timers
Date: Thu, 25 Jun 2026 09:55:22 -0300 [thread overview]
Message-ID: <fec5175f-8533-494e-af5b-1abe26f6d83b@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: 0001-ARM-dts-am33xx-avoid-invalid-OCP-device-link-for-tim.patch --]
[-- Type: text/x-diff, Size: 1829 bytes --]
From 6d482ff72d1a11a5851602717a48eb3e059946d4 Mon Sep 17 00:00:00 2001
From: Wagner Popov dos Santos <wpopov@gmail.com>
Date: Wed, 24 Jun 2026 13:28:02 -0300
Subject: [PATCH] ARM: dts: am33xx: avoid invalid OCP device-link for timers
This patch fixes boot-time fw_devlink errors on AM335x/UCC3 caused
by invalid device-link creation attempts involving timer1/timer2
and supplier ocp.
Observed kernel log messages:
ti-sysc 44e31000.target-module: Failed to create device link (0x180)
with supplier ocp for
/ocp/interconnect@44c00000/segment@200000/target-module@31000/timer@0
ti-sysc 48040000.target-module: Failed to create device link (0x180)
with supplier ocp for
/ocp/interconnect@48000000/segment@0/target-module@40000/timer@0
The change updates dependency handling for timer1 and timer2 so the
kernel no longer attempts this invalid link-creation path during
initialization of supplier ocp.
Impact:
- Removes the two ti-sysc/fw_devlink error messages at boot
- Preserves current timer and clock assignment behavior
- No functional regression observed in boot and timer operation tests
Signed-off-by: Wagner Popov dos Santos <wpopov@gmail.com>
---
arch/arm/boot/dts/ti/omap/am33xx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/ti/omap/am33xx.dtsi b/arch/arm/boot/dts/ti/omap/am33xx.dtsi
index ca3e7f5d7d0d..760598d5ae1c 100644
--- a/arch/arm/boot/dts/ti/omap/am33xx.dtsi
+++ b/arch/arm/boot/dts/ti/omap/am33xx.dtsi
@@ -708,6 +708,7 @@ &timer1_target {
timer@0 {
assigned-clocks = <&timer1_fck>;
assigned-clock-parents = <&sys_clkin_ck>;
+ post-init-providers = <&ocp>;
};
};
@@ -721,5 +722,6 @@ &timer2_target {
timer@0 {
assigned-clocks = <&timer2_fck>;
assigned-clock-parents = <&sys_clkin_ck>;
+ post-init-providers = <&ocp>;
};
};
--
2.43.0
reply other threads:[~2026-06-25 12:55 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=fec5175f-8533-494e-af5b-1abe26f6d83b@gmail.com \
--to=wpopov@gmail.com \
--cc=AaroKoskinenaaro.koskinen@iki.fi \
--cc=AndreasKemnadeandreas@kemnade.info \
--cc=ConorDooleyconor+dt@kernel.org \
--cc=KevinHilmankhilman@baylibre.com \
--cc=KrzysztofKozlowskikrzk+dt@kernel.org \
--cc=RobHerringrobh@kernel.org \
--cc=RogerQuadrosrogerq@kernel.org \
--cc=TonyLindgrentony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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