From: "Kumar, Udit" <u-kumar1@ti.com>
To: Apurva Nandan <a-nandan@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Hari Nagalla <hnagalla@ti.com>,
Dasnavis Sabiya <sabiya.d@mistralsolutions.com>
Subject: Re: [PATCH v4 3/3] arm64: dts: ti: k3-am69-sk: Add phase tags marking
Date: Fri, 11 Aug 2023 23:05:24 +0530 [thread overview]
Message-ID: <638d5883-5b95-403e-ecb9-8122d8774675@ti.com> (raw)
In-Reply-To: <20230811151644.3216621-4-a-nandan@ti.com>
Hi Apurva
On 8/11/2023 8:46 PM, Apurva Nandan wrote:
> bootph-all as phase tag was added to dt-schema
> (dtschema/schemas/bootph.yaml) to cover U-Boot challenges with DT.
> That's why add it also to Linux to be aligned with bootloader requirement.
>
> wkup_uart0, wkup_i2c0, mcu_uart0, main_uart8, main_sdhci0 and main_sdhci1
> are required for bootloader operation on TI K3 AM69-SK EVM. These IPs
> along with pinmuxes need to be marked for all bootloader phases, hence add
> bootph-all to these nodes in kernel dts.
>
> Signed-off-by: Apurva Nandan <a-nandan@ti.com>
> ---
> [...]
> &wkup_uart0 {
> + bootph-all;
> /* Firmware usage */
> status = "reserved";
> pinctrl-names = "default";
I am not sure, if you want to treat wkup_uart in same way as you are
treating secure_proxy_mcu in patch 1 of this series.
IMO, where we are making this node status is okay, mark booth-all at
that place only.
Otherwise for rest of series
LGTM
> @@ -249,6 +257,7 @@ &wkup_uart0 {
> };
>
> &wkup_i2c0 {
> + bootph-all;
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&wkup_i2c0_pins_default>;
> @@ -268,6 +277,7 @@ &wkup_gpio0 {
> };
>
> &mcu_uart0 {
> + bootph-all;
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&mcu_uart0_pins_default>;
> @@ -281,6 +291,7 @@ &mcu_i2c0 {
> };
>
> &main_uart8 {
> + bootph-all;
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&main_uart8_pins_default>;
> @@ -307,6 +318,7 @@ exp1: gpio@21 {
> };
>
> &main_sdhci0 {
> + bootph-all;
> /* eMMC */
> status = "okay";
> non-removable;
> @@ -315,6 +327,7 @@ &main_sdhci0 {
> };
>
> &main_sdhci1 {
> + bootph-all;
> /* SD card */
> status = "okay";
> pinctrl-0 = <&main_mmc1_pins_default>;
next prev parent reply other threads:[~2023-08-11 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 15:16 [PATCH v4 0/3] arm64: dts: ti: k3-j784s4: " Apurva Nandan
2023-08-11 15:16 ` [PATCH v4 1/3] " Apurva Nandan
2023-08-11 15:16 ` [PATCH v4 2/3] arm64: dts: ti: k3-j784s4-evm: " Apurva Nandan
2023-08-11 15:16 ` [PATCH v4 3/3] arm64: dts: ti: k3-am69-sk: " Apurva Nandan
2023-08-11 17:35 ` Kumar, Udit [this message]
2023-08-11 17:54 ` Nishanth Menon
2023-08-11 18:05 ` Kumar, Udit
2023-08-11 18:12 ` Nishanth Menon
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=638d5883-5b95-403e-ecb9-8122d8774675@ti.com \
--to=u-kumar1@ti.com \
--cc=a-nandan@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=sabiya.d@mistralsolutions.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®