[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR04MB70410EA61C984E45615CCF8B86A10@AM0PR04MB7041.eurprd04.prod.outlook.com>
Date: Mon, 11 May 2020 19:32:05 +0000
From: Christian Herber <christian.herber@....com>
To: Andrew Lunn <andrew@...n.ch>,
Oleksij Rempel <o.rempel@...gutronix.de>
CC: "David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
Jonathan Corbet <corbet@....net>,
Michal Kubecek <mkubecek@...e.cz>,
David Jander <david@...tonic.nl>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Russell King <linux@...linux.org.uk>,
"mkl@...gutronix.de" <mkl@...gutronix.de>,
Marek Vasut <marex@...x.de>
Subject: RE: Re: signal quality and cable diagnostic
On May 11, 2020 4:33:53 PM Andrew Lunn <andrew@...n.ch> wrote:
>
> Are the classes part of the Open Alliance specification? Ideally we
> want to report something standardized, not something proprietary to
> NXP.
>
> Andrew
Hi Andrew,
Such mechanisms are standardized and supported by pretty much all devices in the market. The Open Alliance specification is publicly available here: http://www.opensig.org/download/document/218/Advanced_PHY_features_for_automotive_Ethernet_V1.0.pdf
As the specification is newer than the 100BASE-T1 spec, do not expect first generation devices to follow the register definitions as per Open Alliance. But for future devices, also registers should be same across different vendors.
Christian
Powered by blists - more mailing lists