From: Bryan Brattlof <bb@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-am65: add boot phase tags
Date: Thu, 10 Jul 2025 07:33:37 -0500 [thread overview]
Message-ID: <20250710123337.ltnfhtpxaisi2yu3@bryanbrattlof.com> (raw)
In-Reply-To: <83c5d0b8-add8-4db7-bcde-5b17c796b53a@ti.com>
On July 10, 2025 thus sayeth Vignesh Raghavendra:
>
>
> On 10/07/25 04:05, Bryan Brattlof wrote:
>
> [...]
>
> > diff --git a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> > index 7cf1f646500a16c1d1bac6dfb37fb285218063b3..5bbd817bc51464f6605c5b2dc9cb544a109a695d 100644
> > --- a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> > +++ b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
> > @@ -211,6 +211,7 @@ mcu_ringacc: ringacc@2b800000 {
> > ti,sci = <&dmsc>;
> > ti,sci-dev-id = <195>;
> > msi-parent = <&inta_main_udmass>;
> > + bootph-all;
> > };
> >
> > mcu_udmap: dma-controller@285c0000 {
> > @@ -235,6 +236,7 @@ mcu_udmap: dma-controller@285c0000 {
> > ti,sci-rm-range-rchan = <0xb>, /* RX_HCHAN */
> > <0xa>; /* RX_CHAN */
> > ti,sci-rm-range-rflow = <0x0>; /* GP RFLOW */
> > + bootph-all;
> > };
> > };
>
> Should this be board specific property? Does every user of AM65x need
> DMA at boot stage?
>
Yeah. I'm not too sure how we want to handle this. Some boot modes will
require DMA up and running, but if a board only uses eMMC then we won't
need DMA during the early phases of boot.
I saw we already do this for the AM62P so I decided to keep moving in
that direction even though it's not a perfect and it seemed like a
better solution than dragging the DMA node up to the board level.
I'll drop it for now until I can think of a better idea.
> [...]
>
> > @@ -107,5 +111,6 @@ wkup_vtm0: temperature-sensor@42050000 {
> > reg = <0x42050000 0x25c>;
> > power-domains = <&k3_pds 80 TI_SCI_PD_EXCLUSIVE>;
> > #thermal-sensor-cells = <1>;
> > + bootph-all;
>
> Same here..
>
Yeah I'm assuming this is one of those weird things being in the middle
of the Jacinto and Sitara class causes. It's used, much like the rest of
the Jacinto parts, by the bootloaders to get at the voltage domain info
to configure the OPP data before the bootloader starts the A53s.
All AM65x boards will need this node to prevent an overclocking situation
if the voltage isn't high enough.
~Bryan
next prev parent reply other threads:[~2025-07-10 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 22:35 [PATCH 0/2] arm64: dts: ti: k3-am65: add boot phases to critical nodes Bryan Brattlof
2025-07-09 22:35 ` [PATCH 1/2] arm64: dts: ti: k3-am65: add boot phase tags Bryan Brattlof
2025-07-10 6:29 ` Vignesh Raghavendra
2025-07-10 12:33 ` Bryan Brattlof [this message]
2025-07-09 22:35 ` [PATCH 2/2] arm64: dts: ti: k3-am654-base-board: " Bryan Brattlof
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=20250710123337.ltnfhtpxaisi2yu3@bryanbrattlof.com \
--to=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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=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
all inboxes | Powered by JetHome®