From: Sean V Kelley <sean.v.kelley@linux.intel.com>
To: mj@ucw.cz, bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, Sean V Kelley <sean.v.kelley@linux.intel.com>
Subject: [Patch 0/1] pciutils: Add available DVSEC Details
Date: Thu, 9 Apr 2020 11:32:03 -0700 [thread overview]
Message-ID: <20200409183204.328057-1-sean.v.kelley@linux.intel.com> (raw)
Add separate Designated Vendor Specific Capability (DVSEC) defines
and cap function so as to align with PCIe r5.0, sec 7.9.6.2 terms and
provide available details. First step in later adding support for CXL.
Sean V Kelley (1):
lspci: Add available DVSEC details
lib/header.h | 4 +
ls-ecaps.c | 25 +++-
tests/cap-dvsec | 340 ++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 368 insertions(+), 1 deletion(-)
create mode 100644 tests/cap-dvsec
--
2.26.0
next reply other threads:[~2020-04-09 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 18:32 Sean V Kelley [this message]
2020-04-09 18:32 ` [Patch 1/1] lspci: Add available DVSEC details Sean V Kelley
2020-04-09 19:56 ` Bjorn Helgaas
2020-04-09 21:13 ` Sean V Kelley
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=20200409183204.328057-1-sean.v.kelley@linux.intel.com \
--to=sean.v.kelley@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
/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).