[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR04MB5443DAF865284ADE78423C64FB970@AM0PR04MB5443.eurprd04.prod.outlook.com>
Date: Mon, 22 Jun 2020 14:39:54 +0000
From: Florinel Iordache <florinel.iordache@....com>
To: Andrew Lunn <andrew@...n.ch>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"hkallweit1@...il.com" <hkallweit1@...il.com>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"kuba@...nel.org" <kuba@...nel.org>,
"corbet@....net" <corbet@....net>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
Leo Li <leoyang.li@....com>,
"Madalin Bucur (OSS)" <madalin.bucur@....nxp.com>,
Ioana Ciornei <ioana.ciornei@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Florinel Iordache <florinel.iordache@....com>
Subject: RE: [EXT] Re: [PATCH net-next v3 4/7] net: phy: add backplane kr
driver support
> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: Monday, June 22, 2020 5:25 PM
> To: Florinel Iordache <florinel.iordache@....com>
> Cc: davem@...emloft.net; netdev@...r.kernel.org; f.fainelli@...il.com;
> hkallweit1@...il.com; linux@...linux.org.uk; devicetree@...r.kernel.org;
> linux-doc@...r.kernel.org; robh+dt@...nel.org; mark.rutland@....com;
> kuba@...nel.org; corbet@....net; shawnguo@...nel.org; Leo Li
> <leoyang.li@....com>; Madalin Bucur (OSS) <madalin.bucur@....nxp.com>;
> Ioana Ciornei <ioana.ciornei@....com>; linux-kernel@...r.kernel.org
> Subject: [EXT] Re: [PATCH net-next v3 4/7] net: phy: add backplane kr driver
> support
>
> Caution: EXT Email
>
> On Mon, Jun 22, 2020 at 04:35:21PM +0300, Florinel Iordache wrote:
> > Add support for backplane kr generic driver including link training
> > (ieee802.3ap/ba) and fixed equalization algorithm
>
> Hi Florinel
>
> This is still a PHY device. I don't remember any discussions which resolved the
> issues of if at the end of the backplane there is another PHY.
>
> It makes little sense to repost this code until we have this problem discussed and
> a way forward decided on. It fits into the discussion Russell and Ioana are having
> about representing PCS drivers. Please contribute to that.
>
> Andrew
Hi Andrew,
Yes, you are right: we decided to send only support for DPAA1 using current approach as a PHY device
(as mentioned in cover-letter), until PCS representation will be fully clarified.
The entire DPAA2 support was removed for now, together with phylink changes.
DPAA1 maintainer (Madalin Bucur) agrees with current representation as a PHY device for DPAA1.
So we would like to have some discussions around this approach for DPAA1 only, as it seems suitable for us.
Regards,
Florinel.
Powered by blists - more mailing lists