[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN8PR12MB32660970D0294CCEE7B16B53D3350@BN8PR12MB3266.namprd12.prod.outlook.com>
Date: Mon, 13 Jan 2020 15:05:46 +0000
From: Jose Abreu <Jose.Abreu@...opsys.com>
To: Vladimir Oltean <olteanv@...il.com>
CC: Russell King - ARM Linux admin <linux@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Joao Pinto" <Joao.Pinto@...opsys.com>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC net-next] net: phy: Add basic support for Synopsys XPCS
using a PHY driver
From: Vladimir Oltean <olteanv@...il.com>
Date: Jan/13/2020, 14:55:51 (UTC+00:00)
> Clauses 72 and 73 describe some PMD link training procedure too, as
> part of auto-negotiation for 10GBase-KR. Does the XGPCS do any of
> that? Is this series sufficient for link training to work when in the
> 10GBase-KR copper backplane link mode?
Yes, its supported by the IP but not in the patch. It's working fine
without the link training procedure. Actually, Clause 72 Link training is
optional in the IP, and in the configuration I have now it's not enabled
so even if I implemented it I would need a new HW to test it.
---
Thanks,
Jose Miguel Abreu
Powered by blists - more mailing lists