From: Shawn Guo <shawnguo@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] arm64: dts: ls2080a-rdb: add phy nodes
Date: Mon, 22 Aug 2022 11:41:05 +0800 [thread overview]
Message-ID: <20220822034105.GR149610@dragon> (raw)
In-Reply-To: <20220817204357.21753-4-leoyang.li@nxp.com>
On Wed, Aug 17, 2022 at 03:43:54PM -0500, Li Yang wrote:
> Define PHY nodes on the board.
>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
> ---
> .../boot/dts/freescale/fsl-ls2080a-rdb.dts | 68 +++++++++++++++++++
> 1 file changed, 68 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls2080a-rdb.dts b/arch/arm64/boot/dts/freescale/fsl-ls2080a-rdb.dts
> index 44894356059c..fec02fd754be 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls2080a-rdb.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls2080a-rdb.dts
> @@ -23,3 +23,71 @@ chosen {
> stdout-path = "serial1:115200n8";
> };
> };
> +
> +&dpmac5 {
> + phy-handle = <&mdio2_phy1>;
> + phy-connection-type = "10gbase-r";
> +};
> +
> +&dpmac6 {
> + phy-handle = <&mdio2_phy2>;
> + phy-connection-type = "10gbase-r";
> +};
> +
> +&dpmac7 {
> + phy-handle = <&mdio2_phy3>;
> + phy-connection-type = "10gbase-r";
> +};
> +
> +&dpmac8 {
> + phy-handle = <&mdio2_phy4>;
> + phy-connection-type = "10gbase-r";
> +};
> +
> +&emdio1 {
> + status = "disabled";
> +
> + /* CS4340 PHYs */
> + mdio1_phy1: emdio1-phy@1 {
> + reg = <0x10>;
unit-address doesn't match 'reg'.
> + };
> +
> + mdio1_phy2: emdio1-phy@2 {
> + reg = <0x11>;
> + };
> +
> + mdio1_phy3: emdio1-phy@3 {
> + reg = <0x12>;
> + };
> +
> + mdio1_phy4: emdio1-phy@4 {
> + reg = <0x13>;
> + };
> +};
> +
> +&emdio2 {
> + /* AQR405 PHYs */
> + mdio2_phy1: emdio2-phy@1 {
> + compatible = "ethernet-phy-ieee802.3-c45";
> + interrupts = <0 1 0x4>; /* Level high type */
What does '0' mean here? And why not IRQ_TYPE_LEVEL_HIGH for polarity
cell?
Shawn
> + reg = <0x0>;
> + };
> +
> + mdio2_phy2: emdio2-phy@2 {
> + compatible = "ethernet-phy-ieee802.3-c45";
> + interrupts = <0 2 0x4>; /* Level high type */
> + reg = <0x1>;
> + };
> +
> + mdio2_phy3: emdio2-phy@3 {
> + compatible = "ethernet-phy-ieee802.3-c45";
> + interrupts = <0 4 0x4>; /* Level high type */
> + reg = <0x2>;
> + };
> +
> + mdio2_phy4: emdio2-phy@4 {
> + compatible = "ethernet-phy-ieee802.3-c45";
> + interrupts = <0 5 0x4>; /* Level high type */
> + reg = <0x3>;
> + };
> +};
> --
> 2.37.1
>
next prev parent reply other threads:[~2022-08-22 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 20:43 [PATCH v2 0/6] ls208xa dts updates Li Yang
2022-08-17 20:43 ` [PATCH v2 1/6] arm64: dts: ls2080a-qds: add mdio mux nodes from on-board FPGA Li Yang
2022-08-22 3:44 ` Shawn Guo
2022-08-17 20:43 ` [PATCH v2 2/6] arm64: dts: ls2088a-qds: " Li Yang
2022-08-17 20:43 ` [PATCH v2 3/6] arm64: dts: ls2080a-rdb: add phy nodes Li Yang
2022-08-22 3:41 ` Shawn Guo [this message]
2022-08-17 20:43 ` [PATCH v2 4/6] arm64: dts: ls2081a-rdb: Add DTS for NXP LS2081ARDB Li Yang
2022-08-22 3:46 ` Shawn Guo
2022-08-17 20:43 ` [PATCH v2 5/6] arm64: dts: ls208xa-rdb: fix errata E-00013 Li Yang
2022-08-17 20:43 ` [PATCH v2 6/6] arm64: dts: ls208x: remove NXP Erratum A008585 from LS2088A Li Yang
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=20220822034105.GR149610@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).