From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Sean V Kelley <sean.v.kelley@intel.com>
Cc: <bhelgaas@google.com>, <rjw@rjwysocki.net>,
<ashok.raj@kernel.org>, <tony.luck@intel.com>,
<sathyanarayanan.kuppuswamy@linux.intel.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Subject: Re: [RFC PATCH 1/9] pci_ids: Add class code and extended capability for RCEC
Date: Mon, 27 Jul 2020 11:21:21 +0100 [thread overview]
Message-ID: <20200727112121.00007653@Huawei.com> (raw)
In-Reply-To: <20200727110010.00005042@Huawei.com>
On Mon, 27 Jul 2020 11:00:10 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:
> On Fri, 24 Jul 2020 10:22:15 -0700
> Sean V Kelley <sean.v.kelley@intel.com> wrote:
>
> > From: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> >
> > A PCIe Root Complex Event Collector(RCEC) has the base class 0x08,
> > sub-class 0x07, and programming interface 0x00. Add the class code
> > 0x0807 to identify RCEC devices and add the defines for the RCEC
> > Endpoint Association Extended Capability.
> >
> > See PCI Express Base Specification, version 5.0-1, section "1.3.4
> > Root Complex Event Collector" and section "7.9.10 Root Complex
> > Event Collector Endpoint Association Extended Capability"
>
> Add a reference to the document
> "PCI Code and ID Assignment Specification"
> for the class number.
Actually probably no need. I'd somehow managed to fail to notice the
class code is also given in section 1.3.4 of the main spec.
>
> From the change log on latest version seems like it's been there since
> version 1.4.
>
> There is a worrying note (bottom of page 16 of 1.12 version of that docs)
> in there that says some older specs used 0x0806 for RCECs and that we
> should use the port type field to actually check if we have one.
>
> Hopefully we won't encounter any of those in the wild.
>
> Otherwise, it's exactly what the spec says.
> We could bike shed on naming choices, but the ones you have seem clear enough
> to me.
>
> FWIW
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
>
> Jonathan
> >
> > Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> > ---
> > include/linux/pci_ids.h | 1 +
> > include/uapi/linux/pci_regs.h | 7 +++++++
> > 2 files changed, 8 insertions(+)
> >
> > diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> > index 0ad57693f392..de8dff1fb176 100644
> > --- a/include/linux/pci_ids.h
> > +++ b/include/linux/pci_ids.h
> > @@ -81,6 +81,7 @@
> > #define PCI_CLASS_SYSTEM_RTC 0x0803
> > #define PCI_CLASS_SYSTEM_PCI_HOTPLUG 0x0804
> > #define PCI_CLASS_SYSTEM_SDHCI 0x0805
> > +#define PCI_CLASS_SYSTEM_RCEC 0x0807
> > #define PCI_CLASS_SYSTEM_OTHER 0x0880
> >
> > #define PCI_BASE_CLASS_INPUT 0x09
> > diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> > index f9701410d3b5..f335f65f65d6 100644
> > --- a/include/uapi/linux/pci_regs.h
> > +++ b/include/uapi/linux/pci_regs.h
> > @@ -828,6 +828,13 @@
> > #define PCI_PWR_CAP_BUDGET(x) ((x) & 1) /* Included in system budget */
> > #define PCI_EXT_CAP_PWR_SIZEOF 16
> >
> > +/* Root Complex Event Collector Endpoint Association */
> > +#define PCI_RCEC_RCIEP_BITMAP 4 /* Associated Bitmap for RCiEPs */
> > +#define PCI_RCEC_BUSN 8 /* RCEC Associated Bus Numbers */
> > +#define PCI_RCEC_BUSN_REG_VER 0x02 /* Least capability version that BUSN present */
> > +#define PCI_RCEC_BUSN_NEXT(x) (((x) >> 8) & 0xff)
> > +#define PCI_RCEC_BUSN_LAST(x) (((x) >> 16) & 0xff)
> > +
> > /* Vendor-Specific (VSEC, PCI_EXT_CAP_ID_VNDR) */
> > #define PCI_VNDR_HEADER 4 /* Vendor-Specific Header */
> > #define PCI_VNDR_HEADER_ID(x) ((x) & 0xffff)
>
next prev parent reply other threads:[~2020-07-27 10:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 17:22 [RFC PATCH 0/9] Add RCEC handling to PCI/AER Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 1/9] pci_ids: Add class code and extended capability for RCEC Sean V Kelley
2020-07-27 10:00 ` Jonathan Cameron
2020-07-27 10:21 ` Jonathan Cameron [this message]
2020-07-27 15:22 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 2/9] PCI: Extend Root Port Driver to support RCEC Sean V Kelley
2020-07-27 12:30 ` Jonathan Cameron
2020-07-27 15:05 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 3/9] PCI/portdrv: Add pcie_walk_rcec() to walk RCiEPs associated with RCEC Sean V Kelley
2020-07-27 10:49 ` Jonathan Cameron
2020-07-27 15:21 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 4/9] PCI/AER: Extend AER error handling to RCECs Sean V Kelley
2020-07-27 11:00 ` Jonathan Cameron
2020-07-27 14:58 ` Sean V Kelley
2020-07-27 14:04 ` Jonathan Cameron
2020-07-27 15:00 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 5/9] PCI/AER: Apply function level reset to RCiEP on fatal error Sean V Kelley
2020-07-27 11:17 ` Jonathan Cameron
2020-07-28 13:27 ` Zhuo, Qiuxu
2020-07-28 16:14 ` Sean V Kelley
2020-07-28 17:02 ` Jonathan Cameron
2020-07-28 17:42 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 6/9] PCI: Add 'rcec' field to pci_dev for associated RCiEPs Sean V Kelley
2020-07-27 11:23 ` Jonathan Cameron
2020-07-27 15:39 ` Sean V Kelley
2020-07-27 16:11 ` Jonathan Cameron
2020-07-27 16:28 ` Sean V Kelley
2020-07-24 17:22 ` [RFC PATCH 7/9] PCI/AER: Add RCEC AER handling Sean V Kelley
2020-07-27 12:22 ` Jonathan Cameron
2020-07-27 15:19 ` Sean V Kelley
2020-07-27 17:14 ` Jonathan Cameron
2020-07-24 17:22 ` [RFC PATCH 8/9] PCI/PME: Add RCEC PME handling Sean V Kelley
2020-08-04 8:35 ` Jay Fang
2020-08-04 9:47 ` Jonathan Cameron
2020-07-24 17:22 ` [RFC PATCH 9/9] PCI/AER: Add RCEC AER error injection support Sean V Kelley
2020-07-27 12:37 ` [RFC PATCH 0/9] Add RCEC handling to PCI/AER Jonathan Cameron
2020-07-27 14:56 ` 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=20200727112121.00007653@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=ashok.raj@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rjw@rjwysocki.net \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sean.v.kelley@intel.com \
--cc=tony.luck@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).