[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1d9202d8-2a01-420a-937e-216cb1cd1748@denx.de>
Date: Fri, 28 Jun 2024 01:32:05 +0200
From: Marek Vasut <marex@...x.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: linux-arm-kernel@...ts.infradead.org, Conor Dooley <conor+dt@...nel.org>,
Fabio Estevam <festevam@...il.com>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Pengutronix Kernel Team <kernel@...gutronix.de>,
Rob Herring <robh@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>, devicetree@...r.kernel.org,
imx@...ts.linux.dev, kernel@...electronics.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mp: Update Fast ethernet PHY MDIO
addresses to match DH i.MX8MP DHCOM rev.200
On 6/27/24 9:06 PM, Andrew Lunn wrote:
> On Thu, Jun 27, 2024 at 02:58:33AM +0200, Marek Vasut wrote:
>> 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.
>
> Where did the original values come from?
Preproduction rev.100 SoM .
> Did they never work?
They did work on rev.100 SoM .
> A pre-production device?
Yes
> Do we need to be worried about regressions?
No, it is only rev.200 or newer hardware that is shipping.
> It would be good if the commit message explained why this is safe.
Fixed in V2, thanks.
Powered by blists - more mailing lists