From: matthew.gerlach@linux.intel.com
To: linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
mdf@kernel.org, hao.wu@intel.com, trix@redhat.com,
linux-doc@vger.kernel.org, corbet@lwn.net
Cc: Matthew Gerlach <matthew.gerlach@linux.intel.com>
Subject: [PATCH v3 0/2] fpga: dfl: optional VSEC for start of dfl
Date: Tue, 24 Nov 2020 07:56:56 -0800 [thread overview]
Message-ID: <20201124155658.700976-1-matthew.gerlach@linux.intel.com> (raw)
From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
The start of a Device Feature List (DFL) is currently assumed to be at
Bar0/Offset 0 on the PCIe bus by drivers/fpga/dfl-pci.c. This patchset
adds support for the start one or more DFLs to be specified in a
Vendor-Specific Capability (VSEC) structure in PCIe config space. If no
such VSEC structure exists, then the start is assumed to be
Bar0/Offset 0 for backward compatibility.
Matthew Gerlach (2):
fpga: dfl: refactor cci_enumerate_feature_devs()
fpga: dfl: look for vendor specific capability
Documentation/fpga/dfl.rst | 25 ++++++
drivers/fpga/dfl-pci.c | 169 +++++++++++++++++++++++++++++--------
2 files changed, 159 insertions(+), 35 deletions(-)
--
2.25.2
next reply other threads:[~2020-11-24 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 15:56 matthew.gerlach [this message]
2020-11-24 15:56 ` [PATCH v3 1/2] fpga: dfl: refactor cci_enumerate_feature_devs() matthew.gerlach
[not found] ` <DM6PR11MB3819B8E32400D0662CFAD20685F70@DM6PR11MB3819.namprd11.prod.outlook.com>
2020-11-30 23:48 ` matthew.gerlach
2020-11-24 15:56 ` [PATCH v3 2/2] fpga: dfl: look for vendor specific capability matthew.gerlach
[not found] ` <DM6PR11MB38191D8C5E27E6E04B8DAA1A85F70@DM6PR11MB3819.namprd11.prod.outlook.com>
2020-12-01 0:45 ` matthew.gerlach
2020-12-01 18:56 ` Moritz Fischer
2020-12-02 2:00 ` Xu Yilun
2020-12-02 9:40 ` Wu, Hao
2020-12-02 19:17 ` matthew.gerlach
2020-12-02 9:56 ` Wu, Hao
2020-12-02 19:06 ` matthew.gerlach
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=20201124155658.700976-1-matthew.gerlach@linux.intel.com \
--to=matthew.gerlach@linux.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 \
/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).