In case the i.MX8MP DHCOM rev.100 has been populated on the PDK3
carrier board, the on-SoM PHY PHYAD1 signal has been pulled high
by the carrier board and changed the PHY MDIO address from 5 to 7.
This has been fixed on production rev.200 SoM by additional buffer
on the SoM PHYAD/LED signals, remove the workaround.

Signed-off-by: Marek Vasut <ma...@denx.de>
---
Cc: "NXP i.MX U-Boot Team" <uboot-...@nxp.com>
Cc: Algapally Santosh Sagar <santoshsagar.algapa...@amd.com>
Cc: Fabio Estevam <feste...@gmail.com>
Cc: Mayuresh Chitale <mchit...@ventanamicro.com>
Cc: Oleksandr Suvorov <oleksandr.suvo...@foundries.io>
Cc: Ovidiu Panait <ovpan...@gmail.com>
Cc: Roger Quadros <rog...@kernel.org>
Cc: Simon Glass <s...@chromium.org>
Cc: Stefano Babic <sba...@denx.de>
Cc: u-b...@dh-electronics.com
---
 arch/arm/dts/imx8mp-dhcom-pdk3.dts | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/arch/arm/dts/imx8mp-dhcom-pdk3.dts 
b/arch/arm/dts/imx8mp-dhcom-pdk3.dts
index c5f0607f43b..867d238f2b5 100644
--- a/arch/arm/dts/imx8mp-dhcom-pdk3.dts
+++ b/arch/arm/dts/imx8mp-dhcom-pdk3.dts
@@ -227,10 +227,6 @@
        };
 };
 
-&ethphy0g {
-       reg = <7>;
-};
-
 &fec { /* Second ethernet */
        pinctrl-0 = <&pinctrl_fec_rgmii>;
        phy-handle = <&ethphypdk>;
-- 
2.40.1

Reply via email to