From: Rob Herring <robh@kernel.org>
To: Jassi Brar <jassisinghbrar@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Jassi Brar <jaswinder.singh@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH] dt-bindings: mailbox: arm,mhu: Make secure interrupt optional
Date: Thu, 28 Jul 2022 13:08:10 -0600 [thread overview]
Message-ID: <20220728190810.1290857-1-robh@kernel.org> (raw)
The secure interrupt is only useful to secure world, therefore for NS
users it shouldn't be required. Make it optional.
This fixes a warning on Arm Juno board:
mhu@2b1f0000: interrupts: [[0, 36, 4], [0, 35, 4]] is too short
Signed-off-by: Rob Herring <robh@kernel.org>
---
Documentation/devicetree/bindings/mailbox/arm,mhu.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/mailbox/arm,mhu.yaml b/Documentation/devicetree/bindings/mailbox/arm,mhu.yaml
index bd49c201477d..d9a4f4a02d7c 100644
--- a/Documentation/devicetree/bindings/mailbox/arm,mhu.yaml
+++ b/Documentation/devicetree/bindings/mailbox/arm,mhu.yaml
@@ -57,6 +57,7 @@ properties:
maxItems: 1
interrupts:
+ minItems: 2
items:
- description: low-priority non-secure
- description: high-priority non-secure
--
2.34.1
next reply other threads:[~2022-07-28 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 19:08 Rob Herring [this message]
2022-07-28 20:17 ` [PATCH] dt-bindings: mailbox: arm,mhu: Make secure interrupt optional Jassi Brar
2022-07-28 21:07 ` Jassi Brar
2022-07-29 11:10 ` Sudeep Holla
2022-07-29 15:18 ` Jassi Brar
2022-08-01 10:23 ` Sudeep Holla
2022-08-01 13:57 ` Jassi Brar
2022-08-01 14:18 ` Sudeep Holla
2022-07-29 23:17 ` Rob Herring
2022-08-01 10:28 ` Sudeep Holla
2022-07-29 8:48 ` Sudeep Holla
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=20220728190810.1290857-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=jaswinder.singh@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.