From: Andrew Lunn <andrew@lunn.ch>
To: Claudiu Manoil <claudiu.manoil@nxp.com>
Cc: "David S . Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexandru Marginean <alexandru.marginean@nxp.com>,
Catalin Horghidan <catalin.horghidan@nxp.com>
Subject: Re: [PATCH net-next 1/4] enetc: Introduce basic PF and VF ENETC ethernet drivers
Date: Sat, 17 Nov 2018 00:48:26 +0100 [thread overview]
Message-ID: <20181116234826.GB752@lunn.ch> (raw)
In-Reply-To: <VI1PR04MB4880BE4EA7B7C0A1EEA0A0D196DD0@VI1PR04MB4880.eurprd04.prod.outlook.com>
> 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
next prev parent reply other threads:[~2018-11-16 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 16:13 [PATCH net-next 0/4] Introduce ENETC ethernet drivers Claudiu Manoil
2018-11-15 16:13 ` [PATCH net-next 1/4] enetc: Introduce basic PF and VF " Claudiu Manoil
2018-11-15 20:35 ` Andrew Lunn
2018-11-16 9:32 ` Claudiu Manoil
2018-11-16 23:48 ` Andrew Lunn [this message]
2018-11-17 0:30 ` Andrew Lunn
2018-11-19 15:09 ` Claudiu Manoil
2018-11-19 15:20 ` Andrew Lunn
2018-11-17 20:08 ` David Miller
2018-11-19 15:25 ` Claudiu Manoil
2018-11-15 16:13 ` [PATCH net-next 2/4] enetc: Add ethtool statistics Claudiu Manoil
2018-11-15 16:13 ` [PATCH net-next 3/4] enetc: Add vf to pf messaging support Claudiu Manoil
2018-11-15 16:13 ` [PATCH net-next 4/4] enetc: Add RFS and RSS support Claudiu Manoil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181116234826.GB752@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandru.marginean@nxp.com \
--cc=catalin.horghidan@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox