From: Tianfei Zhang <tianfei.zhang@intel.com>
To: hao.wu@intel.com, trix@redhat.com, mdf@kernel.org,
yilun.xu@intel.com, linux-fpga@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: corbet@lwn.net, Tianfei Zhang <tianfei.zhang@intel.com>
Subject: [PATCH v5 0/6] Add OFS support for DFL driver
Date: Sun, 13 Mar 2022 06:52:36 -0400 [thread overview]
Message-ID: <20220313105242.1567774-1-tianfei.zhang@intel.com> (raw)
This is v5 patchset adding OFS (Open FPGA Stack) support for
DFL driver, based on v5.17-rc7. OFS is a collection of RTL
and open software providing interface to access the instantiated
RTL easily in FPGA. OFS leverages the DFL for the implementation
of the FPGA RTL design.
Patch 1, allows for ports without local bar space for "multiple VFs per
PR slot" model.
Patch 2, uses some lowest bits of flags to track the port status which
the AFU was connected to port device or not.
Patch 3, checks the number of released port match the number of
VFs or not in legacy model.
Patch 4, configures port access mode for afu connected with port.
Patch 5, handles dfl's starting with AFU.
Patch 6, adds architecture description about OFS support for DFL
in documentation.
Changelog v4 -> v5:
- fix documentation with Matthew and Randy's comment.
Changelog v3 -> v4:
- change "features" to "flags" in dfl_fpga_cdev to track the status
of port device.
- use dfl_fpga_cdev->flags to check if it need configure the port access
mode or not.
- add description about access the AFU on "multiple VFs per PR slot"
model.
Changelog v2 -> v3:
- no code change, just change the name from IOFS to OFS.
Changelog v1 -> v2:
- Introducing a new member "features" in dfl_fpga_cdev for feature
control.
- Adding new flag DFL_FEAT_PORT_CONNECTED_AFU for OFS legacy model.
- Updates the documentation for the access models about AFU in OFS.
- Drop the PCI PID patch and will send it later.
Matthew Gerlach (2):
fpga: dfl: Allow ports without local bar space.
fpga: dfl: support PF/VF starting with DFH
Tianfei zhang (4):
fpga: dfl: tracking port conntected with AFU
fpga: dfl: check released_port_num and num_vfs for legacy model
fpga: dfl: configure port access mode for afu connected with port
Documentation: fpga: dfl: add description of OFS
Documentation/fpga/dfl.rst | 114 +++++++++++++++++++++++++++++++++++++
drivers/fpga/dfl-pci.c | 9 +++
drivers/fpga/dfl.c | 62 ++++++++++++++------
drivers/fpga/dfl.h | 22 +++++++
4 files changed, 191 insertions(+), 16 deletions(-)
--
2.26.2
next reply other threads:[~2022-03-13 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 10:52 Tianfei Zhang [this message]
2022-03-13 10:52 ` [PATCH v5 1/6] fpga: dfl: Allow ports without local bar space Tianfei Zhang
2022-03-13 10:52 ` [PATCH v5 2/6] fpga: dfl: tracking port conntected with AFU Tianfei Zhang
2022-03-13 10:52 ` [PATCH v5 3/6] fpga: dfl: check released_port_num and num_vfs for legacy model Tianfei Zhang
2022-03-13 10:52 ` [PATCH v5 4/6] fpga: dfl: configure port access mode for afu connected with port Tianfei Zhang
2022-03-13 10:52 ` [PATCH v5 5/6] fpga: dfl: support PF/VF starting with DFH Tianfei Zhang
2022-03-13 10:52 ` [PATCH v5 6/6] Documentation: fpga: dfl: add description of OFS Tianfei Zhang
2022-03-13 16:32 ` Randy Dunlap
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=20220313105242.1567774-1-tianfei.zhang@intel.com \
--to=tianfei.zhang@intel.com \
--cc=corbet@lwn.net \
--cc=hao.wu@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@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;
as well as URLs for NNTP newsgroup(s).