From: "tip-bot2 for Anirudha Sarangi" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Anirudha Sarangi <anirudha.sarangi@amd.com>,
Tushar Nimkar <tushar.nimkar@amd.com>,
Thomas Gleixner <tglx@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: irq/drivers] dt-bindings: interrupt-controller: Add Xilinx Versal NET SMMU CSR
Date: Thu, 15 Oct 2026 10:00:33 -0000 [thread overview]
Message-ID: <179205843332.2666988.11635736954701951306.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20260928-smmu-changes-v2-v4-1-3c79a14cd806@amd.com>
The following commit has been merged into the irq/drivers branch of tip:
Commit-ID: 675b45ab71f3b17482dde264d6ee7f98690c487c
Gitweb: https://git.kernel.org/tip/675b45ab71f3b17482dde264d6ee7f98690c487c
Author: Anirudha Sarangi <anirudha.sarangi@amd.com>
AuthorDate: Mon, 28 Sep 2026 15:03:03 +05:30
Committer: Thomas Gleixner <tglx@kernel.org>
CommitterDate: Thu, 15 Oct 2026 11:59:22 +02:00
dt-bindings: interrupt-controller: Add Xilinx Versal NET SMMU CSR
Add a device tree binding schema for the Xilinx Versal NET SMMU CSR
(Control and Status Register) interrupt controller.
The SMMU CSR block acts as a vendor-specific interrupt controller
in front of the ARM SMMUv3, providing registers to enable and clear
standard SMMU interrupts such as EVENTQ, CMDQ_SYNC, GERROR and PRIQ.
Interrupts must be acknowledged in this block before being forwarded
to the parent interrupt controller (e.g. GIC).
Co-developed-by: Tushar Nimkar <tushar.nimkar@amd.com>
Signed-off-by: Anirudha Sarangi <anirudha.sarangi@amd.com>
Signed-off-by: Tushar Nimkar <tushar.nimkar@amd.com>
Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://patch.msgid.link/20260928-smmu-changes-v2-v4-1-3c79a14cd806@amd.com
---
Documentation/devicetree/bindings/interrupt-controller/xlnx,versal-net-smmu-csr.yaml | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 75 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/xlnx,versal-net-smmu-csr.yaml
diff --git a/Documentation/devicetree/bindings/interrupt-controller/xlnx,versal-net-smmu-csr.yaml b/Documentation/devicetree/bindings/interrupt-controller/xlnx,versal-net-smmu-csr.yaml
new file mode 100644
index 0000000..38b63e5
--- /dev/null
+++ b/Documentation/devicetree/bindings/interrupt-controller/xlnx,versal-net-smmu-csr.yaml
@@ -0,0 +1,75 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/interrupt-controller/xlnx,versal-net-smmu-csr.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Xilinx Versal NET SMMU CSR Interrupt Controller
+
+maintainers:
+ - Anirudha Sarangi <anirudha.sarangi@amd.com>
+ - Tushar Nimkar <tushar.nimkar@amd.com>
+
+description: |
+ The Versal NET platform includes a Xilinx-specific SMMU CSR (Control and
+ Status Register) block that acts as an intermediate interrupt controller
+ for ARM SMMUv3.
+
+ The block provides registers to enable, disable and clear the
+ standard SMMUv3 interrupt sources (EVENTQ, CMDQ_SYNC, GERROR and PRIQ)
+ before forwarding them to the parent interrupt controller,
+ typically a GIC.
+
+ The controller receives one parent interrupt and demultiplexes CSR
+ status bits into the following child interrupt identifiers
+ 0 - EVENTQ
+ 1 - CMDQ_SYNC
+ 2 - GERROR (GLOBAL)
+ 3 - PRIQ
+
+allOf:
+ - $ref: /schemas/interrupt-controller.yaml#
+
+properties:
+ compatible:
+ const: xlnx,versal-net-smmu-csr
+
+ reg:
+ maxItems: 1
+
+ interrupt-controller: true
+
+ "#interrupt-cells":
+ const: 1
+ description: |
+ Single cell containing the child interrupt identifier
+ 0 - EVENTQ
+ 1 - CMDQ_SYNC
+ 2 - GERROR (GLOBAL)
+ 3 - PRIQ
+
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - interrupt-controller
+ - "#interrupt-cells"
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/arm-gic.h>
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ interrupt-controller@eca10000 {
+ compatible = "xlnx,versal-net-smmu-csr";
+ reg = <0xeca10000 0x1000>;
+ interrupt-controller;
+ #interrupt-cells = <1>;
+ interrupt-parent = <&gic>;
+ interrupts = <GIC_SPI 169 IRQ_TYPE_LEVEL_HIGH>;
+ };
next prev parent reply other threads:[~2026-10-15 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 9:33 [PATCH v4 0/2] Add Xilinx Versal NET SMMU CSR interrupt controller support Tushar Nimkar
2026-09-28 9:33 ` [PATCH v4 1/2] dt-bindings: interrupt-controller: Add Xilinx Versal NET SMMU CSR Tushar Nimkar
2026-10-15 10:00 ` tip-bot2 for Anirudha Sarangi [this message]
2026-09-28 9:33 ` [PATCH v4 2/2] irqchip: Add Xilinx Versal NET SMMU CSR interrupt controller driver Tushar Nimkar
2026-10-15 10:00 ` [tip: irq/drivers] " tip-bot2 for Anirudha Sarangi
-- strict thread matches above, loose matches on Subject: below --
2026-09-23 7:16 [PATCH v3 1/2] dt-bindings: interrupt-controller: Add Xilinx Versal NET SMMU CSR Tushar Nimkar
2026-10-15 9:54 ` [tip: irq/drivers] " tip-bot2 for Anirudha Sarangi
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=179205843332.2666988.11635736954701951306.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=anirudha.sarangi@amd.com \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=tushar.nimkar@amd.com \
--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®