From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-cxl@vger.kernel.org>, <linux-pci@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Ben Widawsky <ben.widawsky@intel.com>,
Chris Browy <cbrowy@avery-design.com>,
<linux-acpi@vger.kernel.org>, <alison.schofield@intel.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
<linuxarm@huawei.com>, Fangjian <f.fangjian@huawei.com>
Subject: Re: [RFC PATCH v2 1/4] PCI: Add vendor define ID for the PCI SIG
Date: Tue, 13 Apr 2021 19:21:35 +0100 [thread overview]
Message-ID: <20210413192135.000024de@Huawei.com> (raw)
In-Reply-To: <20210413163448.GA2240386@bjorn-Precision-5520>
On Tue, 13 Apr 2021 11:34:48 -0500
Bjorn Helgaas <helgaas@kernel.org> wrote:
> On Wed, Apr 14, 2021 at 12:01:56AM +0800, Jonathan Cameron wrote:
> > This ID is used in DOE headers to identify protocols that are
> > defined within the PCI Express Base Specification.
>
> Can you please include the specific spec citation here?
Will make sure to add to cover leter for next version but for now,
Table 7-x2: Data Object Exchange ECN
(first column lists the Vendor ID for the protocols)
Available on the PCI SIG spec downloads page.
It also exists in various other places in the 5.0 spec, but I'm
not sure if any are software visible (e.g. VDMs)
Jonathan
>
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > ---
> > Since V1: New Patch
> >
> > include/linux/pci_ids.h | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> > index a76ccb697bef..2c0459c23331 100644
> > --- a/include/linux/pci_ids.h
> > +++ b/include/linux/pci_ids.h
> > @@ -149,6 +149,7 @@
> > #define PCI_CLASS_OTHERS 0xff
> >
> > /* Vendors and devices. Sort key: vendor first, device next. */
> > +#define PCI_VENDOR_ID_PCI_SIG 0x0001
> >
> > #define PCI_VENDOR_ID_LOONGSON 0x0014
> >
> > --
> > 2.19.1
> >
next prev parent reply other threads:[~2021-04-13 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 16:01 [RFC PATCH v2 0/4] PCI Data Object Exchange support + CXL CDAT Jonathan Cameron
2021-04-13 16:01 ` [RFC PATCH v2 1/4] PCI: Add vendor define ID for the PCI SIG Jonathan Cameron
2021-04-13 16:34 ` Bjorn Helgaas
2021-04-13 18:21 ` Jonathan Cameron [this message]
2021-04-13 18:38 ` Bjorn Helgaas
2021-04-13 16:01 ` [RFC PATCH v2 2/4] PCI/doe: Initial support PCI Data Object Exchange Jonathan Cameron
2021-04-13 19:49 ` Bjorn Helgaas
2021-04-13 16:01 ` [RFC PATCH v2 3/4] cxl/mem: Add CDAT table reading from DOE Jonathan Cameron
2021-04-14 18:14 ` Konrad Rzeszutek Wilk
2021-04-14 18:50 ` Ben Widawsky
2021-04-13 16:01 ` [RFC PATCH v2 4/4] cxl/mem: Add a debug parser for CDAT commands Jonathan Cameron
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=20210413192135.000024de@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=cbrowy@avery-design.com \
--cc=dan.j.williams@intel.com \
--cc=f.fangjian@huawei.com \
--cc=helgaas@kernel.org \
--cc=ira.weiny@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=vishal.l.verma@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).