[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR04MB48809AFBB9DF01001AA5E2CA96C70@VI1PR04MB4880.eurprd04.prod.outlook.com>
Date: Tue, 23 Jul 2019 16:07:34 +0000
From: Claudiu Manoil <claudiu.manoil@....com>
To: Arseny Solokha <asolokha@...kras.ru>,
Ioana Ciornei <ioana.ciornei@....com>,
Russell King <linux@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [RFC PATCH 1/2] gianfar: convert to phylink
>-----Original Message-----
>From: Arseny Solokha <asolokha@...kras.ru>
>Sent: Tuesday, July 23, 2019 6:17 PM
>To: Claudiu Manoil <claudiu.manoil@....com>; Ioana Ciornei
><ioana.ciornei@....com>; Russell King <linux@...linux.org.uk>; Andrew Lunn
><andrew@...n.ch>
>Cc: netdev@...r.kernel.org; Arseny Solokha <asolokha@...kras.ru>
>Subject: [RFC PATCH 1/2] gianfar: convert to phylink
>
>Convert gianfar to use the phylink API for better SFP modules support.
>
>The driver still uses phylib for serdes configuration over the TBI
>interface, as there seems to be no functionally equivalent API present
>in phylink (yet). phylib usage is basically confined in two functions.
>
Thanks for your patch. Phylink in gianfar... that would be something!
At first glance a lot of code has changed with this patch or got relocated.
To make it easier to swallow, I think a few cleanup patches could be
separated before migrating to phylink. Like for instance getting rid of the
old* link state variables, which I think are an artifact from early phylib usage.
Nonetheless good to see this implemented, I'll have a closer look asap.
Thanks
Claudiu
Powered by blists - more mailing lists