Hi all, Am Dienstag, dem 09.03.2021 um 12:26 +0100 schrieb Oleksij Rempel: > changes v2: > - rebase against latest kernel > - fix networking on RIoTBoard > > This patch series tries to remove most of the imx6 and imx7 board > specific PHY configuration via fixup, as this breaks the PHYs when > connected to switch chips or USB Ethernet MACs. > > Each patch has the possibility to break boards, but contains a > recommendation to fix the problem in a more portable and future-proof > way.
I agree with the opinion that those PHY fixups introduce more harm than good. Essentially they are pushing board specific configuration values into the PHY, without any checks that the fixup is even running on the specific board it was targeted at. While there is a real chance to break some out of tree boards or incomplete configs I think that's something we can accept here. If someone makes a case why they can absolutely not fixup their DT or kernel config we could even bring back some of those fixups with a proper board compatible check to avoid mashing things up for other boards with the same PHY. I guess the only realistic way to learn if someone can make such a case is to apply this series and look for any fallout. So for what it is worth: Acked-by: Lucas Stach <l.st...@pengutronix.de> > regards, > Oleksij > > Oleksij Rempel (7): > ARM: imx6q: remove PHY fixup for KSZ9031 > ARM: imx6q: remove TX clock delay of ar8031_phy_fixup() > ARM: imx6q: remove hand crafted PHY power up in ar8035_phy_fixup() > ARM: imx6q: remove clk-out fixup for the Atheros AR8031 and AR8035 > PHYs > ARM: imx6q: remove Atheros AR8035 SmartEEE fixup > ARM: imx6sx: remove Atheros AR8031 PHY fixup > ARM: imx7d: remove Atheros AR8031 PHY fixup > > arch/arm/boot/dts/imx6dl-riotboard.dts | 2 + > arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts | 2 +- > arch/arm/mach-imx/mach-imx6q.c | 85 ------------------------- > arch/arm/mach-imx/mach-imx6sx.c | 26 -------- > arch/arm/mach-imx/mach-imx7d.c | 22 ------- > 5 files changed, 3 insertions(+), 134 deletions(-) >
