All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/2] fpga: dfl: optional VSEC for start of dfl
Date: Wed, 18 Nov 2020 11:01:49 -0800	[thread overview]
Message-ID: <20201118190151.365564-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 |  13 +++
 drivers/fpga/dfl-pci.c     | 163 +++++++++++++++++++++++++++++--------
 2 files changed, 141 insertions(+), 35 deletions(-)

-- 
2.25.2


             reply	other threads:[~2020-11-18 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 19:01 matthew.gerlach [this message]
2020-11-18 19:01 ` [PATCH v2 1/2] fpga: dfl: refactor cci_enumerate_feature_devs() matthew.gerlach
2020-11-18 19:01 ` [PATCH v2 2/2] fpga: dfl: look for vendor specific capability matthew.gerlach
2020-11-22  1:18   ` Moritz Fischer
2020-11-23 17:24     ` 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=20201118190151.365564-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.