[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5Cz0A19P9E61dy79BFF+V2WsAjobqQ1g9TeiJSCY2Nt4A@mail.gmail.com>
Date: Thu, 21 Mar 2019 08:17:01 -0300
From: Fabio Estevam <festevam@...il.com>
To: Abel Vesa <abel.vesa@....com>
Cc: Steve Twiss <stwiss.opensource@...semi.com>,
Andrew Lunn <andrew@...n.ch>, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
dl-linux-imx <linux-imx@....com>,
DEVICETREE <devicetree@...r.kernel.org>,
LINUX-ARM-KERNEL <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
Support Opensource <Support.Opensource@...semi.com>
Subject: Re: [PATCH] ARM: dts: imx6qdl-sabresd: change phy-mode to use rgmii-id
Hi Abel,
On Thu, Mar 21, 2019 at 5:42 AM Abel Vesa <abel.vesa@....com> wrote:
> > It seems we have other boards that need to be fixed and we can not
> > have an old dtb with functional Ethernet with a new kernel.
> >
> > Does anyone know if this issue is AR8031 specific?
>
> I can confirm the same fix is works on imx6sx too.
imx6sx-sabresd also uses an AR8031 Ethernet PHY.
I also tested that changing the phy-mode to "rgmii-id" fixes Ethernet
on pico-imx7d with AR8035.
So yes, we currently have lots of broken dtb's in mainline and I am
wondering what is the proper fix here.
Does anyone know what was the kernel commit that introduced such regressions?
Powered by blists - more mailing lists