The ARM MHUv2 Receiver block can indeed support more interrupts, up to the
maximum number of available channels, but anyway no more than the maximum
number of supported interrupt for an AMBA device.
Signed-off-by: Cristian Marussi <cristian.marussi@xxxxxxx>
---
Cc: Rob Herring <robh+dt@xxxxxxxxxx>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@xxxxxxxxxx>
Cc: devicetree@xxxxxxxxxxxxxxx
.../devicetree/bindings/mailbox/arm,mhuv2.yaml | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml b/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml
index a4f1fe63659a..5a57f4e2a623 100644
--- a/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml
+++ b/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml
@@ -69,10 +69,15 @@ properties:
interrupts:
description: |
- The MHUv2 controller always implements an interrupt in the "receiver"
- mode, while the interrupt in the "sender" mode was not available in the
- version MHUv2.0, but the later versions do have it.
- maxItems: 1
+ The MHUv2 controller always implements at least an interrupt in the
+ "receiver" mode, while the interrupt in the "sender" mode was not
+ available in the version MHUv2.0, but the later versions do have it.
+ In "receiver" mode, beside a single combined interrupt, there could be
+ multiple interrupts, up to the number of implemented channels but anyway
+ no more than the maximum number of interrupts potentially supported by
+ AMBA.
+ minItems: 1
+ maxItems: 9
clocks:
maxItems: 1
--
2.34.1
