From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 03/11] arm64: dts: ls1088a: add external MDIO device nodes
Date: Fri, 30 Oct 2020 09:22:34 +0000 [thread overview]
Message-ID: <20201030091942.t2h6f4rdp4uhcaqa@skbuf> (raw)
In-Reply-To: <20201030081617.GM28755@dragon>
On Fri, Oct 30, 2020 at 04:16:21PM +0800, Shawn Guo wrote:
> On Mon, Oct 26, 2020 at 06:09:57PM +0200, Ioana Ciornei wrote:
> > Add the external MDIO device nodes found in the WRIOP global memory
> > region. This is needed for management of external PHYs.
> >
> > Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
> > ---
> > Changes in v2:
> > - removed the 0x from the unit addresses
> > Changes in v3:
> > - none
> > Changes in v4:
> > - none
> >
> > arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
> > index ff5805206a28..aea42e9e947f 100644
> > --- a/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
> > +++ b/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
> > @@ -672,6 +672,24 @@ ptp-timer@8b95000 {
> > fsl,extts-fifo;
> > };
> >
> > + emdio1: mdio@8b96000 {
> > + compatible = "fsl,fman-memac-mdio";
> > + reg = <0x0 0x8B96000 0x0 0x1000>;
>
> Use lowercase for hex values.
>
Sure, will change in next version.
Ioana
next prev parent reply other threads:[~2020-10-30 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 16:09 [PATCH v4 00/11] arm64: dts: layerscape: update MAC nodes with PHY information Ioana Ciornei
2020-10-26 16:09 ` [PATCH v4 01/11] dt-bindings: net: add the DPAA2 MAC DTS definition Ioana Ciornei
2020-10-26 16:09 ` [PATCH v4 02/11] dt-bindings: net: add the 10gbase-r connection type Ioana Ciornei
2020-10-26 16:09 ` [PATCH v4 03/11] arm64: dts: ls1088a: add external MDIO device nodes Ioana Ciornei
2020-10-30 8:16 ` Shawn Guo
2020-10-30 9:22 ` Ioana Ciornei [this message]
2020-10-26 16:09 ` [PATCH v4 04/11] arm64: dts: ls1088ardb: add QSGMII PHY nodes Ioana Ciornei
2020-10-26 16:09 ` [PATCH v4 05/11] arm64: dts: ls1088ardb: add necessary DTS nodes for DPMAC2 Ioana Ciornei
2020-10-26 16:10 ` [PATCH v4 06/11] arm64: dts: ls208xa: add the external MDIO nodes Ioana Ciornei
2020-10-26 16:10 ` [PATCH v4 07/11] arm64: dts: ls2088ardb: add PHY nodes for the CS4340 PHYs Ioana Ciornei
2020-10-26 16:10 ` [PATCH v4 08/11] arm64: dts: ls2088ardb: add PHY nodes for the AQR405 PHYs Ioana Ciornei
2020-10-26 16:10 ` [PATCH v4 09/11] arm64: dts: ls208xa: add PCS MDIO and PCS PHY nodes Ioana Ciornei
2020-10-26 16:10 ` [PATCH v4 10/11] arm64: dts: lx2160a: " Ioana Ciornei
2020-10-26 16:10 ` [PATCH v4 11/11] 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=20201030091942.t2h6f4rdp4uhcaqa@skbuf \
--to=ioana.ciornei@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@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).