On Sun, Jul 26, 2020 at 08:01:25PM -0700, Chris Healy wrote: > It appears quite a few boards were affected by this micrel PHY driver change: > > 2ccb0161a0e9eb06f538557d38987e436fc39b8d > 80bf72598663496d08b3c0231377db6a99d7fd68 > 2de00450c0126ec8838f72157577578e85cae5d8 > 820f8a870f6575acda1bf7f1a03c701c43ed5d79 > > I just updated the phy-mode with my board from rgmii to rgmii-id and > everything started working fine with net-next again:
Hi Chris Is this a mainline supported board? Do you plan to submit a patch? Laurent, does the change also work for your board? This is another one of those cases were a bug in the PHY driver, not respecting the phy-mode, has masked a bug in the device tree, using the wrong phy-mode. We had the same issue with the Atheros PHY a while back. Andrew
