From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: jassisinghbrar@gmail.com, robh+dt@kernel.org, shawnguo@kernel.org
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski@canonical.com, daniel.baluta@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V3 2/5] dt-bindings: mailbox: imx-mu: add i.MX93 S4 MU support
Date: Fri, 11 Feb 2022 14:02:58 +0800 [thread overview]
Message-ID: <20220211060301.1852772-3-peng.fan@oss.nxp.com> (raw)
In-Reply-To: <20220211060301.1852772-1-peng.fan@oss.nxp.com>
From: Peng Fan <peng.fan@nxp.com>
Similar to i.MX8ULP S4 MU, i.MX93 MU is dedicated for communication
between Sentinel and Cortex-A cores from hardware design, it could not be
reused for other purpose.
However i.MX93 S4 MU use separate tx/rx interrupt, so update
interrupts and add interrupt-names property.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
.../devicetree/bindings/mailbox/fsl,mu.yaml | 21 +++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/Documentation/devicetree/bindings/mailbox/fsl,mu.yaml b/Documentation/devicetree/bindings/mailbox/fsl,mu.yaml
index 6d056d5e16bf..f0a7e693ebf8 100644
--- a/Documentation/devicetree/bindings/mailbox/fsl,mu.yaml
+++ b/Documentation/devicetree/bindings/mailbox/fsl,mu.yaml
@@ -29,6 +29,7 @@ properties:
- const: fsl,imx8ulp-mu
- const: fsl,imx8-mu-scu
- const: fsl,imx8-mu-seco
+ - const: fsl,imx93-mu-s4
- const: fsl,imx8ulp-mu-s4
- items:
- const: fsl,imx93-mu
@@ -57,6 +58,12 @@ properties:
interrupts:
maxItems: 1
+ interrupt-names:
+ minItems: 1
+ items:
+ - const: txirq
+ - const: rxirq
+
"#mbox-cells":
description: |
<&phandle type channel>
@@ -90,6 +97,20 @@ required:
- interrupts
- "#mbox-cells"
+allOf:
+ - if:
+ properties:
+ compatible:
+ enum:
+ - fsl,imx93-mu-s4
+ then:
+ properties:
+ interrupt-names:
+ minItems: 2
+ maxItems: 2
+ interrupts:
+ maxItems: 2
+
additionalProperties: false
examples:
--
2.25.1
next prev parent reply other threads:[~2022-02-11 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 6:02 [PATCH V3 0/5] mailbox: imx: support i.MX93 Peng Fan (OSS)
2022-02-11 6:02 ` [PATCH V3 1/5] dt-bindings: mailbox: imx-mu: add i.MX93 MU Peng Fan (OSS)
2022-02-17 23:21 ` Rob Herring
2022-02-11 6:02 ` Peng Fan (OSS) [this message]
2022-02-17 23:23 ` [PATCH V3 2/5] dt-bindings: mailbox: imx-mu: add i.MX93 S4 MU support Rob Herring
2022-02-11 6:02 ` [PATCH V3 3/5] mailbox: imx: extend irq to an array Peng Fan (OSS)
2022-02-11 6:03 ` [PATCH V3 4/5] mailbox: imx: support dual interrupts Peng Fan (OSS)
2022-02-11 6:03 ` [PATCH V3 5/5] mailbox: imx: support i.MX93 S401 MU Peng Fan (OSS)
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=20220211060301.1852772-3-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).