From: Dave Jiang <dave.jiang@intel.com>
To: penn <engguopeng@buaa.edu.cn>, linux-cxl@vger.kernel.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
bhelgaas@google.com, dave@stgolabs.net, jic23@kernel.org,
alison.schofield@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, djbw@kernel.org, johnny.li@montage-tech.com,
peng.guo@montage-tech.com, jingzhong.yang@montage-tech.com
Subject: Re: [PATCH v2 1/2] PCI: Add MMIO Capabilities Register Block definitions
Date: Tue, 18 Aug 2026 15:37:34 -0700 [thread overview]
Message-ID: <2ba00f98-c950-45b4-aed7-202fa8811863@intel.com> (raw)
In-Reply-To: <20260817075854.17207-2-engguopeng@buaa.edu.cn>
On 8/17/26 12:58 AM, penn wrote:
> From: Penn <engguopeng@buaa.edu.cn>
>
> PCIe r7.0 sec 6.35 defines the MMIO Capabilities Register Block
> (MCAP). It consists of an array header followed by capability headers
> that identify the version, location, size, and vendor of each MMIO
> capability.
>
> Define the MCAP array-header and capability-header registers and their
> fields. These definitions allow subsystem drivers to use the Vendor ID
> along with the Capability ID when capabilities from multiple vendors
> share the same MCAP.
>
> Signed-off-by: Penn <engguopeng@buaa.edu.cn>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Changes in v2:
> - Update the MCAP specification citation to PCIe r7.0 sec 6.35.
> - Document that capability header indices are one-based.
>
> include/uapi/linux/pci_regs.h | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> index 14f634ab9350..4dd22cde9e71 100644
> --- a/include/uapi/linux/pci_regs.h
> +++ b/include/uapi/linux/pci_regs.h
> @@ -1338,6 +1338,28 @@
> #define PCI_IDE_SEL_ADDR_3(x) (28 + (x) * PCI_IDE_SEL_ADDR_BLOCK_SIZE)
> #define PCI_IDE_SEL_BLOCK_SIZE(nr_assoc) (20 + PCI_IDE_SEL_ADDR_BLOCK_SIZE * (nr_assoc))
>
> +/* PCIe r7.0, sec 6.35: MMIO Capabilities Register Block (MCAP) */
> +#define PCI_MCAP_ARRAY_1 0x00
> +#define PCI_MCAP_ARRAY_ID __GENMASK(15, 0)
> +#define PCI_MCAP_ARRAY_VERSION __GENMASK(23, 16)
> +#define PCI_MCAP_ARRAY_TYPE __GENMASK(27, 24)
> +#define PCI_MCAP_ARRAY_TYPE_CLASS_CODE 0x0
> +#define PCI_MCAP_ARRAY_2 0x04
> +#define PCI_MCAP_ARRAY_COUNT __GENMASK(15, 0)
> +
> +/* Capability header indices are one-based. */
> +#define PCI_MCAP_HDR_SIZEOF 0x10
> +#define PCI_MCAP_HDR_BASE(n) ((n) * PCI_MCAP_HDR_SIZEOF)
> +#define PCI_MCAP_HDR_REG_1 0x00
> +#define PCI_MCAP_CAP_ID __GENMASK(15, 0)
> +#define PCI_MCAP_CAP_VERSION __GENMASK(23, 16)
> +#define PCI_MCAP_HDR_REG_2 0x04
> +#define PCI_MCAP_HDR_OFFSET __GENMASK(31, 0)
> +#define PCI_MCAP_HDR_REG_3 0x08
> +#define PCI_MCAP_HDR_LENGTH __GENMASK(31, 0)
> +#define PCI_MCAP_HDR_REG_4 0x0c
> +#define PCI_MCAP_HDR_VENDOR_ID __GENMASK(15, 0)
> +
> /*
> * Compute Express Link (CXL r4.0, sec 8.1)
> *
next prev parent reply other threads:[~2026-08-18 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 7:58 [PATCH v2 0/2] PCI/CXL: Distinguish CXL capabilities in MCAP penn
2026-08-17 7:58 ` [PATCH v2 1/2] PCI: Add MMIO Capabilities Register Block definitions penn
2026-08-18 22:37 ` Dave Jiang [this message]
2026-08-17 7:58 ` [PATCH v2 2/2] cxl/core: Skip non-CXL capabilities in MCAP penn
2026-08-18 22:43 ` Dave Jiang
2026-08-19 1:28 ` engguopeng
2026-08-19 15:09 ` Dave Jiang
2026-08-20 2:36 ` engguopeng
2026-08-21 18:01 ` 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=2ba00f98-c950-45b4-aed7-202fa8811863@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=bhelgaas@google.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=engguopeng@buaa.edu.cn \
--cc=ira.weiny@intel.com \
--cc=jic23@kernel.org \
--cc=jingzhong.yang@montage-tech.com \
--cc=johnny.li@montage-tech.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=peng.guo@montage-tech.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
all inboxes | Powered by JetHome®