From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Shubham Das" <shubham.das@intel.com>,
netdev@vger.kernel.org, andrew@lunn.ch,
alexander.duyck@gmail.com, lee@trager.us,
"Björn Töpel" <bjorn@kernel.org>
Cc: siddaraju.dh@intel.com, balaji.chintalapalle@intel.com,
dasshubhamk@gmail.com, magnus.k.lindberg@ericsson.com,
jonas.wirandi@ericsson.com
Subject: Re: [RFC PATCH net-next 0/2] ethtool: add interface capabilities and PHY test
Date: Fri, 4 Sep 2026 09:36:49 +0200 [thread overview]
Message-ID: <a5c85a6e-918d-49a3-9a29-c0ce429fc9fd@bootlin.com> (raw)
In-Reply-To: <20260825043708.1512634-1-shubham.das@intel.com>
Hi,
On 8/25/26 06:37, 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. phy-test-get / phy-test-act: 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: which hardware entity (MAC, PHY, MODULE)
> - sublayer: which 802.3 layer (RS, PCS, FEC, PMA, PMD)
> - instance: identifies multiple instances of the same component
> (e.g., internal vs external PHY)
> - depth: host-side vs line-side within the same sublayer
+Björn,
I'll try to give this a read/test in the next days,
Maxime
>
> Prior discussion on this proposal:
> Link: https://lore.kernel.org/netdev/SN7PR11MB810923BBDEC398E860099150FF1B2@SN7PR11MB8109.namprd11.prod.outlook.com/
>
> Shubham Das (2):
> ethtool: add interface capabilities query (intf-caps-get)
> ethtool: add PHY test framework (phy-test-get, phy-test-act)
>
> Documentation/netlink/specs/ethtool.yaml | 206 ++++++++++++++++++
> include/linux/ethtool.h | 92 ++++++++
> .../uapi/linux/ethtool_netlink_generated.h | 104 +++++++++
> net/ethtool/Makefile | 2 +-
> net/ethtool/intf_caps.c | 130 +++++++++++
> net/ethtool/netlink.c | 24 ++
> net/ethtool/netlink.h | 7 +
> net/ethtool/phytest.c | 171 +++++++++++++++
> 8 files changed, 735 insertions(+), 1 deletion(-)
> create mode 100644 net/ethtool/intf_caps.c
> create mode 100644 net/ethtool/phytest.c
>
prev parent reply other threads:[~2026-09-04 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 4:37 [RFC PATCH net-next 0/2] ethtool: add interface capabilities and PHY test Shubham Das
2026-08-25 4:37 ` [RFC PATCH net-next 1/2] ethtool: add interface capabilities query (intf-caps-get) Shubham Das
2026-08-25 4:37 ` [RFC PATCH net-next 2/2] ethtool: add PHY test framework (phy-test-get, phy-test-act) Shubham Das
2026-09-04 6:44 ` [RFC PATCH net-next 0/2] ethtool: add interface capabilities and PHY test Das, Shubham
2026-09-04 7:36 ` Maxime Chevallier [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=a5c85a6e-918d-49a3-9a29-c0ce429fc9fd@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=alexander.duyck@gmail.com \
--cc=andrew@lunn.ch \
--cc=balaji.chintalapalle@intel.com \
--cc=bjorn@kernel.org \
--cc=dasshubhamk@gmail.com \
--cc=jonas.wirandi@ericsson.com \
--cc=lee@trager.us \
--cc=magnus.k.lindberg@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=shubham.das@intel.com \
--cc=siddaraju.dh@intel.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