From: Robin Murphy <robin.murphy@arm.com>
To: Jun Guo <jun.guo@cixtech.com>,
peter.chen@cixtech.com, fugang.duan@cixtech.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
ychuang3@nuvoton.com, schung@nuvoton.com
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
linux-arm-kernel@lists.infradead.org, jelly.jia@cixtech.com
Subject: Re: [PATCH v2 1/3] dt-bindings: dma: arm-dma350: update DT binding docs for cix sky1 SoC
Date: Tue, 16 Dec 2025 12:43:07 +0000 [thread overview]
Message-ID: <9d4c274f-3e4c-49a1-9b2a-a95e9a48a4a6@arm.com> (raw)
In-Reply-To: <20251216123026.3519923-2-jun.guo@cixtech.com>
On 2025-12-16 12:30 pm, Jun Guo wrote:
> Add SoC-specific compatible strings to the DT binding documents to support
> cix sky1 SoC.
>
> When adding support for a new SoC that uses the arm dma controller,
> future contributors should be encouraged to actually add SoC-specific
> compatible strings. The use of the "arm,dma-350" compatible string in
> isolation should be disallowed.
No, you've missed the point - however many channels the hardware
implements, the DT should list that many interrupt specifiers; it
doesn't matter whether any of them happen to be the same.
Thanks,
Robin.
> Signed-off-by: Jun Guo <jun.guo@cixtech.com>
> ---
> .../devicetree/bindings/dma/arm,dma-350.yaml | 31 +++++++++++++------
> 1 file changed, 21 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
> index 429f682f15d8..78bcc7f9aa8b 100644
> --- a/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
> +++ b/Documentation/devicetree/bindings/dma/arm,dma-350.yaml
> @@ -14,7 +14,11 @@ allOf:
>
> properties:
> compatible:
> - const: arm,dma-350
> + oneOf:
> + - items:
> + - enum:
> + - cix,sky1-dma-350
> + - const: arm,dma-350
>
> reg:
> items:
> @@ -22,15 +26,22 @@ properties:
>
> interrupts:
> minItems: 1
> - items:
> - - description: Channel 0 interrupt
> - - description: Channel 1 interrupt
> - - description: Channel 2 interrupt
> - - description: Channel 3 interrupt
> - - description: Channel 4 interrupt
> - - description: Channel 5 interrupt
> - - description: Channel 6 interrupt
> - - description: Channel 7 interrupt
> + maxItems: 8
> + description: |
> + The DMA controller may be configured with separate interrupts for each channel,
> + or with a single combined interrupt for all channels, depending on the SoC integration.
> + oneOf:
> + - items:
> + - description: Channel 0 interrupt
> + - description: Channel 1 interrupt
> + - description: Channel 2 interrupt
> + - description: Channel 3 interrupt
> + - description: Channel 4 interrupt
> + - description: Channel 5 interrupt
> + - description: Channel 6 interrupt
> + - description: Channel 7 interrupt
> + - items:
> + - description: Combined interrupt shared by all channels
>
> "#dma-cells":
> const: 1
next prev parent reply other threads:[~2025-12-16 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 12:30 [PATCH v2 0/3] dmaengine: arm-dma350: add support for shared interrupt mode Jun Guo
2025-12-16 12:30 ` [PATCH v2 1/3] dt-bindings: dma: arm-dma350: update DT binding docs for cix sky1 SoC Jun Guo
2025-12-16 12:43 ` Robin Murphy [this message]
2026-01-13 2:05 ` Jun Guo
2025-12-16 12:30 ` [PATCH v2 2/3] dma: arm-dma350: add support for shared interrupt mode Jun Guo
2025-12-16 12:51 ` Robin Murphy
2025-12-17 2:12 ` Jun Guo
2026-01-13 1:56 ` Jun Guo
2025-12-16 12:30 ` [PATCH v2 3/3] arm64: dts: cix: add DT nodes for DMA Jun Guo
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=9d4c274f-3e4c-49a1-9b2a-a95e9a48a4a6@arm.com \
--to=robin.murphy@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--cc=jelly.jia@cixtech.com \
--cc=jun.guo@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@cixtech.com \
--cc=robh@kernel.org \
--cc=schung@nuvoton.com \
--cc=vkoul@kernel.org \
--cc=ychuang3@nuvoton.com \
/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®