[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ae34d3f-a44d-47ab-8bf1-d87366d24fc8@lunn.ch>
Date: Thu, 27 Jun 2024 21:06:51 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Marek Vasut <marex@...x.de>
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 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? Did they never work? A
pre-production device? Do we need to be worried about regressions?
It would be good if the commit message explained why this is safe.
Andrew
Powered by blists - more mailing lists