[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y+T2oku3ocAuafe0@lunn.ch>
Date: Thu, 9 Feb 2023 14:35:30 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Sverdlin, Alexander" <alexander.sverdlin@...mens.com>
Cc: "wei.fang@....com" <wei.fang@....com>,
"xiaoning.wang@....com" <xiaoning.wang@....com>,
"shenwei.wang@....com" <shenwei.wang@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-imx@....com" <linux-imx@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net: fec: Defer probe if other FEC has deferred MDIO
> You are right, there is unfortunately no i.MX8 support in the upstream
> tree, so it's not possible to reproduce anything.
commit 947240ebcc635ab063f17ba027352c3a474d2438
Author: Fugang Duan <fugang.duan@....com>
Date: Wed Jul 28 19:51:59 2021 +0800
net: fec: add imx8mq and imx8qm new versions support
The ENET of imx8mq and imx8qm are basically the same as imx6sx,
but they have new features support based on imx6sx, like:
- imx8mq: supports IEEE 802.3az EEE standard.
- imx8qm: supports RGMII mode delayed clock.
Are you using some other imx8 SoC?
> Just wanted to discuss the probe concept of this driver, which is
> rather fragile with all there static local variables, probe call
> counters and relying on the probe order. All of this falls together
> like a house of cards if something gets deferred.
I agree with the comments about it being fragile. It would be good to
get all the naming from OF nodes/addresses. But it needs doing by
somebody with access to a test farm of lots of different boards with
IMX2/5, IMX6 through to 8 and Vybrid.
Andrew
Powered by blists - more mailing lists