Re: [RFC net-next 0/2] ethtool: add interface caps and PHY tests

[Andrew Lunn <andrew@lunn.ch>]

On Wed, Sep 30, 2026 at 08:21:46AM -0500, Shubham Das wrote:
> This series adds two new ethtool netlink commands:
> 
> 1. intf-caps-get: Discovers the functional block layout of a network
>    interface. Each block represents a hardware point (MAC/PHY/MODULE) at
>    a specific 802.3 sublayer (RS/PCS/FEC/PMA/PMD) with its supported
>    capabilities (loopback, test patterns, BERT, error injection).
> 
> 2. Add ETHTOOL_MSG_PHY_TEST_GET and ETHTOOL_MSG_PHY_TEST_SET for per-block,
>   per-lane PHY testing using test patterns, BERT (Bit Error Ratio Test),
>   and error injection. The block_id from intf-caps-get identifies which
>   hardware point to test.
> 
> The block model uses:
>   - component: identifies the hardware entity (MAC, PHY, or module).
>   - sublayer: identifies the 802.3 sublayer (RS, PCS, FEC, PMA, or PMD).
>   - instance: identifies multiple instances of the same component, such as
>     internal and external PHYs.
>   - depth: identifies the host-side or line-side block within the same
>     sublayer.
> 
> Prior discussion on this proposal:
> https://lore.kernel.org/netdev/SN7PR11MB810923BBDEC398E860099150FF1B2

When adding new APIs you also need to include a user, so we can see
the API in action.

    Andrew

---
pw-bot: cr