From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
"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 v1 1/1] phy: dp83td510: Utilize ALCD for cable length measurement when link is active
Date: Fri, 16 Aug 2024 16:00:20 +0200 [thread overview]
Message-ID: <Zr9bdJEG3sEdC6BI@pengutronix.de> (raw)
In-Reply-To: <f026cabc-76d3-474c-90a1-47c355a7d673@lunn.ch>
On Fri, Aug 16, 2024 at 03:10:35PM +0200, Andrew Lunn wrote:
> > The DP83TD510 PHY provides an alternative through ALCD (Active Link
> > Cable Diagnostics), which allows for cable length measurement without
> > disrupting an active link. Since a live link indicates no short or open
> > cable states, ALCD can be used effectively to gather cable length
> > information.
>
> Is this specific to TI?
It seems to be, yes. I assume they are using echo cancellation values or
some thing like this.
> Did you compare ALCD to TDR length measurement? Are they about the
> same?
Default ALCD values are about 20meters off. Which seems to be ok for
1000meter cable. TI describes calibration procedure for ALCD to provide
better measurements, but so far it was good enough. The problem with
this calibration is: it seems to be different for different cables, so
it make no sense to integrate it in kernel.
> I'm just thinking about if we want to include an additional
> attribute in ethnl_cable_test_fault_length() to indicate how the
> measurement was performed.
Sounds good. In this case user space will be able to know how to correct
this values.
Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-08-16 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 10:51 [PATCH net-next v1 1/1] phy: dp83td510: Utilize ALCD for cable length measurement when link is active Oleksij Rempel
2024-08-16 13:10 ` Andrew Lunn
2024-08-16 14:00 ` Oleksij Rempel [this message]
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=Zr9bdJEG3sEdC6BI@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=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=netdev@vger.kernel.org \
--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