[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eca707a6-7161-4efc-9831-69fbfa56eb93@lunn.ch>
Date: Thu, 13 Nov 2025 14:28:17 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: Susheela Doddagoudar <susheelavin@...il.com>, netdev@...r.kernel.org,
mkubecek@...e.cz, Hariprasad Kelam <hkelam@...vell.com>,
Lee Trager <lee@...ger.us>, Alexander Duyck <alexanderduyck@...com>
Subject: Re: Ethtool: advance phy debug support
On Thu, Nov 13, 2025 at 12:11:08PM +0100, Maxime Chevallier wrote:
> Hi,
>
> On 13/11/2025 06:12, Susheela Doddagoudar wrote:
> > Hi All/ Michal Kubecek,
> >
> > To support Advanced PHY Debug operations like
> > PRBS pattern tests, EHM tests, TX_EQ settings, Various PHY loopback etc.....
>
> Added a bunch of people in CC:
>
> I don't have feedback on your current proposition, however people have
> showed interest in what you mention, it may be a good idea to get everyone
> in the loop.
>
> For the Loopback you're mentionning, there's this effort here [1] that
> Hariprasad is working on, it may be a good idea to sync the effort :)
>
> [1] : https://lore.kernel.org/netdev/20251024044849.1098222-1-hkelam@marvell.com/
>
> As for the PRBS, there was a discussion on this at the last Netdevconf,
> see the slides and talk here [2], I've added Lee in CC but I don't
> really know what's the state of that work.
>
> [2] : https://netdevconf.info/0x19/sessions/talk/open-source-tooling-for-phy-management-and-testing.html
For PRBS pattern tests testing i think there needs to be a framework
around it.
When you enable testing, the netif becomes usable, so its state needs
changing to "under test" as defined in RFC2863. We ideally want it
revert to normal operation after a time period. There are a number of
different PRBS patterns, so you need to be able to select one, and
maybe pass the test duration. It can also be performed in different
places. 802.3 defines a number of registers in the PCS for this. I
would expect to see a library that any standards conforming PCS can
use. There are also PHYs which support this features, but each vendor
implements it differently, so we need some sort of generic API for
PHYs. I expect we will also end up with a set of netlink message,
similar to how cable testing working.
Andrew
Powered by blists - more mailing lists