From: Shannon Nelson <shannon.nelson@amd.com>
To: <jgg@nvidia.com>, <andrew.gospodarek@broadcom.com>,
<aron.silverton@oracle.com>, <dan.j.williams@intel.com>,
<daniel.vetter@ffwll.ch>, <dave.jiang@intel.com>,
<dsahern@kernel.org>, <gospo@broadcom.com>, <hch@infradead.org>,
<itayavr@nvidia.com>, <jiri@nvidia.com>,
<Jonathan.Cameron@huawei.com>, <kuba@kernel.org>,
<lbloch@nvidia.com>, <leonro@nvidia.com>, <saeedm@nvidia.com>,
<linux-cxl@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<netdev@vger.kernel.org>
Cc: <brett.creeley@amd.com>, Shannon Nelson <shannon.nelson@amd.com>
Subject: [RFC PATCH fwctl 0/5] pds_fwctl: fwctl for AMD/Pensando core devices
Date: Tue, 11 Feb 2025 15:48:49 -0800 [thread overview]
Message-ID: <20250211234854.52277-1-shannon.nelson@amd.com> (raw)
Following along from Jason's work [1] we have our initial RFC patchset
for pds_fwctl - an auxiliary_bus driver for supporting fwctl through the
pds_core driver and its PDS core device.
The PDS core is PCI device that is separate and distinct from the
ionic Eth device and from the other PCI devices that can be supported
by the AMD/Pensando DSC. It is used by pds_vdpa and pds_vfio_pci to
coordinate/communicate with the FW for setting up their services.
Until now the DSC's basic configurations for defining what devices to
support and for getting low-level device debug information have been
through internal commands not available from the host side, requiring
access into the DSC's own OS. Adding the fwctl service allows us to start
bringing these capabilities up into the host, but they don't replace the
existing function-specific tools. For example, these are things that make
the Eth PCI device appear on the PCI bus, while the tuning of the specific
Eth features still go through the standard ethtool/devlink/ip/etc tools.
The first two patches add a new pds_core.fwctl auxiliary_device to the
pds_core driver. This is only supported by the pds_core PF and not on
any VFs.
The remaining patches add the pds_fwctl driver framework and then fill
in the details for the fwctl services.
[1] https://lore.kernel.org/netdev/0-v4-0cf4ec3b8143+4995-fwctl_jgg@nvidia.com/
[PATCH v4 00/10] Introduce fwctl subystem
Brett Creeley (1):
pds_fwctl: add rpc and query support
Shannon Nelson (4):
pds_core: specify auxiliary_device to be created
pds_core: add new fwctl auxilary_device
pds_fwctl: initial driver framework
pds_fwctl: add Documentation entries
Documentation/userspace-api/fwctl/fwctl.rst | 1 +
Documentation/userspace-api/fwctl/index.rst | 1 +
.../userspace-api/fwctl/pds_fwctl.rst | 41 ++
MAINTAINERS | 7 +
drivers/fwctl/Kconfig | 10 +
drivers/fwctl/Makefile | 1 +
drivers/fwctl/pds/Makefile | 4 +
drivers/fwctl/pds/main.c | 558 ++++++++++++++++++
drivers/net/ethernet/amd/pds_core/auxbus.c | 44 +-
drivers/net/ethernet/amd/pds_core/core.c | 7 +
drivers/net/ethernet/amd/pds_core/core.h | 8 +-
drivers/net/ethernet/amd/pds_core/devlink.c | 6 +-
drivers/net/ethernet/amd/pds_core/main.c | 21 +-
include/linux/pds/pds_adminq.h | 264 +++++++++
include/linux/pds/pds_common.h | 2 +
include/uapi/fwctl/fwctl.h | 1 +
include/uapi/fwctl/pds.h | 43 ++
17 files changed, 988 insertions(+), 31 deletions(-)
create mode 100644 Documentation/userspace-api/fwctl/pds_fwctl.rst
create mode 100644 drivers/fwctl/pds/Makefile
create mode 100644 drivers/fwctl/pds/main.c
create mode 100644 include/uapi/fwctl/pds.h
--
2.17.1
next reply other threads:[~2025-02-11 23:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 23:48 Shannon Nelson [this message]
2025-02-11 23:48 ` [RFC PATCH fwctl 1/5] pds_core: specify auxiliary_device to be created Shannon Nelson
2025-02-12 11:57 ` Jonathan Cameron
2025-02-13 22:44 ` Nelson, Shannon
2025-02-11 23:48 ` [RFC PATCH fwctl 2/5] pds_core: add new fwctl auxilary_device Shannon Nelson
2025-02-12 12:02 ` Jonathan Cameron
2025-02-13 22:48 ` Nelson, Shannon
2025-02-12 12:03 ` Jonathan Cameron
2025-02-13 22:49 ` Nelson, Shannon
2025-02-18 19:28 ` Leon Romanovsky
2025-02-18 20:00 ` Nelson, Shannon
2025-02-19 8:24 ` Leon Romanovsky
2025-02-20 23:20 ` Nelson, Shannon
2025-02-22 18:26 ` Leon Romanovsky
2025-02-11 23:48 ` [RFC PATCH fwctl 3/5] pds_fwctl: initial driver framework Shannon Nelson
2025-02-12 12:22 ` Jonathan Cameron
2025-02-13 23:06 ` Nelson, Shannon
2025-02-14 0:55 ` Jason Gunthorpe
2025-02-12 23:26 ` Dave Jiang
2025-02-13 23:31 ` Nelson, Shannon
2025-02-18 19:51 ` Leon Romanovsky
2025-02-18 22:19 ` Nelson, Shannon
2025-02-19 8:25 ` Leon Romanovsky
2025-02-20 23:27 ` Nelson, Shannon
2025-02-22 18:29 ` Leon Romanovsky
2025-02-11 23:48 ` [RFC PATCH fwctl 4/5] pds_fwctl: add rpc and query support Shannon Nelson
2025-02-12 12:47 ` Jonathan Cameron
2025-02-13 23:13 ` Nelson, Shannon
2025-02-13 1:02 ` Dave Jiang
2025-02-13 23:34 ` Nelson, Shannon
2025-02-11 23:48 ` [RFC PATCH fwctl 5/5] pds_fwctl: add Documentation entries Shannon Nelson
2025-02-12 12:51 ` Jonathan Cameron
2025-02-12 13:13 ` Jason Gunthorpe
2025-02-12 14:23 ` Leon Romanovsky
2025-02-13 23:18 ` Nelson, Shannon
2025-02-12 13:40 ` [RFC PATCH fwctl 0/5] pds_fwctl: fwctl for AMD/Pensando core devices Andrew Lunn
2025-02-12 14:43 ` Jason Gunthorpe
2025-02-12 16:19 ` Andrew Lunn
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=20250211234854.52277-1-shannon.nelson@amd.com \
--to=shannon.nelson@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=aron.silverton@oracle.com \
--cc=brett.creeley@amd.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dave.jiang@intel.com \
--cc=dsahern@kernel.org \
--cc=gospo@broadcom.com \
--cc=hch@infradead.org \
--cc=itayavr@nvidia.com \
--cc=jgg@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=lbloch@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.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