* Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> [190612 08:21]: > Hi Tony, > > On Wed, Jun 12, 2019 at 10:04 AM Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > Hi, > > > > * yegorslists@xxxxxxxxxxxxxx <yegorslists@xxxxxxxxxxxxxx> [190611 02:31]: > > > From: Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> > > > > > > The PHY must add both tx and rx delay and not only on the tx clock. > > > > As we're close to -rc5, I applied this against v5.2-rc1 and merged into > > omap-for-v5.3/dt as it seems it's optional or has been broken for a while > > with no fixes tag. After it hits the mainline kernel during the merge > > window you can request it be applied into the stable trees as needed. > > > > However, if this is urgent, let me know what regression it fixes and > > I'll merge it into my fixes branch too. > > This is the same fix as 759c962d3c9bb1a60e3b4b780daa66ee6d4be13a: > > ARM: dts: am335x-evmsk: Fix PHY mode for ethernet > > The PHY must add both tx and rx delay and not only on the tx clock. > The board uses AR8031_AL1A PHY where the rx delay is enabled by default, > the tx dealy is disabled. > > The reason why rgmii-txid worked because the rx delay was not disabled by > the driver so essentially we ended up with rgmii-id PHY mode. > > It seems to be working in 4.19. So I think kernels 5.0, 5.1 are the > first to be affected. Without this patch eth1 is not working on Baltos > devices. OK thanks so it's pretty regression recent then, I'll merge it into fixes too. Regards, Tony