Netdev List
 help / color / mirror / Atom feed
From: Paul Greenwalt <paul.greenwalt@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, Paul Greenwalt <paul.greenwalt@intel.com>
Subject: [PATCH iwl-next 0/3] idpf: add devlink info support with selftest
Date: Fri, 14 Aug 2026 13:49:16 -0400	[thread overview]
Message-ID: <20260814174919.4177289-1-paul.greenwalt@intel.com> (raw)

Add initial devlink info support for idpf and a matching selftest.

Patch 1 fixes probe unwind by clearing drvdata on the error path.

Patch 2 introduces an idpf devlink instance and reports:
  - serial_number: device serial number for NIPA CI identification
  - fw.mgmt.api (running): driver-device communication protocol version

This follows a phased approach and reports stable, readily-available
information. Firmware version support will be added in future patches as it
becomes available through virtchnl.

Patch 3 adds a hardware selftest that validates basic devlink info
reporting and matches test patterns used by NIPA CI.

Paul Greenwalt (3):
  idpf: clear drvdata on probe error path
  idpf: add devlink info support
  selftests: net: hw: add devlink info test

 Documentation/networking/devlink/idpf.rst     |  29 +++++
 Documentation/networking/devlink/index.rst    |   1 +
 drivers/net/ethernet/intel/idpf/Makefile      |   1 +
 .../net/ethernet/intel/idpf/idpf_devlink.c    |  79 ++++++++++++
 .../net/ethernet/intel/idpf/idpf_devlink.h    |  45 +++++++
 drivers/net/ethernet/intel/idpf/idpf_main.c   |  13 +-
 .../testing/selftests/drivers/net/hw/Makefile |   1 +
 .../selftests/drivers/net/hw/devlink_info.sh  | 119 ++++++++++++++++++
 8 files changed, 285 insertions(+), 3 deletions(-)
 create mode 100644 Documentation/networking/devlink/idpf.rst
 create mode 100644 drivers/net/ethernet/intel/idpf/idpf_devlink.c
 create mode 100644 drivers/net/ethernet/intel/idpf/idpf_devlink.h
 create mode 100755 tools/testing/selftests/drivers/net/hw/devlink_info.sh

-- 
2.52.0


             reply	other threads:[~2026-08-15  1:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 17:49 Paul Greenwalt [this message]
2026-08-14 17:49 ` [PATCH iwl-next 1/3] idpf: clear drvdata on probe error path Paul Greenwalt
2026-08-14 17:49 ` [PATCH iwl-next 2/3] idpf: add devlink info support Paul Greenwalt
2026-08-14 17:49 ` [PATCH iwl-next 3/3] selftests: net: hw: add devlink info test Paul Greenwalt

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=20260814174919.4177289-1-paul.greenwalt@intel.com \
    --to=paul.greenwalt@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    /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