From: "irqchip-bot for Frank Li" <tip-bot2@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Marc Zyngier <maz@kernel.org>,
tglx@linutronix.de
Subject: [irqchip: irq/irqchip-next] dt-bindings: irqchip: Describe the IMX MU block as a MSI controller
Date: Wed, 28 Sep 2022 13:37:13 -0000 [thread overview]
Message-ID: <166437223395.401.8077585689879090034.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220922161246.20586-5-Frank.Li@nxp.com>
The following commit has been merged into the irq/irqchip-next branch of irqchip:
Commit-ID: 27c0141e094e45e875ccc1f299458db6433c1e55
Gitweb: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms/27c0141e094e45e875ccc1f299458db6433c1e55
Author: Frank Li <Frank.Li@nxp.com>
AuthorDate: Thu, 22 Sep 2022 11:12:44 -05:00
Committer: Marc Zyngier <maz@kernel.org>
CommitterDate: Wed, 28 Sep 2022 14:24:32 +01:00
dt-bindings: irqchip: Describe the IMX MU block as a MSI controller
I.MX MU supports generating IRQs by writing to a register.
Describe its use as a MSI controller so that other blocks (such as a PCI EP)
can use it directly.
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Frank Li <Frank.Li@nxp.com>
[maz: commit message]
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220922161246.20586-5-Frank.Li@nxp.com
---
Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml | 99 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 99 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml
diff --git a/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml b/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml
new file mode 100644
index 0000000..799ae5c
--- /dev/null
+++ b/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml
@@ -0,0 +1,99 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/interrupt-controller/fsl,mu-msi.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Freescale/NXP i.MX Messaging Unit (MU) work as msi controller
+
+maintainers:
+ - Frank Li <Frank.Li@nxp.com>
+
+description: |
+ The Messaging Unit module enables two processors within the SoC to
+ communicate and coordinate by passing messages (e.g. data, status
+ and control) through the MU interface. The MU also provides the ability
+ for one processor (A side) to signal the other processor (B side) using
+ interrupts.
+
+ Because the MU manages the messaging between processors, the MU uses
+ different clocks (from each side of the different peripheral buses).
+ Therefore, the MU must synchronize the accesses from one side to the
+ other. The MU accomplishes synchronization using two sets of matching
+ registers (Processor A-side, Processor B-side).
+
+ MU can work as msi interrupt controller to do doorbell
+
+allOf:
+ - $ref: /schemas/interrupt-controller/msi-controller.yaml#
+
+properties:
+ compatible:
+ enum:
+ - fsl,imx6sx-mu-msi
+ - fsl,imx7ulp-mu-msi
+ - fsl,imx8ulp-mu-msi
+ - fsl,imx8ulp-mu-msi-s4
+
+ reg:
+ items:
+ - description: a side register base address
+ - description: b side register base address
+
+ reg-names:
+ items:
+ - const: processor-a-side
+ - const: processor-b-side
+
+ interrupts:
+ description: a side interrupt number.
+ maxItems: 1
+
+ clocks:
+ maxItems: 1
+
+ power-domains:
+ items:
+ - description: a side power domain
+ - description: b side power domain
+
+ power-domain-names:
+ items:
+ - const: processor-a-side
+ - const: processor-b-side
+
+ interrupt-controller: true
+
+ msi-controller: true
+
+ "#msi-cells":
+ const: 0
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - interrupt-controller
+ - msi-controller
+ - "#msi-cells"
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/arm-gic.h>
+ #include <dt-bindings/firmware/imx/rsrc.h>
+
+ msi-controller@5d270000 {
+ compatible = "fsl,imx6sx-mu-msi";
+ msi-controller;
+ #msi-cells = <0>;
+ interrupt-controller;
+ reg = <0x5d270000 0x10000>, /* A side */
+ <0x5d300000 0x10000>; /* B side */
+ reg-names = "processor-a-side", "processor-b-side";
+ interrupts = <GIC_SPI 191 IRQ_TYPE_LEVEL_HIGH>;
+ power-domains = <&pd IMX_SC_R_MU_12A>,
+ <&pd IMX_SC_R_MU_12B>;
+ power-domain-names = "processor-a-side", "processor-b-side";
+ };
next prev parent reply other threads:[~2022-09-28 13:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 16:12 [PATCH v11 0/6] PCI EP driver support MSI doorbell from host Frank Li
2022-09-22 16:12 ` [PATCH v12 1/6] platform-msi: export symbol platform_msi_create_irq_domain() Frank Li
2022-09-28 13:37 ` [irqchip: irq/irqchip-next] platform-msi: Export " irqchip-bot for Frank Li
2022-09-22 16:12 ` [PATCH v12 2/6] irqchip: allow pass down .pm field at IRQCHIP_PLATFORM_DRIVER_END Frank Li
2022-09-28 13:37 ` [irqchip: irq/irqchip-next] irqchip: Allow extra fields to be passed to IRQCHIP_PLATFORM_DRIVER_END irqchip-bot for Frank Li
2022-09-22 16:12 ` [PATCH v12 3/6] irqchip: Add IMX MU MSI controller driver Frank Li
2022-09-28 13:37 ` [irqchip: irq/irqchip-next] " irqchip-bot for Frank Li
2022-09-29 16:26 ` irqchip-bot for Frank Li
2022-09-22 16:12 ` [PATCH v12 4/6] dt-bindings: irqchip: imx mu work as msi controller Frank Li
2022-09-28 13:37 ` irqchip-bot for Frank Li [this message]
2022-09-29 16:26 ` [irqchip: irq/irqchip-next] dt-bindings: irqchip: Describe the IMX MU block as a MSI controller irqchip-bot for Frank Li
2022-09-22 16:12 ` [PATCH v12 5/6] PCI: endpoint: pci-epf-vntb: Clean up Frank Li
2022-10-06 14:25 ` Frank Li
2022-10-07 8:43 ` Lorenzo Pieralisi
2022-09-22 16:12 ` [PATCH v12 6/6] PCI: endpoint: Add vNTB MSI support Frank Li
2022-10-07 9:15 ` Lorenzo Pieralisi
2022-10-07 14:54 ` [EXT] " Frank Li
2022-09-28 13:33 ` [PATCH v11 0/6] PCI EP driver support MSI doorbell from host Marc Zyngier
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=166437223395.401.8077585689879090034.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=Frank.Li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®