From: Moritz Fischer <mdf@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-fpga@vger.kernel.org, trix@redhat.com, hao.wu@intel.com,
yilun.xu@intel.com, russell.h.weight@intel.com,
Moritz Fischer <mdf@kernel.org>
Subject: [PATCH 0/8] FPGA DFL Changes for 5.11
Date: Thu, 10 Dec 2020 08:57:56 -0800 [thread overview]
Message-ID: <20201210165804.44234-1-mdf@kernel.org> (raw)
Hi Greg,
here are some (late) changes for DFL for 5.11.
Matthew's set adds support for locating DFL lists using a vendor
specific extended capability (similar to MSIX bar indicators).
Xu's set now hopefully addressed the outstanding comments to support
DFL as a bus. The first user is the dfl-emif driver that was ack'd by
Krzysztof already (he suggested to take it through DFL tree).
Thanks,
Moritz
Matthew Gerlach (2):
fpga: dfl: refactor cci_enumerate_feature_devs()
fpga: dfl-pci: locate DFLs by PCIe vendor specific capability
Xu Yilun (6):
fpga: dfl: fix the definitions of type & feature_id for dfl devices
fpga: dfl: move dfl_device_id to mod_devicetable.h
fpga: dfl: add dfl bus support to MODULE_DEVICE_TABLE()
fpga: dfl: move dfl bus related APIs to include/linux/dfl.h
fpga: dfl: add support for N3000 Nios private feature
memory: dfl-emif: add the DFL EMIF private feature driver
.../ABI/testing/sysfs-bus-dfl-devices-emif | 25 +
.../testing/sysfs-bus-dfl-devices-n3000-nios | 47 ++
Documentation/fpga/dfl.rst | 27 +
MAINTAINERS | 3 +-
drivers/fpga/Kconfig | 11 +
drivers/fpga/Makefile | 2 +
drivers/fpga/dfl-n3000-nios.c | 588 ++++++++++++++++++
drivers/fpga/dfl-pci.c | 165 +++--
drivers/fpga/dfl.c | 4 +-
drivers/fpga/dfl.h | 85 +--
drivers/memory/Kconfig | 9 +
drivers/memory/Makefile | 2 +
drivers/memory/dfl-emif.c | 207 ++++++
include/linux/dfl.h | 86 +++
include/linux/mod_devicetable.h | 24 +
scripts/mod/devicetable-offsets.c | 4 +
scripts/mod/file2alias.c | 13 +
17 files changed, 1180 insertions(+), 122 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl-devices-emif
create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl-devices-n3000-nios
create mode 100644 drivers/fpga/dfl-n3000-nios.c
create mode 100644 drivers/memory/dfl-emif.c
create mode 100644 include/linux/dfl.h
--
2.29.2
next reply other threads:[~2020-12-10 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 16:57 Moritz Fischer [this message]
2020-12-10 16:57 ` [PATCH 1/8] fpga: dfl: refactor cci_enumerate_feature_devs() Moritz Fischer
2020-12-10 16:57 ` [PATCH 2/8] fpga: dfl-pci: locate DFLs by PCIe vendor specific capability Moritz Fischer
2020-12-10 16:57 ` [PATCH 3/8] fpga: dfl: fix the definitions of type & feature_id for dfl devices Moritz Fischer
2020-12-10 16:58 ` [PATCH 4/8] fpga: dfl: move dfl_device_id to mod_devicetable.h Moritz Fischer
2020-12-10 16:58 ` [PATCH 5/8] fpga: dfl: add dfl bus support to MODULE_DEVICE_TABLE() Moritz Fischer
2020-12-14 13:43 ` Tom Rix
2020-12-15 1:39 ` Xu Yilun
2020-12-10 16:58 ` [PATCH 6/8] fpga: dfl: move dfl bus related APIs to include/linux/dfl.h Moritz Fischer
2020-12-10 16:58 ` [PATCH 7/8] fpga: dfl: add support for N3000 Nios private feature Moritz Fischer
2020-12-10 16:58 ` [PATCH 8/8] memory: dfl-emif: add the DFL EMIF private feature driver Moritz Fischer
2020-12-14 14:05 ` [PATCH 0/8] FPGA DFL Changes for 5.11 Greg KH
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=20201210165804.44234-1-mdf@kernel.org \
--to=mdf@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=russell.h.weight@intel.com \
--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).