From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "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, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
mkl@pengutronix.de, Marek Vasut <marex@denx.de>,
Christian Herber <christian.herber@nxp.com>
Subject: Re: signal quality and cable diagnostic
Date: Mon, 11 May 2020 16:33:37 +0200 [thread overview]
Message-ID: <20200511143337.GC413878@lunn.ch> (raw)
In-Reply-To: <20200511141310.GA2543@pengutronix.de>
On Mon, May 11, 2020 at 04:13:10PM +0200, Oleksij Rempel wrote:
> Hi Andrew,
>
> First of all, great work! As your cable diagnostic patches are in
> net-next now and can be used as base for the follow-up discussion.
>
> Do you already have ethtool patches somewhere? :=) Can you please give a
> link for testing?
Hi Oleksij
It was mentioned in the cover note
https://github.com/lunn/ethtool/tree/feature/cable-test-v4
>
> I continue to work on TJA11xx PHY and need to export some additional
> cable diagnostic/link stability information: Signal Quality Index (SQI).
Is this something you want to continually make available, or just as
part of cable diagnostics. Additional nested attributes can be added
to the cable test results structure, and the user space code just
dumps whatever it finds. So it should be easy to have something like:
Pair A: OK
Pair A: Signal Quality Index class D
Are the classes part of the Open Alliance specification? Ideally we
want to report something standardized, not something proprietary to
NXP.
Andrew
next prev parent reply other threads:[~2020-05-11 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 14:13 signal quality and cable diagnostic Oleksij Rempel
2020-05-11 14:33 ` Andrew Lunn [this message]
2020-05-12 8:22 ` Oleksij Rempel
2020-05-12 8:54 ` Robert Schwebel
2020-05-14 7:13 ` [EXT] " Christian Herber
2020-05-14 8:28 ` Oleksij Rempel
2020-05-11 14:59 ` Michal Kubecek
2020-05-12 6:48 ` Oleksij Rempel
2020-05-12 13:04 ` Andrew Lunn
2020-05-24 21:28 ` Pavel Machek
2020-05-26 7:06 ` PHYs with advanced cable diagnostic support Oleksij Rempel
-- strict thread matches above, loose matches on Subject: below --
2020-05-14 8:42 signal quality and cable diagnostic Christian Herber
2020-05-24 21:27 ` Pavel Machek
2020-05-24 22:42 ` Russell King - ARM Linux admin
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=20200511143337.GC413878@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).