From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: shawnguo@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: [PATCH 9/9] arm64: dts: lx2160ardb: add nodes for the AQR107 PHYs
Date: Fri, 25 Sep 2020 16:25:03 +0300 [thread overview]
Message-ID: <20200925132503.30206-10-ioana.ciornei@nxp.com> (raw)
In-Reply-To: <20200925132503.30206-1-ioana.ciornei@nxp.com>
Annotate the EMDIO1 node and describe the 2 AQR107 PHYs found on the
LX2160ARDB board. Also, add the necessary phy-handles for DPMACs 3 and 4
to their associated PHY.
Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
---
.../boot/dts/freescale/fsl-lx2160a-rdb.dts | 32 +++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/fsl-lx2160a-rdb.dts b/arch/arm64/boot/dts/freescale/fsl-lx2160a-rdb.dts
index 54fe8cd3a711..7723ad5efd37 100644
--- a/arch/arm64/boot/dts/freescale/fsl-lx2160a-rdb.dts
+++ b/arch/arm64/boot/dts/freescale/fsl-lx2160a-rdb.dts
@@ -35,6 +35,18 @@ &crypto {
status = "okay";
};
+&dpmac3 {
+ phy-handle = <&aquantia_phy1>;
+ phy-connection-type = "usxgmii";
+ managed = "in-band-status";
+};
+
+&dpmac4 {
+ phy-handle = <&aquantia_phy2>;
+ phy-connection-type = "usxgmii";
+ managed = "in-band-status";
+};
+
&dpmac17 {
phy-handle = <&rgmii_phy1>;
phy-connection-type = "rgmii-id";
@@ -61,6 +73,18 @@ rgmii_phy2: ethernet-phy@2 {
reg = <0x2>;
eee-broken-1000t;
};
+
+ aquantia_phy1: ethernet-phy@4 {
+ /* AQR107 PHY */
+ compatible = "ethernet-phy-ieee802.3-c45";
+ reg = <0x4>;
+ };
+
+ aquantia_phy2: ethernet-phy@5 {
+ /* AQR107 PHY */
+ compatible = "ethernet-phy-ieee802.3-c45";
+ reg = <0x5>;
+ };
};
&esdhc0 {
@@ -156,6 +180,14 @@ rtc@51 {
};
};
+&pcs_mdio3 {
+ status = "okay";
+};
+
+&pcs_mdio4 {
+ status = "okay";
+};
+
&sata0 {
status = "okay";
};
--
2.25.1
prev parent reply other threads:[~2020-09-25 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 13:24 [PATCH 0/9] arm64: dts: layerscape: update MAC nodes with PHY information Ioana Ciornei
2020-09-25 13:24 ` [PATCH 1/9] arm64: dts: ls1088a: add external MDIO device nodes Ioana Ciornei
2020-10-30 0:01 ` Shawn Guo
2020-10-30 9:26 ` Ioana Ciornei
2020-09-25 13:24 ` [PATCH 2/9] arm64: dts: ls1088ardb: add QSGMII PHY nodes Ioana Ciornei
2020-10-30 0:07 ` Shawn Guo
2020-10-30 9:32 ` Ioana Ciornei
2020-09-25 13:24 ` [PATCH 3/9] arm64: dts: ls1088ardb: add necessary DTS nodes for DPMAC2 Ioana Ciornei
2020-09-25 13:24 ` [PATCH 4/9] arm64: dts: ls208xa: add the external MDIO nodes Ioana Ciornei
2020-09-25 13:24 ` [PATCH 5/9] arm64: dts: ls2088ardb: add PHY nodes for the CS4340 PHYs Ioana Ciornei
2020-10-30 0:10 ` Shawn Guo
2020-10-30 9:40 ` Ioana Ciornei
2020-09-25 13:25 ` [PATCH 6/9] arm64: dts: ls2088ardb: add PHY nodes for the AQR405 PHYs Ioana Ciornei
2020-09-25 13:25 ` [PATCH 7/9] arm64: dts: ls208xa: add PCS MDIO and PCS PHY nodes Ioana Ciornei
2020-09-25 13:25 ` [PATCH 8/9] arm64: dts: lx2160a: " Ioana Ciornei
2020-09-25 13:25 ` Ioana Ciornei [this message]
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=20200925132503.30206-10-ioana.ciornei@nxp.com \
--to=ioana.ciornei@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
/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).