From: Andrew Davis <afd@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Abraham I <kishon@kernel.org>,
Roger Quadros <rogerq@kernel.org>,
Devarsh Thakkar <devarsht@ti.com>, Swamil Jain <s-jain1@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] arm64: ti: Use syscon for the Control Module
Date: Thu, 28 May 2026 17:59:34 -0500 [thread overview]
Message-ID: <29c9bd27-df32-4c56-8df2-987722d02b9a@ti.com> (raw)
In-Reply-To: <20260528-ti-main-conf-v1-0-a54ac5c8d081@ideasonboard.com>
On 5/28/26 7:53 AM, Tomi Valkeinen wrote:
> I have been trying to get BeagleY-AI display support to upstream:
>
> 20260513-beagley-ai-display-v2-0-9e9bcefde6bc@ideasonboard.com
>
> One difficulty has been the handling of the Control Module region, as
> we need access to a single in that region, surrounded by registers for
> other subsystems. In my series I made the related node a syscon, thus
> allowing versatile access to the registers:
>
> https://lore.kernel.org/all/20260513-beagley-ai-display-v2-14-9e9bcefde6bc@ideasonboard.com/
>
> However, that's not a correct way to handle it. I realized we already
> have ti,j721e-system-controller.yaml binding for older SoCs, which has
> syscon but it's not used for the newer TI SoCs. This series takes the
> same binding into use for the newer SoCs.
>
We moved away from this system-controller thing because it was always
a hack to allow us to poke into random control registers from nodes
throughout the DT. This was a mess and also caused issues with multiple
mappings to the same registers (some sub nodes inside the control space
also make their own mappings). If you need access to registers then make
a node with those registers in the `reg` property.
The only reason we didn't get rid of `ti,j721e-system-controller.yaml`
completely from the older SoCs was we were told it would be an ABI
break to correct those DT files. Let's not spread that problem to
new SoCs.
Andrew
> I think this is an ABI change, but I also think this is not an ABI
> break. I hope people with more expertise in this area can confirm my
> thoughts.
>
> I believe we could drop the renaming patches, and just adjust the
> ti,j721e-system-controller.yaml a bit more to accommodate the "wrong"
> node names. But if there's no downside to the renames, I think it's nice
> to have a more consistent naming.
>
> Tomi
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
> ---
> Tomi Valkeinen (6):
> arm64: dts: ti: j784s4/j742s2: Rename pcieN-ctrl nodes to pcie-ctrl
> arm64: dts: ti: k3-am62*: Rename 'clock-controller' to 'clock'
> arm64: dts: ti: k3-am62-main: Rename 'oldi-io-controller' to 'dss-oldi-io-ctrl'
> dt-bindings: soc: ti: ti,j721e-system-controller: Relax the bindings
> dt-bindings: soc: ti: ti,j721e-system-controller: Add more compatibles
> arm64: dts: ti: Use syscon and simple-mfd for the main conf region
>
> .../devicetree/bindings/soc/ti/ti,j721e-system-controller.yaml | 10 ++++++----
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 9 +++++----
> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 7 ++++---
> arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 6 +++---
> arch/arm64/boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi | 6 +++---
> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 4 ++--
> 6 files changed, 23 insertions(+), 19 deletions(-)
> ---
> base-commit: e7ae89a0c97ce2b68b0983cd01eda67cf373517d
> change-id: 20260528-ti-main-conf-d75aea5e5c2b
>
> Best regards,
> --
> Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>
>
next prev parent reply other threads:[~2026-05-28 22:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 12:53 [PATCH 0/6] arm64: ti: Use syscon for the Control Module Tomi Valkeinen
2026-05-28 12:53 ` [PATCH 1/6] arm64: dts: ti: j784s4/j742s2: Rename pcieN-ctrl nodes to pcie-ctrl Tomi Valkeinen
2026-05-28 12:53 ` [PATCH 2/6] arm64: dts: ti: k3-am62*: Rename 'clock-controller' to 'clock' Tomi Valkeinen
2026-05-28 12:53 ` [PATCH 3/6] arm64: dts: ti: k3-am62-main: Rename 'oldi-io-controller' to 'dss-oldi-io-ctrl' Tomi Valkeinen
2026-05-28 12:53 ` [PATCH 4/6] dt-bindings: soc: ti: ti,j721e-system-controller: Relax the bindings Tomi Valkeinen
2026-05-30 11:40 ` Krzysztof Kozlowski
2026-05-28 12:53 ` [PATCH 5/6] dt-bindings: soc: ti: ti,j721e-system-controller: Add more compatibles Tomi Valkeinen
2026-05-30 11:39 ` Krzysztof Kozlowski
2026-05-28 12:53 ` [PATCH 6/6] arm64: dts: ti: Use syscon and simple-mfd for the main conf region Tomi Valkeinen
2026-05-28 22:59 ` Andrew Davis [this message]
2026-06-12 10:06 ` [PATCH 0/6] arm64: ti: Use syscon for the Control Module Tomi Valkeinen
2026-06-26 11:42 ` Tomi Valkeinen
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=29c9bd27-df32-4c56-8df2-987722d02b9a@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-jain1@ti.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=vigneshr@ti.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