From: Paresh Bhagat <p-bhagat@ti.com>
To: Bryan Brattlof <bb@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <praneeth@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<khasim@ti.com>, <v-singh1@ti.com>, <afd@ti.com>,
<devarsht@ti.com>, <s-vadapalli@ti.com>, <andrew@lunn.ch>
Subject: Re: [PATCH v5 1/4] arm64: dts: ti: Add bootph property to nodes at source for am62a
Date: Thu, 3 Jul 2025 11:23:37 +0530 [thread overview]
Message-ID: <dfc9feec-e385-451a-bdf0-0a02bb4b66a6@ti.com> (raw)
In-Reply-To: <20250701160828.lmmfgfrmfcqiwpzz@bryanbrattlof.com>
Hi Bryan,
On 01/07/25 21:38, Bryan Brattlof wrote:
> On June 27, 2025 thus sayeth Paresh Bhagat:
>> Add bootph property directly into the original definitions of relevant
>> nodes (e.g., power domains, USB controllers, and other peripherals)
>> within their respective DTSI files (ex. main, mcu, and wakeup) for
>> am62a.
>>
>> By defining bootph in the nodes source definitions instead of appending
>> it later in final DTS files, this change ensures that the property is
>> inherently present wherever the nodes are reused across derived device
>> trees.
>>
>> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 14 ++++++++++++++
>> arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi | 1 +
>> arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi | 2 ++
>> 3 files changed, 17 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
>> index 63e097ddf988..770f1258b0aa 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
>>
> ...
>
>> main_pmx0: pinctrl@f4000 {
>> @@ -262,6 +271,7 @@ main_pmx0: pinctrl@f4000 {
>> #pinctrl-cells = <1>;
>> pinctrl-single,register-width = <32>;
>> pinctrl-single,function-mask = <0xffffffff>;
>> + bootph-all;
>> };
> I don't think the boot phase flags for the pinmux nodes need to be here.
> The child nodes for the MMC, UART and Ethernet pins should take care of
> this.
>
> ...
>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
>> b/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
>> index ee961ced7208..df4aa131097f 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
>> @@ -12,6 +12,7 @@ mcu_pmx0: pinctrl@4084000 {
>> #pinctrl-cells = <1>;
>> pinctrl-single,register-width = <32>;
>> pinctrl-single,function-mask = <0xffffffff>;
>> + bootph-all;
>> };
> Same here. If we need any pins from the MCU domain during bootup those
> nodes can take care of adding the boot phase flag.
>
> ~Bryan
Will fix this thanks.
next prev parent reply other threads:[~2025-07-03 5:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 11:57 [PATCH v5 0/4] Add support for AM62D2 SoC and EVM Paresh Bhagat
2025-06-27 11:57 ` [PATCH v5 1/4] arm64: dts: ti: Add bootph property to nodes at source for am62a Paresh Bhagat
2025-07-01 16:08 ` Bryan Brattlof
2025-07-03 5:53 ` Paresh Bhagat [this message]
2025-06-27 11:57 ` [PATCH v5 2/4] dt-bindings: arm: ti: Add AM62D2 SoC and Boards Paresh Bhagat
2025-06-27 11:57 ` [PATCH v5 3/4] arm64: dts: ti: Add pinctrl entries for AM62D2 family of SoCs Paresh Bhagat
2025-06-27 11:57 ` [PATCH v5 4/4] arm64: dts: ti: Add support for AM62D2-EVM Paresh Bhagat
2025-07-01 16:25 ` Bryan Brattlof
2025-07-03 6:42 ` Paresh Bhagat
2025-07-03 12:20 ` Bryan Brattlof
2025-07-04 9:00 ` Paresh Bhagat
2025-07-04 4:10 ` Vignesh Raghavendra
2025-07-04 8:46 ` Paresh Bhagat
2025-07-04 4:50 ` Vignesh Raghavendra
2025-07-04 8:49 ` Paresh Bhagat
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=dfc9feec-e385-451a-bdf0-0a02bb4b66a6@ti.com \
--to=p-bhagat@ti.com \
--cc=afd@ti.com \
--cc=andrew@lunn.ch \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khasim@ti.com \
--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=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=v-singh1@ti.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
all inboxes | Powered by JetHome®