From: Andrew Lunn <andrew@lunn.ch>
To: Michael Walle <michael@walle.cc>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next 4/4] net: phy: bcm54140: add cable diagnostics support
Date: Sun, 10 May 2020 16:44:51 +0200 [thread overview]
Message-ID: <20200510144451.GJ362499@lunn.ch> (raw)
In-Reply-To: <20200509223714.30855-5-michael@walle.cc>
On Sun, May 10, 2020 at 12:37:14AM +0200, Michael Walle wrote:
> Use the generic cable tester functions from bcm-phy-lib to add cable
> tester support.
>
> 100m cable, A/B/C/D open:
> Cable test started for device eth0.
> Cable test completed for device eth0.
> Pair: Pair A, result: Open Circuit
> Pair: Pair B, result: Open Circuit
> Pair: Pair C, result: Open Circuit
> Pair: Pair D, result: Open Circuit
> Pair: Pair A, fault length: 106.60m
> Pair: Pair B, fault length: 103.32m
> Pair: Pair C, fault length: 104.96m
> Pair: Pair D, fault length: 106.60m
>
> 1m cable, A/B connected, pair C shorted, D open:
> Cable test started for device eth0.
> Cable test completed for device eth0.
> Pair: Pair A, result: OK
> Pair: Pair B, result: OK
> Pair: Pair C, result: Short within Pair
> Pair: Pair D, result: Open Circuit
> Pair: Pair C, fault length: 0.82m
> Pair: Pair D, fault length: 1.64m
>
> 1m cable, A/B connected, pair C shorted with D:
> Cable test started for device eth0.
> Cable test completed for device eth0.
> Pair: Pair A, result: OK
> Pair: Pair B, result: OK
> Pair: Pair C, result: Short to another pair
> Pair: Pair D, result: Short to another pair
> Pair: Pair C, fault length: 1.64m
> Pair: Pair D, fault length: 1.64m
>
> The granularity of the length measurement seems to be 82cm.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2020-05-10 14:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 22:37 [PATCH net-next 0/4] net: phy: broadcom: cable tester support Michael Walle
2020-05-09 22:37 ` [PATCH net-next 1/4] net: phy: broadcom: add exp register access methods without buslock Michael Walle
2020-05-09 23:47 ` Florian Fainelli
2020-05-10 14:32 ` Andrew Lunn
2020-05-09 22:37 ` [PATCH net-next 2/4] net: phy: broadcom: add bcm_phy_modify_exp() Michael Walle
2020-05-09 23:48 ` Florian Fainelli
2020-05-10 14:33 ` Andrew Lunn
2020-05-09 22:37 ` [PATCH net-next 3/4] net: phy: broadcom: add cable test support Michael Walle
2020-05-10 0:09 ` Florian Fainelli
2020-05-10 2:20 ` kbuild test robot
2020-05-10 2:20 ` kbuild test robot
2020-05-10 14:44 ` Andrew Lunn
2020-05-10 14:51 ` Michael Walle
2020-05-09 22:37 ` [PATCH net-next 4/4] net: phy: bcm54140: add cable diagnostics support Michael Walle
2020-05-10 0:05 ` kbuild test robot
2020-05-10 0:05 ` kbuild test robot
2020-05-10 0:09 ` Florian Fainelli
2020-05-10 5:37 ` kbuild test robot
2020-05-10 5:37 ` kbuild test robot
2020-05-10 14:44 ` Andrew Lunn [this message]
2020-05-10 18:21 ` [PATCH net-next 0/4] net: phy: broadcom: cable tester support Jakub Kicinski
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=20200510144451.GJ362499@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.