Thread (9 messages) flat view 9 messages, 2 authors, 2021-03-29

Re: FEC unbind/bind feature

From: Andrew Lunn <andrew@lunn.ch>
Date: 2021-03-26 13:37:39

On Fri, Mar 26, 2021 at 01:18:52PM +0000, Joakim Zhang wrote:
quoted
-----Original Message-----
From: Andrew Lunn <andrew@lunn.ch>
Sent: 2021年3月26日 20:34
To: Joakim Zhang <redacted>
Cc: Florian Fainelli <f.fainelli@gmail.com>; hkallweit1@gmail.com;
netdev@vger.kernel.org
Subject: Re: FEC unbind/bind feature
quoted
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.
quoted
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.
quoted
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?
Yes. We have much more control over XDP since it is in kernel, and
uses kernel drivers. No need to unbind the FEC, since the FEC is the
driver used by XDP. The down side is, the FEC has not been optimised
for XDP, so you will be using the generic support. Its performance
won't be optimal. To get that, you need to add native XDP support to
the FEC driver.

    Andrew
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help