From: Mark Kettenis <kettenis@openbsd.org>
To: devicetree@vger.kernel.org
Cc: maz@kernel.org, robin.murphy@arm.com, sven@svenpeter.dev,
alyssa@rosenzweig.io, Mark Kettenis <kettenis@openbsd.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Hector Martin <marcan@marcan.st>,
Bjorn Helgaas <bhelgaas@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Jim Quinlan <jim2101024@gmail.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Saenz Julienne <nsaenzjulienne@suse.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: [PATCH v5 2/4] dt-bindings: interrupt-controller: msi: Add msi-ranges property
Date: Tue, 21 Sep 2021 20:34:13 +0200 [thread overview]
Message-ID: <20210921183420.436-3-kettenis@openbsd.org> (raw)
In-Reply-To: <20210921183420.436-1-kettenis@openbsd.org>
Update the MSI controller binding to add an msi-ranges property
that specifies how MSIs map onto regular interrupts on some other
interrupt controller.
Acked-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Mark Kettenis <kettenis@openbsd.org>
---
.../bindings/interrupt-controller/msi-controller.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml b/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml
index 58d898d5b943..449d6067ec88 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/msi-controller.yaml
@@ -32,6 +32,14 @@ properties:
Identifies the node as an MSI controller.
$ref: /schemas/types.yaml#/definitions/flag
+ msi-ranges:
+ description:
+ A list of <phandle intspec span> tuples, where "phandle" is the
+ parent interrupt controller, "intspec" is the starting/base
+ interrupt specifier and "span" is the size of the
+ range. Multiple ranges can be provided.
+ $ref: /schemas/types.yaml#/definitions/phandle-array
+
dependencies:
"#msi-cells": [ msi-controller ]
--
2.33.0
next prev parent reply other threads:[~2021-09-21 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 18:34 [PATCH v5 0/4] Apple M1 PCIe DT bindings Mark Kettenis
2021-09-21 18:34 ` [PATCH v5 1/4] dt-bindings: interrupt-controller: Convert MSI controller to json-schema Mark Kettenis
2021-09-27 16:54 ` Rob Herring
2021-09-21 18:34 ` Mark Kettenis [this message]
2021-09-27 16:55 ` [PATCH v5 2/4] dt-bindings: interrupt-controller: msi: Add msi-ranges property Rob Herring
2021-09-21 18:34 ` [PATCH v5 3/4] dt-bindings: pci: Add DT bindings for apple,pcie Mark Kettenis
2021-09-27 17:03 ` Rob Herring
2021-09-21 18:34 ` [PATCH v5 4/4] arm64: apple: Add PCIe node Mark Kettenis
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=20210921183420.436-3-kettenis@openbsd.org \
--to=kettenis@openbsd.org \
--cc=alyssa@rosenzweig.io \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jim2101024@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=marcan@marcan.st \
--cc=maz@kernel.org \
--cc=nsaenz@kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sven@svenpeter.dev \
--cc=tglx@linutronix.de \
/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).