[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f026cabc-76d3-474c-90a1-47c355a7d673@lunn.ch>
Date: Fri, 16 Aug 2024 15:10:35 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Oleksij Rempel <o.rempel@...gutronix.de>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
kernel@...gutronix.de, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next v1 1/1] phy: dp83td510: Utilize ALCD for cable
length measurement when link is active
> 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?
Did you compare ALCD to TDR length measurement? Are they about the
same? 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.
Andrew
Powered by blists - more mailing lists