From: Alvaro Karsz <alvaro.karsz@solid-run.com>
To: virtualization@lists.linux-foundation.org
Cc: linux-pci@vger.kernel.org, Alvaro Karsz <alvaro.karsz@solid-run.com>
Subject: [PATCH 0/3] virtio: vdpa: new SolidNET DPU driver
Date: Mon, 12 Dec 2022 16:24:51 +0200 [thread overview]
Message-ID: <20221212142454.3225177-1-alvaro.karsz@solid-run.com> (raw)
This series adds a vDPA driver for SolidNET DPU.
Patch 1 adds SolidRun vendor id to pci_ids.
Patch 2 adds a pci quirk needed by the DPU.
Patch 3 has the driver source code.
Patch 1 is prerequisite for both patch 2 and patch 3.
Alvaro Karsz (3):
Add SolidRun vendor id
New PCI quirk for SolidRun SNET DPU.
virtio: vdpa: new SolidNET DPU driver.
MAINTAINERS | 4 +
drivers/pci/quirks.c | 8 +
drivers/vdpa/Kconfig | 11 +
drivers/vdpa/Makefile | 1 +
drivers/vdpa/solidrun/Makefile | 3 +
drivers/vdpa/solidrun/snet_hwmon.c | 191 +++++
drivers/vdpa/solidrun/snet_main.c | 1114 ++++++++++++++++++++++++++++
drivers/vdpa/solidrun/snet_vdpa.h | 192 +++++
include/linux/pci_ids.h | 2 +
9 files changed, 1526 insertions(+)
create mode 100644 drivers/vdpa/solidrun/Makefile
create mode 100644 drivers/vdpa/solidrun/snet_hwmon.c
create mode 100644 drivers/vdpa/solidrun/snet_main.c
create mode 100644 drivers/vdpa/solidrun/snet_vdpa.h
--
2.32.0
next reply other threads:[~2022-12-12 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 14:24 Alvaro Karsz [this message]
2022-12-12 14:24 ` [PATCH 1/3] Add SolidRun vendor id Alvaro Karsz
2022-12-12 14:24 ` [PATCH 2/3] New PCI quirk for SolidRun SNET DPU Alvaro Karsz
2022-12-12 14:24 ` [PATCH 3/3 v4] virtio: vdpa: new SolidNET DPU driver Alvaro Karsz
2022-12-12 15:01 ` Guenter Roeck
2022-12-12 16:29 ` Alvaro Karsz
2022-12-12 16:38 ` Alvaro Karsz
2022-12-12 17:01 ` Guenter Roeck
2022-12-12 17:46 ` Alvaro Karsz
2022-12-12 17:56 ` Alvaro Karsz
2022-12-12 19:05 ` Guenter Roeck
2022-12-12 20:17 ` Alvaro Karsz
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=20221212142454.3225177-1-alvaro.karsz@solid-run.com \
--to=alvaro.karsz@solid-run.com \
--cc=linux-pci@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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