From: Michael Walle <mwalle@kernel.org> To: 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> Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Michael Walle <mwalle@kernel.org> Subject: [PATCH] arm64: dts: ti: k3-j722s: Disable ethernet ports by default Date: Tue, 2 Apr 2024 17:18:02 +0200 [thread overview] Message-ID: <20240402151802.3803708-1-mwalle@kernel.org> (raw) Device tree best practice is to disable any external interface in the dtsi and just enable them if needed in the device tree. Thus, disable both ethernet ports by default and just enable the one used by the EVM in its device tree. There is no functional change. Signed-off-by: Michael Walle <mwalle@kernel.org> --- This should also be true for all the other SoCs. But I don't wanted to touch all the (older) device trees. j722s is pretty new, so there we should get it right. --- arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 5 +---- arch/arm64/boot/dts/ti/k3-j722s.dtsi | 8 ++++++++ 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts index d045dc7dde0c..afe7f68e6a4b 100644 --- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts +++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts @@ -224,14 +224,11 @@ cpsw3g_phy0: ethernet-phy@0 { }; &cpsw_port1 { + status = "okay"; phy-mode = "rgmii-rxid"; phy-handle = <&cpsw3g_phy0>; }; -&cpsw_port2 { - status = "disabled"; -}; - &main_gpio1 { status = "okay"; }; diff --git a/arch/arm64/boot/dts/ti/k3-j722s.dtsi b/arch/arm64/boot/dts/ti/k3-j722s.dtsi index c75744edb143..d0451e6e7496 100644 --- a/arch/arm64/boot/dts/ti/k3-j722s.dtsi +++ b/arch/arm64/boot/dts/ti/k3-j722s.dtsi @@ -83,6 +83,14 @@ &inta_main_dmss { ti,interrupt-ranges = <7 71 21>; }; +&cpsw_port1 { + status = "disabled"; +}; + +&cpsw_port2 { + status = "disabled"; +}; + &oc_sram { reg = <0x00 0x70000000 0x00 0x40000>; ranges = <0x00 0x00 0x70000000 0x40000>; -- 2.39.2
WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <mwalle@kernel.org> To: 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> Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Michael Walle <mwalle@kernel.org> Subject: [PATCH] arm64: dts: ti: k3-j722s: Disable ethernet ports by default Date: Tue, 2 Apr 2024 17:18:02 +0200 [thread overview] Message-ID: <20240402151802.3803708-1-mwalle@kernel.org> (raw) Device tree best practice is to disable any external interface in the dtsi and just enable them if needed in the device tree. Thus, disable both ethernet ports by default and just enable the one used by the EVM in its device tree. There is no functional change. Signed-off-by: Michael Walle <mwalle@kernel.org> --- This should also be true for all the other SoCs. But I don't wanted to touch all the (older) device trees. j722s is pretty new, so there we should get it right. --- arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 5 +---- arch/arm64/boot/dts/ti/k3-j722s.dtsi | 8 ++++++++ 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts index d045dc7dde0c..afe7f68e6a4b 100644 --- a/arch/arm64/boot/dts/ti/k3-j722s-evm.dts +++ b/arch/arm64/boot/dts/ti/k3-j722s-evm.dts @@ -224,14 +224,11 @@ cpsw3g_phy0: ethernet-phy@0 { }; &cpsw_port1 { + status = "okay"; phy-mode = "rgmii-rxid"; phy-handle = <&cpsw3g_phy0>; }; -&cpsw_port2 { - status = "disabled"; -}; - &main_gpio1 { status = "okay"; }; diff --git a/arch/arm64/boot/dts/ti/k3-j722s.dtsi b/arch/arm64/boot/dts/ti/k3-j722s.dtsi index c75744edb143..d0451e6e7496 100644 --- a/arch/arm64/boot/dts/ti/k3-j722s.dtsi +++ b/arch/arm64/boot/dts/ti/k3-j722s.dtsi @@ -83,6 +83,14 @@ &inta_main_dmss { ti,interrupt-ranges = <7 71 21>; }; +&cpsw_port1 { + status = "disabled"; +}; + +&cpsw_port2 { + status = "disabled"; +}; + &oc_sram { reg = <0x00 0x70000000 0x00 0x40000>; ranges = <0x00 0x00 0x70000000 0x40000>; -- 2.39.2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-04-02 15:18 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-02 15:18 Michael Walle [this message] 2024-04-02 15:18 ` [PATCH] arm64: dts: ti: k3-j722s: Disable ethernet ports by default Michael Walle 2024-04-02 16:13 ` Nishanth Menon 2024-04-02 16:13 ` Nishanth Menon 2024-04-02 16:16 ` Michael Walle 2024-04-02 16:16 ` Michael Walle 2024-04-02 16:19 ` Nishanth Menon 2024-04-02 16:19 ` Nishanth Menon 2024-04-02 16:58 ` Francesco Dolcini 2024-04-02 16:58 ` Francesco Dolcini 2024-04-03 7:35 ` Michael Walle 2024-04-03 7:35 ` Michael Walle
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=20240402151802.3803708-1-mwalle@kernel.org \ --to=mwalle@kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.