From: "tip-bot2 for Frank Li" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Frank Li <Frank.Li@nxp.com>, Thomas Gleixner <tglx@linutronix.de>,
"Rob Herring (Arm)" <robh@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: irq/msi] dt-bindings: PCI: pci-ep: Add support for iommu-map and msi-map
Date: Thu, 08 May 2025 17:27:10 -0000 [thread overview]
Message-ID: <174672523050.406.12783420937421276511.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20250414-ep-msi-v18-4-f69b49917464@nxp.com>
The following commit has been merged into the irq/msi branch of tip:
Commit-ID: a6aed6b9c79e57064fa8c028662214b436578e80
Gitweb: https://git.kernel.org/tip/a6aed6b9c79e57064fa8c028662214b436578e80
Author: Frank Li <Frank.Li@nxp.com>
AuthorDate: Mon, 14 Apr 2025 14:30:58 -04:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Wed, 07 May 2025 17:49:00 +02:00
dt-bindings: PCI: pci-ep: Add support for iommu-map and msi-map
Document the use of (msi|iommu)-map for PCI Endpoint (EP) controllers,
which can use MSI as a doorbell mechanism. Each EP controller can support
up to 8 physical functions and 65,536 virtual functions.
Define how to construct device IDs using function bits [2:0] and virtual
function index bits [31:3], enabling (msi|iommu)-map to associate each
child device with a specific (msi|iommu)-specifier.
The EP cannot rely on PCI Requester ID (RID) because the RID is determined
by the PCI topology of the host system. Since the EP may be connected to
different PCI hosts, the RID can vary between systems and is therefore not
a reliable identifier.
Signed-off-by: Frank Li <Frank.Li@nxp.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Link: https://lore.kernel.org/all/20250414-ep-msi-v18-4-f69b49917464@nxp.com
---
Documentation/devicetree/bindings/pci/pci-ep.yaml | 68 ++++++++++++++-
1 file changed, 68 insertions(+)
diff --git a/Documentation/devicetree/bindings/pci/pci-ep.yaml b/Documentation/devicetree/bindings/pci/pci-ep.yaml
index f75000e..214caa4 100644
--- a/Documentation/devicetree/bindings/pci/pci-ep.yaml
+++ b/Documentation/devicetree/bindings/pci/pci-ep.yaml
@@ -17,6 +17,24 @@ properties:
$nodename:
pattern: "^pcie-ep@"
+ iommu-map:
+ $ref: /schemas/types.yaml#/definitions/uint32-matrix
+ items:
+ items:
+ - description: Device ID (see msi-map) base
+ maximum: 0x7ffff
+ - description: phandle to IOMMU
+ - description: IOMMU specifier base (currently always 1 cell)
+ - description: Number of Device IDs
+ maximum: 0x80000
+
+ iommu-map-mask:
+ description:
+ A mask to be applied to each Device ID prior to being mapped to an
+ IOMMU specifier per the iommu-map property.
+ $ref: /schemas/types.yaml#/definitions/uint32
+ maximum: 0x7ffff
+
max-functions:
description: Maximum number of functions that can be configured
$ref: /schemas/types.yaml#/definitions/uint8
@@ -35,6 +53,56 @@ properties:
$ref: /schemas/types.yaml#/definitions/uint32
enum: [ 1, 2, 3, 4 ]
+ msi-map:
+ description: |
+ Maps a Device ID to an MSI and associated MSI specifier data.
+
+ A PCI Endpoint (EP) can use MSI as a doorbell function. This is achieved by
+ mapping the MSI controller's address into PCI BAR<n>. The PCI Root Complex
+ can write to this BAR<n>, triggering the EP to generate IRQ. This notifies
+ the EP-side driver of an event, eliminating the need for the driver to
+ continuously poll for status changes.
+
+ However, the EP cannot rely on Requester ID (RID) because the RID is
+ determined by the PCI topology of the host system. Since the EP may be
+ connected to different PCI hosts, the RID can vary between systems and is
+ therefore not a reliable identifier.
+
+ Each EP can support up to 8 physical functions and up to 65,536 virtual
+ functions. To uniquely identify each child device, a device ID is defined
+ as
+ - Bits [2:0] for the function number (func)
+ - Bits [18:3] for the virtual function index (vfunc)
+
+ The resulting device ID is computed as:
+
+ (func & 0x7) | (vfunc << 3)
+
+ The property is an arbitrary number of tuples of
+ (device-id-base, msi, msi-base,length).
+
+ Any Device ID id in the interval [id-base, id-base + length) is
+ associated with the listed MSI, with the MSI specifier
+ (id - id-base + msi-base).
+ $ref: /schemas/types.yaml#/definitions/uint32-matrix
+ items:
+ items:
+ - description: The Device ID base matched by the entry
+ maximum: 0x7ffff
+ - description: phandle to msi-controller node
+ - description: (optional) The msi-specifier produced for the first
+ Device ID matched by the entry. Currently, msi-specifier is 0 or
+ 1 cells.
+ - description: The length of consecutive Device IDs following the
+ Device ID base
+ maximum: 0x80000
+
+ msi-map-mask:
+ description: A mask to be applied to each Device ID prior to being
+ mapped to an msi-specifier per the msi-map property.
+ $ref: /schemas/types.yaml#/definitions/uint32
+ maximum: 0x7ffff
+
num-lanes:
description: maximum number of lanes
$ref: /schemas/types.yaml#/definitions/uint32
next prev parent reply other threads:[~2025-05-08 17:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 18:30 [PATCH v18 00/15] PCI: EP: Add RC-to-EP doorbell with platform MSI controller Frank Li
2025-04-14 18:30 ` [PATCH v18 01/15] platform-msi: Add msi_remove_device_irq_domain() in platform_device_msi_free_irqs_all() Frank Li
2025-05-08 17:27 ` [tip: irq/msi] " tip-bot2 for Frank Li
2025-04-14 18:30 ` [PATCH v18 02/15] irqdomain: Add IRQ_DOMAIN_FLAG_MSI_IMMUTABLE and irq_domain_is_msi_immutable() Frank Li
2025-05-08 17:27 ` [tip: irq/msi] " tip-bot2 for Frank Li
2025-04-14 18:30 ` [PATCH v18 03/15] irqchip/gic-v3-its: Set IRQ_DOMAIN_FLAG_MSI_IMMUTABLE for ITS Frank Li
2025-05-08 17:27 ` [tip: irq/msi] " tip-bot2 for Frank Li
2025-04-14 18:30 ` [PATCH v18 04/15] dt-bindings: PCI: pci-ep: Add support for iommu-map and msi-map Frank Li
2025-04-15 23:27 ` Rob Herring (Arm)
2025-05-08 17:27 ` tip-bot2 for Frank Li [this message]
2025-04-14 18:30 ` [PATCH v18 05/15] irqchip/gic-v3-its: Add support for device tree msi-map and msi-mask Frank Li
2025-05-08 17:27 ` [tip: irq/msi] " tip-bot2 for Frank Li
2025-04-14 18:31 ` [PATCH v18 06/15] PCI: endpoint: Set ID and of_node for function driver Frank Li
2025-04-14 18:31 ` [PATCH v18 07/15] PCI: endpoint: Add RC-to-EP doorbell support using platform MSI controller Frank Li
2025-04-14 18:31 ` [PATCH v18 08/15] PCI: endpoint: pci-ep-msi: Add MSI address/data pair mutable check Frank Li
2025-05-07 15:03 ` Thomas Gleixner
2025-04-14 18:31 ` [PATCH v18 09/15] PCI: endpoint: Add pci_epf_align_inbound_addr() helper for address alignment Frank Li
2025-04-14 18:31 ` [PATCH v18 10/15] PCI: endpoint: pci-epf-test: Add doorbell test support Frank Li
2025-04-14 18:31 ` [PATCH v18 11/15] misc: pci_endpoint_test: Add doorbell test case Frank Li
2025-04-14 18:31 ` [PATCH v18 12/15] selftests: pci_endpoint: " Frank Li
2025-04-14 18:31 ` [PATCH v18 13/15] pci: imx6: Add helper function imx_pcie_add_lut_by_rid() Frank Li
2025-04-14 18:31 ` [PATCH v18 14/15] pci: imx6: Add LUT setting for MSI/IOMMU in Endpoint mode Frank Li
2025-04-14 18:31 ` [PATCH v18 15/15] arm64: dts: imx95: Add msi-map for pci-ep device Frank Li
2025-05-02 1:10 ` [PATCH v18 00/15] PCI: EP: Add RC-to-EP doorbell with platform MSI controller Frank Li
2025-05-08 17:26 ` Thomas Gleixner
2025-05-11 8:24 ` Manivannan Sadhasivam
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=174672523050.406.12783420937421276511.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=Frank.Li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®