[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB8PR04MB67951448528CEA7DF6661611E6619@DB8PR04MB6795.eurprd04.prod.outlook.com>
Date: Fri, 26 Mar 2021 13:18:52 +0000
From: Joakim Zhang <qiangqing.zhang@....com>
To: Andrew Lunn <andrew@...n.ch>
CC: Florian Fainelli <f.fainelli@...il.com>,
"hkallweit1@...il.com" <hkallweit1@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: FEC unbind/bind feature
> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: 2021年3月26日 20:34
> To: Joakim Zhang <qiangqing.zhang@....com>
> Cc: Florian Fainelli <f.fainelli@...il.com>; hkallweit1@...il.com;
> netdev@...r.kernel.org
> Subject: Re: FEC unbind/bind feature
>
> > One more add, yes, I am looking the drivers/net/mdio, it is better to
> implement standalone MDIO driver when writing the MAC driver at the
> beginning.
> > Now if I abstract MDIO driver from FEC driver, dt bindings would change, it
> will break all existing implementations in the kernel based on FEC driver, let
> them can't work.
> > How to compatible the legacy dt bindings? I have no idea now. At the same
> time, I also feel that it seems not necessary to rewrite it.
>
> I have a reasonable understanding of the FEC MDIO driver. I have broken it a
> few times :-)
>
> It is going to be hard to make it an independent driver, because it needs access
> to the interrupt flags and the clocks for power saving. From a hardware
> perspective, it is not an independent hardware block, it is integrated into the
> MAC.
>
> XDP probably is your easier path.
Thanks Andrew for your share, you mean use XDP instead DPDK, right?
Best Regards,
Joakim Zhang
> Andrew
Powered by blists - more mailing lists