[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250823154009.25992-9-jszhang@kernel.org>
Date: Sat, 23 Aug 2025 23:40:03 +0800
From: Jisheng Zhang <jszhang@...nel.org>
To: Vinod Koul <vkoul@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Robin Murphy <robin.murphy@....com>
Cc: dmaengine@...r.kernel.org,
devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 08/14] dt-bindings: dma: dma350: Document interrupt-names
Currently, the dma350 driver assumes all channels are available to
linux, this may not be true on some platforms, so it's possible no
irq(s) for the unavailable channel(s). What's more, the available
channels may not be continuous. To handle this case, we'd better
get the irq of each channel by name.
Signed-off-by: Jisheng Zhang <jszhang@...nel.org>
---
Documentation/devicetree/bindings/dma/arm,dma-350.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
index 429f682f15d8..94752516e51a 100644
--- a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
+++ b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
@@ -32,6 +32,10 @@ properties:
- description: Channel 6 interrupt
- description: Channel 7 interrupt
+ interrupt-names:
+ minItems: 1
+ maxItems: 8
+
"#dma-cells":
const: 1
description: The cell is the trigger input number
@@ -40,5 +44,6 @@ required:
- compatible
- reg
- interrupts
+ - interrupt-names
unevaluatedProperties: false
--
2.50.0
Powered by blists - more mailing lists