From: Nishanth Menon <nm@ti.com>
To: Chintan Vankar <c-vankar@ti.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, <srk@ti.com>,
<s-vadapalli@ti.com>, <danishanwar@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 1/2] arm64: dts: ti: k3-am68-sk/k3-j721s2-mcu: Add bootph-all property to enable Ethernet boot
Date: Fri, 25 Apr 2025 16:24:27 -0500 [thread overview]
Message-ID: <20250425212427.vvyocc4mmne5g3vq@vividly> (raw)
In-Reply-To: <20250425051055.2393301-2-c-vankar@ti.com>
On 10:40-20250425, Chintan Vankar wrote:
> Ethernet boot requires CPSW nodes to be present starting from R5 SPL
> stage. Add bootph-all property to required nodes to enable Ethernet boot
> on AM68-SK and J721S2-EVM.
>
> Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> Signed-off-by: Chintan Vankar <c-vankar@ti.com>
> ---
>
> Link to v2:
> https://lore.kernel.org/r/20250302153502.181832-2-c-vankar@ti.com/
>
> Changes from v2 to v3:
> - Removed "bootph-all" property from "mcu_cpsw" node as suggested by
> Vignesh since child node already has that.
>
> arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts | 3 +++
> arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 3 +++
Why does every board that uses j721s2 need to have bootph-all for
cpsw? Is network boot mandatory boot mode for all boards? That does
not sound right. Just do them in the board file please.
> 2 files changed, 6 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts b/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
> index 5fa70a874d7b..c402d5e288b0 100644
> --- a/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
> @@ -344,6 +344,7 @@ J721S2_WKUP_IOPAD(0x008, PIN_OUTPUT, 0) /* (E22) MCU_RGMII1_TD3 */
> J721S2_WKUP_IOPAD(0x018, PIN_OUTPUT, 0) /* (F21) MCU_RGMII1_TXC */
> J721S2_WKUP_IOPAD(0x000, PIN_OUTPUT, 0) /* (F22) MCU_RGMII1_TX_CTL */
> >;
> + bootph-all;
> };
>
> mcu_mdio_pins_default: mcu-mdio-default-pins {
> @@ -351,6 +352,7 @@ mcu_mdio_pins_default: mcu-mdio-default-pins {
> J721S2_WKUP_IOPAD(0x034, PIN_OUTPUT, 0) /* (A21) MCU_MDIO0_MDC */
> J721S2_WKUP_IOPAD(0x030, PIN_INPUT, 0) /* (A22) MCU_MDIO0_MDIO */
> >;
> + bootph-all;
> };
>
> mcu_mcan0_pins_default: mcu-mcan0-default-pins {
> @@ -626,6 +628,7 @@ &mcu_cpsw {
> &davinci_mdio {
> phy0: ethernet-phy@0 {
> reg = <0>;
> + bootph-all;
> ti,rx-internal-delay = <DP83867_RGMIIDCTL_2_00_NS>;
> ti,fifo-depth = <DP83867_PHYCR_FIFO_DEPTH_4_B_NIB>;
> ti,min-output-impedance;
> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
> index bc31266126d0..218290b1840a 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
> @@ -154,12 +154,14 @@ mcu_conf: bus@40f00000 {
> cpsw_mac_syscon: ethernet-mac-syscon@200 {
> compatible = "ti,am62p-cpsw-mac-efuse", "syscon";
> reg = <0x200 0x8>;
> + bootph-all;
> };
>
> phy_gmii_sel: phy@4040 {
> compatible = "ti,am654-phy-gmii-sel";
> reg = <0x4040 0x4>;
> #phy-cells = <1>;
> + bootph-all;
> };
>
> };
> @@ -562,6 +564,7 @@ cpsw_port1: port@1 {
> label = "port1";
> ti,syscon-efuse = <&cpsw_mac_syscon 0x0>;
> phys = <&phy_gmii_sel 1>;
> + bootph-all;
> };
> };
>
> --
> 2.34.1
>
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2025-04-25 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 5:10 [PATCH v3 0/2] Add bootph-all property to necessary nodes to enable ethernet boot for AM68-SK, J722s and AM62p-SK Chintan Vankar
2025-04-25 5:10 ` [PATCH v3 1/2] arm64: dts: ti: k3-am68-sk/k3-j721s2-mcu: Add bootph-all property to enable Ethernet boot Chintan Vankar
2025-04-25 21:24 ` Nishanth Menon [this message]
2025-04-29 7:28 ` Chintan Vankar
2025-04-25 5:10 ` [PATCH v3 2/2] arm64: dts: ti: k3-am62p*/k3-j722s: " Chintan Vankar
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=20250425212427.vvyocc4mmne5g3vq@vividly \
--to=nm@ti.com \
--cc=c-vankar@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--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=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@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