From: sashiko-bot@kernel.org
To: "Wagner Popov dos Santos" <wpopov@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] ARM: dts: am33xx: avoid invalid OCP device-link for timer1 and timer2
Date: Wed, 01 Jul 2026 18:21:52 +0000 [thread overview]
Message-ID: <20260701182153.0F5B61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260701175647.8694-1-wpopov@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Using the undocumented, Linux-internal `post-init-providers` property to silence an OS warning.
--
commit be227235cebc7285a11a56bcbf6975ef2b78f927
Author: Wagner Popov dos Santos <wpopov@gmail.com>
ARM: dts: am33xx: avoid invalid OCP device-link for timer1 and timer2
This patch updates dependency handling for timer1 and timer2 on AM335x/UCC3.
It adds post-init-providers to the device nodes to avoid boot-time
fw_devlink errors caused by invalid link-creation attempts.
> diff --git a/arch/arm/boot/dts/ti/omap/am33xx.dtsi b/arch/arm/boot/dts/ti/omap/am33xx.dtsi
> index ca3e7f5d7d0dc..760598d5ae1c9 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>;
[Severity: Medium]
Does this introduce a regression by using an undocumented Linux-specific
property in the Device Tree to silence an OS warning here in timer1_target?
Since Device Tree is intended to be an OS-agnostic hardware description,
adding this internal Linux fw_devlink mechanism pollutes the DT with an
OS-specific probing workaround.
Would it be better to fix this regression in the driver core instead?
Perhaps patching fw_devlink_create_devlink() to gracefully skip link creation
when the resolved supplier is an ancestor of the consumer would address the
root cause without adding OS-specific properties to the DT.
> };
> };
>
> @@ -721,5 +722,6 @@ &timer2_target {
> timer@0 {
> assigned-clocks = <&timer2_fck>;
> assigned-clock-parents = <&sys_clkin_ck>;
> + post-init-providers = <&ocp>;
[Severity: Medium]
Does this node for timer2_target introduce the same regression mentioned
above?
> };
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260701175647.8694-1-wpopov@gmail.com?part=1
prev parent reply other threads:[~2026-07-01 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 17:56 [PATCH] ARM: dts: am33xx: avoid invalid OCP device-link for timer1 and timer2 Wagner Popov dos Santos
2026-07-01 18:21 ` sashiko-bot [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=20260701182153.0F5B61F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wpopov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.