[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181116234826.GB752@lunn.ch>
Date: Sat, 17 Nov 2018 00:48:26 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Claudiu Manoil <claudiu.manoil@....com>
Cc: "David S . Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alexandru Marginean <alexandru.marginean@....com>,
Catalin Horghidan <catalin.horghidan@....com>
Subject: Re: [PATCH net-next 1/4] enetc: Introduce basic PF and VF ENETC
ethernet drivers
> I know phylib has some limitations that are supposed to be addressed by phylink,
> but I didn't figure out yet how phylink does that or whether it works on our designs
> too.
Anything which phylib can do, phylink should also be able to do.
And phylink should make it easier to support SGMII. If you are using
the in-band signalling, you need to get that information out of the
MAC. And when you add support for 2.5G, you need to dynamically
reconfigure your SGMII link, depending on what speed the PHY decides
to do. phylink will help with that.
But you can start with phylib and convert later, if you want.
Andrew
Powered by blists - more mailing lists