From: Andrew Lunn <andrew@lunn.ch>
To: Peng Fan <peng.fan@nxp.com>
Cc: Marek Vasut <marex@denx.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"kernel@dh-electronics.com" <kernel@dh-electronics.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: imx8mp: Update Fast ethernet PHY MDIO addresses to match DH i.MX8MP DHCOM rev.200
Date: Fri, 28 Jun 2024 16:09:52 +0200 [thread overview]
Message-ID: <6687963b-1cbf-4093-aa8d-b90ce9ba7c0b@lunn.ch> (raw)
In-Reply-To: <AM6PR04MB5941804BFE1CC6F72E776F9588D02@AM6PR04MB5941.eurprd04.prod.outlook.com>
On Fri, Jun 28, 2024 at 01:01:49AM +0000, Peng Fan wrote:
> > Subject: [PATCH v2] arm64: dts: imx8mp: Update Fast ethernet PHY
> > MDIO addresses to match DH i.MX8MP DHCOM rev.200
> >
> > The production DH i.MX8MP DHCOM SoM rev.200 uses updated PHY
> > MDIO addresses for the Fast ethernet PHYs. Update the base SoM DT
> > to cater for this change.
> > Prototype rev.100 SoM was never publicly available and was
> > manufactured in limited series, anything currently available is rev.200
> > or newer, so it is safe to update the DT this way.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > ---
>
> Reviewed-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2024-06-28 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 23:30 Marek Vasut
2024-06-28 1:01 ` Peng Fan
2024-06-28 14:09 ` Andrew Lunn [this message]
2024-07-01 9:21 ` Shawn Guo
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=6687963b-1cbf-4093-aa8d-b90ce9ba7c0b@lunn.ch \
--to=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--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
all inboxes | Powered by JetHome®