[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BN8PR12MB3266ADC38B505A739E24AB74D3BA0@BN8PR12MB3266.namprd12.prod.outlook.com>
Date: Fri, 6 Sep 2019 13:28:32 +0000
From: Jose Abreu <Jose.Abreu@...opsys.com>
To: Ong Boon Leong <boon.leong.ong@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"mcoquelin.stm32@...il.com" <mcoquelin.stm32@...il.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"andrew@...n.ch" <andrew@...n.ch>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peppe.cavallaro@...com" <peppe.cavallaro@...com>,
"alexandre.torgue@...com" <alexandre.torgue@...com>,
"weifeng.voon@...el.com" <weifeng.voon@...el.com>
Subject: RE: [RFC net-next v2 4/5] net: phy: introducing support for DWC xPCS
logics for EHL & TGL
From: Ong Boon Leong <boon.leong.ong@...el.com>
Date: Aug/28/2019, 18:47:21 (UTC+00:00)
> xPCS is DWC Ethernet Physical Coding Sublayer that can be integrated with
> Ethernet MAC controller and acts as converter between GMII and SGMII.
You have to be careful here because xPCS supports much more than these
interfaces and speeds.
I would implement this thinking about the future integrations and
leaving margin for more speeds.
As for this being a converter I'm not sure about the implementation
logic because sometimes you can have a setup like:
MAC <-> xPCS <-> SERDES <-> SFP
SERDES and SFP may not require configuration nor even have MDIO access
so in my view the "PHY" would then be the xPCS, no ?
---
Thanks,
Jose Miguel Abreu
Powered by blists - more mailing lists