From: Florian Fainelli <f.fainelli@gmail.com>
To: Ioana Ciornei <ioana.ciornei@nxp.com>,
davem@davemloft.net, netdev@vger.kernel.org
Cc: shawnguo@kernel.org, robh+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [RESEND net-next 2/9] arm64: dts: ls1088ardb: add QSGMII PHY nodes
Date: Fri, 2 Oct 2020 08:37:03 -0700 [thread overview]
Message-ID: <02d2d46c-8a88-2d44-f8b7-ed73cae93eda@gmail.com> (raw)
In-Reply-To: <20201002144847.13793-3-ioana.ciornei@nxp.com>
On 10/2/2020 7:48 AM, Ioana Ciornei wrote:
> Annotate the external MDIO1 node and describe the 8 QSGMII PHYs found on
> the LS1088ARDB board and add phy-handles for DPMACs 3-10 to its
> associated PHY. Also, add the internal PCS MDIO nodes for the internal
> MDIO buses found on the LS1088A SoC along with their internal PCS PHY
> and link the corresponding DPMAC to the PCS through the pcs-handle.
>
> Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
> ---
> .../boot/dts/freescale/fsl-ls1088a-rdb.dts | 100 ++++++++++++++++++
> .../arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 50 +++++++++
> 2 files changed, 150 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1088a-rdb.dts b/arch/arm64/boot/dts/freescale/fsl-ls1088a-rdb.dts
> index 5633e59febc3..d7886b084f7f 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1088a-rdb.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1088a-rdb.dts
> @@ -17,6 +17,98 @@ / {
> compatible = "fsl,ls1088a-rdb", "fsl,ls1088a";
> };
>
> +&dpmac3 {
> + phy-handle = <&mdio1_phy5>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_0>;
from net-next/master
git grep 'pcs-handle' Documentation/devicetree/bindings/*
zsh: exit 1 git grep 'pcs-handle' Documentation/devicetree/bindings/*
Is there a binding that we are missing?
--
Florian
next prev parent reply other threads:[~2020-10-02 15:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 14:48 [RESEND net-next 0/9] arm64: dts: layerscape: update MAC nodes with PHY information Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 1/9] arm64: dts: ls1088a: add external MDIO device nodes Ioana Ciornei
2020-10-02 15:33 ` Florian Fainelli
2020-10-02 15:46 ` Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 2/9] arm64: dts: ls1088ardb: add QSGMII PHY nodes Ioana Ciornei
2020-10-02 15:37 ` Florian Fainelli [this message]
2020-10-02 15:48 ` Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 3/9] arm64: dts: ls1088ardb: add necessary DTS nodes for DPMAC2 Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 4/9] arm64: dts: ls208xa: add the external MDIO nodes Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 5/9] arm64: dts: ls2088ardb: add PHY nodes for the CS4340 PHYs Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 6/9] arm64: dts: ls2088ardb: add PHY nodes for the AQR405 PHYs Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 7/9] arm64: dts: ls208xa: add PCS MDIO and PCS PHY nodes Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 8/9] arm64: dts: lx2160a: " Ioana Ciornei
2020-10-02 14:48 ` [RESEND net-next 9/9] arm64: dts: lx2160ardb: add nodes for the AQR107 PHYs Ioana Ciornei
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=02d2d46c-8a88-2d44-f8b7-ed73cae93eda@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).