[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200317163802.GZ24270@lunn.ch>
Date: Tue, 17 Mar 2020 17:38:02 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Russell King <rmk+kernel@...linux.org.uk>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [RFC net-next 2/5] net: phylink: add separate pcs operations
structure
On Tue, Mar 17, 2020 at 02:52:51PM +0000, Russell King wrote:
> *NOT FOR MERGING*
>
> Add a separate set of PCS operations, which MAC drivers can use to
> couple phylink with their associated MAC PCS layer. The PCS
> operations include:
>
> - pcs_get_state() - reads the link up/down, resolved speed, duplex
> and pause from the PCS.
> - pcs_config() - configures the PCS for the specified mode, PHY
> interface type, and setting the advertisement.
> - pcs_an_restart() - restarts 802.3 in-band negotiation with the
> link partner
> - pcs_link_up() - informs the PCS that link has come up, and the
> parameters of the link. Link parameters are used to program the
> PCS for fixed speed and non-inband modes.
Hi Russell
This API makes sense. But it seems quite common to have multiple
PCS's. Rather than have MAC drivers implement their own mux, i wonder
if there should be core support? Or at least a library to help the
implementation?
Andrew
Powered by blists - more mailing lists