[net-next,v2,0/3] Add ALCD Support to Cable Testing Interface

Message

Oleksij Rempel Aug. 20, 2024, 10:12 a.m. UTC

Hi all,

This patch series introduces support for Active Link Cable Diagnostics
(ALCD) in the ethtool cable testing interface and the DP83TD510 PHY
driver.

Why ALCD?
On a 10BaseT1L interface, TDR (Time Domain Reflectometry) is not
possible if the link partner is active - TDR will fail in these cases
because it requires interrupting the link. Since the link is active, we
already know the cable is functioning, so instead of using TDR, we can
use ALCD.

ALCD lets us measure cable length without disrupting the active link,
which is crucial in environments where network uptime is important. It
provides a way to gather diagnostic data without the need for downtime.

What's in this series:
- Extended the ethtool cable testing interface to specify the source of
  diagnostic results (TDR or ALCD).
- Updated the DP83TD510 PHY driver to use ALCD when the link is
  active, ensuring we can still get cable length info without dropping the
  connection.

Changes are described in separate patches.

Thanks,
Oleksij

Oleksij Rempel (3):
  ethtool: Extend cable testing interface with result source information
  ethtool: Add support for specifying information source in cable test
    results
  phy: dp83td510: Utilize ALCD for cable length measurement when link is
    active

 Documentation/netlink/specs/ethtool.yaml     |  6 ++
 Documentation/networking/ethtool-netlink.rst |  5 ++
 drivers/net/phy/dp83td510.c                  | 83 ++++++++++++++++++--
 include/linux/ethtool_netlink.h              | 29 +++++--
 include/uapi/linux/ethtool_netlink.h         | 11 +++
 net/ethtool/cabletest.c                      | 19 ++++-
 6 files changed, 137 insertions(+), 16 deletions(-)

--
2.39.2