From: Andrew Davis <afd@ti.com>
To: 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>,
Bryan Brattlof <bb@ti.com>, Le Jin <le.jin@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andrew Davis <afd@ti.com>
Subject: [PATCH 07/11] arm64: dts: ti: k3-am65: Enable MDIO nodes at the board level
Date: Fri, 28 Oct 2022 09:24:13 -0500 [thread overview]
Message-ID: <20221028142417.10642-8-afd@ti.com> (raw)
In-Reply-To: <20221028142417.10642-1-afd@ti.com>
MDIO nodes defined in the top-level AM65x SoC dtsi files are incomplete
and will not be functional unless they are extended with a pinmux.
As the attached PHY is only known about at the board integration level,
these nodes should only be enabled when provided with this information.
Disable the MDIO nodes in the dtsi files and only enable the ones that
are actually pinned out on a given board.
Signed-off-by: Andrew Davis <afd@ti.com>
---
arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 12 ------------
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 3 +++
arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 1 +
arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 13 +------------
4 files changed, 5 insertions(+), 24 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
index 56562081a8e52..35af8798f208e 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
@@ -732,18 +732,6 @@ &mcu_r5fss0_core1 {
mboxes = <&mailbox0_cluster1 &mbox_mcu_r5fss0_core1>;
};
-&icssg0_mdio {
- status = "disabled";
-};
-
-&icssg1_mdio {
- status = "disabled";
-};
-
-&icssg2_mdio {
- status = "disabled";
-};
-
&mcasp0 {
status = "disabled";
};
diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
index fbb631c7664d2..9cdde6e25e7de 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
@@ -1078,6 +1078,7 @@ icssg0_mdio: mdio@32400 {
#address-cells = <1>;
#size-cells = <0>;
bus_freq = <1000000>;
+ status = "disabled";
};
};
@@ -1219,6 +1220,7 @@ icssg1_mdio: mdio@32400 {
#address-cells = <1>;
#size-cells = <0>;
bus_freq = <1000000>;
+ status = "disabled";
};
};
@@ -1360,6 +1362,7 @@ icssg2_mdio: mdio@32400 {
#address-cells = <1>;
#size-cells = <0>;
bus_freq = <1000000>;
+ status = "disabled";
};
};
};
diff --git a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
index 7a11501bad0bc..22f30174621e2 100644
--- a/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi
@@ -278,6 +278,7 @@ davinci_mdio: mdio@f00 {
clocks = <&k3_clks 5 10>;
clock-names = "fck";
bus_freq = <1000000>;
+ status = "disabled";
};
cpts@3d000 {
diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
index 0c63c24941061..beac2c563e831 100644
--- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
+++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
@@ -533,6 +533,7 @@ &mcu_cpsw {
};
&davinci_mdio {
+ status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&mcu_mdio_pins_default>;
@@ -563,15 +564,3 @@ &mcasp2 {
&dss {
status = "disabled";
};
-
-&icssg0_mdio {
- status = "disabled";
-};
-
-&icssg1_mdio {
- status = "disabled";
-};
-
-&icssg2_mdio {
- status = "disabled";
-};
--
2.37.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-28 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 14:24 [PATCH 00/11] AM65x Disable Incomplete DT Nodes Andrew Davis
2022-10-28 14:24 ` [PATCH 01/11] arm64: dts: ti: k3-am65: Enable UART nodes at the board level Andrew Davis
2022-10-28 14:24 ` [PATCH 02/11] arm64: dts: ti: k3-am65: Enable I2C " Andrew Davis
2022-10-28 14:24 ` [PATCH 03/11] arm64: dts: ti: k3-am65: Enable SPI " Andrew Davis
2022-10-28 14:24 ` [PATCH 04/11] arm64: dts: ti: k3-am65: Enable EPWM " Andrew Davis
2022-10-28 14:24 ` [PATCH 05/11] arm64: dts: ti: k3-am65: Enable ECAP " Andrew Davis
2022-10-28 14:24 ` [PATCH 06/11] arm64: dts: ti: k3-am65: MDIO pinmux should belong to the MDIO node Andrew Davis
2022-10-28 14:24 ` Andrew Davis [this message]
2022-10-28 14:24 ` [PATCH 08/11] arm64: dts: ti: k3-am65: Enable MCAN nodes at the board level Andrew Davis
2022-10-28 14:24 ` [PATCH 09/11] arm64: dts: ti: k3-am65: Enable PCIe " Andrew Davis
2022-10-28 14:24 ` [PATCH 10/11] arm64: dts: ti: k3-am65: Enable Mailbox " Andrew Davis
2022-10-28 14:24 ` [PATCH 11/11] arm64: dts: ti: k3-am65: Enable McASP " Andrew Davis
2022-10-31 14:54 ` [PATCH 00/11] AM65x Disable Incomplete DT Nodes Bryan Brattlof
2022-11-03 13:20 ` Jan Kiszka
2022-11-04 2:57 ` 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=20221028142417.10642-8-afd@ti.com \
--to=afd@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=le.jin@siemens.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).