From: Shawn Guo <shawnguo@kernel.org>
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>, Andy Duan <fugang.duan@nxp.com>
Subject: Re: [PATCH 4/5] arch: arm64: dts: imx8mq/m/n/p: add mac address for FEC
Date: Fri, 15 Jan 2021 17:18:48 +0800 [thread overview]
Message-ID: <20210115091847.GJ28365@dragon> (raw)
In-Reply-To: <DB8PR04MB6795D05432EC545786ADD880E6AA0@DB8PR04MB6795.eurprd04.prod.outlook.com>
On Tue, Jan 12, 2021 at 10:42:19AM +0000, Joakim Zhang wrote:
>
> > -----Original Message-----
> > From: Shawn Guo <shawnguo@kernel.org>
> > Sent: 2021年1月5日 8:35
> > To: Joakim Zhang <qiangqing.zhang@nxp.com>
> > Cc: s.hauer@pengutronix.de; festevam@gmail.com;
> > devicetree@vger.kernel.org; dl-linux-imx <linux-imx@nxp.com>; Andy Duan
> > <fugang.duan@nxp.com>
> > Subject: Re: [PATCH 4/5] arch: arm64: dts: imx8mq/m/n/p: add mac address
> > for FEC
> >
> > On Thu, Nov 19, 2020 at 05:52:48PM +0800, Joakim Zhang wrote:
> > > Add mac address in efuse, so that FEC driver can parse it from nvmem
> > > cell.
> > >
> > > Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
> > > ---
> > > arch/arm64/boot/dts/freescale/imx8mm.dtsi | 7 +++++++
> > > arch/arm64/boot/dts/freescale/imx8mn.dtsi | 7 +++++++
> > > arch/arm64/boot/dts/freescale/imx8mp.dtsi | 7 +++++++
> > > arch/arm64/boot/dts/freescale/imx8mq.dtsi | 7 +++++++
> > > 4 files changed, 28 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/freescale/imx8mm.dtsi
> > > b/arch/arm64/boot/dts/freescale/imx8mm.dtsi
> > > index 367174031a90..0fbff13a9629 100644
> > > --- a/arch/arm64/boot/dts/freescale/imx8mm.dtsi
> > > +++ b/arch/arm64/boot/dts/freescale/imx8mm.dtsi
> > > @@ -521,6 +521,10 @@
> > > cpu_speed_grade: speed-grade@10 {
> > > reg = <0x10 4>;
> > > };
> > > +
> > > + fec_mac_address: mac-address@640 {
> >
> > Shouldn't the unit-address be @90 rather than @640?
>
>
> Hi Shann, @90 is a offset, @640 is an absolute address, which one is prefer to you? Thanks.
My point was that unit-address should match 'reg' property.
Shawn
next prev parent reply other threads:[~2021-01-15 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 9:52 [PATCH 0/5] arch: arm64: imx:patches for FEC Joakim Zhang
2020-11-19 9:52 ` [PATCH 1/5] arch: arm64: imx6ul/sx/qdl: add wakeup support via magic packet Joakim Zhang
2021-01-05 0:33 ` Shawn Guo
2020-11-19 9:52 ` [PATCH 2/5] arch: arm64: imx8mm/n/p: correct assigned clocks for FEC Joakim Zhang
2021-01-05 0:34 ` Shawn Guo
2020-11-19 9:52 ` [PATCH 3/5] arch: arm64: dts: imx8mq: assign clock parents " Joakim Zhang
2020-11-19 9:52 ` [PATCH 4/5] arch: arm64: dts: imx8mq/m/n/p: add mac address " Joakim Zhang
2021-01-05 0:35 ` Shawn Guo
2021-01-12 10:42 ` Joakim Zhang
2021-01-15 9:18 ` Shawn Guo [this message]
2020-11-19 9:52 ` [PATCH 5/5] arch: arm64: dts: imx8mq/m/n/p: add fsl,stop-mode property " Joakim Zhang
2020-12-03 10:54 ` [PATCH 0/5] arch: arm64: imx:patches " Joakim Zhang
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=20210115091847.GJ28365@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=linux-imx@nxp.com \
--cc=qiangqing.zhang@nxp.com \
--cc=s.hauer@pengutronix.de \
/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).