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: Re: [PATCH v6 0/2] pciutils: Add basic decode support for CXL DVSEC
Date: Mon, 04 May 2020 09:20:21 -0700 [thread overview]
Message-ID: <47C51040-497A-4D1F-97F1-B6C87830F7C9@linux.intel.com> (raw)
In-Reply-To: <20200420221444.2641935-1-sean.v.kelley@linux.intel.com>
On 20 Apr 2020, at 15:14, Sean V Kelley wrote:
> Changes since v5 [1]:
>
> - There can be multiple vendor specific DVSEC IDs associated with CXL.
> (Bjorn Helgaas)
>
> [1]
> https://lore.kernel.org/linux-pci/20200415004751.2103963-1-sean.v.kelley@linux.intel.com/
>
> This patch series adds support for basic lspci decode of Compute
> eXpress Link[2],
> a new CPU interconnect building upon PCIe. As a foundation for the CXL
> support it adds separate Designated Vendor-Specific Capability (DVSEC)
> defines
> and a cap function so as to align with PCIe r5.0, sec 7.9.6.2 terms
> and
> provide available details. It makes use of the DVSEC Vendor ID and
> DVSEC ID so as
> to identify a CXL capable device.
>
> [2] https://www.computeexpresslink.org/
Just a light ping on these patches.
Thanks!
Sean
>
> Sean V Kelley (2):
> pciutils: Decode available DVSEC details
> pciutils: Decode Compute eXpress Link DVSEC
>
> lib/header.h | 24 ++++
> ls-ecaps.c | 79 +++++++++-
> tests/cap-dvsec | 340
> ++++++++++++++++++++++++++++++++++++++++++++
> tests/cap-dvsec-cxl | 340
> ++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 782 insertions(+), 1 deletion(-)
> create mode 100644 tests/cap-dvsec
> create mode 100644 tests/cap-dvsec-cxl
>
> --
> 2.26.0
prev parent reply other threads:[~2020-05-04 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 22:14 [PATCH v6 0/2] pciutils: Add basic decode support for CXL DVSEC Sean V Kelley
2020-04-20 22:14 ` [PATCH v6 1/2] pciutils: Decode available DVSEC details Sean V Kelley
2020-04-20 22:14 ` [PATCH v6 2/2] pciutils: Decode Compute eXpress Link DVSEC Sean V Kelley
2020-05-04 16:20 ` Sean V Kelley [this message]
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=47C51040-497A-4D1F-97F1-B6C87830F7C9@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).