From: Andrew Lunn <andrew@lunn.ch>
To: Christian Herber <christian.herber@nxp.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Michal Kubecek <mkubecek@suse.cz>,
David Jander <david@protonic.nl>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
"mkl@pengutronix.de" <mkl@pengutronix.de>,
Marek Vasut <marex@denx.de>
Subject: Re: Re: signal quality and cable diagnostic
Date: Mon, 11 May 2020 21:54:35 +0200 [thread overview]
Message-ID: <20200511195435.GF413878@lunn.ch> (raw)
In-Reply-To: <AM0PR04MB70410EA61C984E45615CCF8B86A10@AM0PR04MB7041.eurprd04.prod.outlook.com>
On Mon, May 11, 2020 at 07:32:05PM +0000, Christian Herber wrote:
> On May 11, 2020 4:33:53 PM Andrew Lunn <andrew@lunn.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.
Hi Christian
Since we are talking about a kernel/user API definition here, i don't
care about the exact registers. What is important is the
naming/representation of the information. It seems like NXP uses Class
A - Class H, where as the standard calls them SQI=0 - SQI=7. So we
should name the KAPI based on the standard, not what NXP calls them.
Andrew
next prev parent reply other threads:[~2020-05-11 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 19:32 Re: signal quality and cable diagnostic Christian Herber
2020-05-11 19:54 ` Andrew Lunn [this message]
2020-05-12 5:13 ` Oleksij Rempel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200511195435.GF413878@lunn.ch \
--to=andrew@lunn.ch \
--cc=christian.herber@nxp.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marex@denx.de \
--cc=mkl@pengutronix.de \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).