From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 3/3] net: phy: dp83tg720: Add cable testing support
Date: Sun, 11 Aug 2024 17:32:51 +0200 [thread overview]
Message-ID: <0aaf3031-f63f-4ba1-a017-ee2c7e673abc@lunn.ch> (raw)
In-Reply-To: <20240811052005.1013512-3-o.rempel@pengutronix.de>
On Sun, Aug 11, 2024 at 07:20:05AM +0200, Oleksij Rempel wrote:
> Introduce cable testing support for the DP83TG720 PHY. This implementation
> is based on the "DP83TG720S-Q1: Configuring for Open Alliance Specification
> Compliance (Rev. B)" application note.
>
> The feature has been tested with cables of various lengths:
> - No cable: 1m till open reported.
> - 5 meter cable: reported properly.
> - 20 meter cable: reported as 19m.
> - 40 meter cable: reported as cable ok.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2024-08-11 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 5:20 [PATCH net-next v4 1/3] ethtool: Add new result codes for TDR diagnostics Oleksij Rempel
2024-08-11 5:20 ` [PATCH net-next v4 2/3] phy: Add Open Alliance helpers for the PHY framework Oleksij Rempel
2024-08-11 9:21 ` Russell King (Oracle)
2024-08-11 15:33 ` Andrew Lunn
2024-08-11 5:20 ` [PATCH net-next v4 3/3] net: phy: dp83tg720: Add cable testing support Oleksij Rempel
2024-08-11 15:32 ` Andrew Lunn [this message]
2024-08-11 15:29 ` [PATCH net-next v4 1/3] ethtool: Add new result codes for TDR diagnostics Andrew Lunn
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=0aaf3031-f63f-4ba1-a017-ee2c7e673abc@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®