From: CL Wang <cl634@andestech.com>
To: Conor Dooley <conor@kernel.org>
Cc: <vkoul@kernel.org>, <dmaengine@vger.kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tim609@andestech.com>, <cl634@andestech.com>
Subject: Re: [PATCH V1 1/2] dt-bindings: dmaengine: Add support for ATCDMAC300 DMA engine
Date: Tue, 7 Oct 2025 20:33:01 +0800 [thread overview]
Message-ID: <aOUIfaZY7-eUYoOS@swlinux02> (raw)
In-Reply-To: <20251002-absolute-spinning-f899e75b2c4a@spud>
Hi Conor,
Thanks for your review.
Yes, the DMA driver supports the Qilai platform. I have updated the DTS binding as shown below.
Could you please take a look and let me know if anything still needs to be adjusted?
properties:
compatible:
- const: andestech,atcdmac300
+ oneOf:
+ - items:
+ - enum:
+ - andestech,qilai-dma
+ - const: andestech,atcdmac300
+ - const: andestech,atcdmac300
...
dma-controller@f0c00000 {
- compatible = "andestech,atcdmac300";
+ compatible = "andestech,qilai-dma", "andestech,atcdmac300";
Thank you again for your feedback.
Best regards,
CL
On Thu, Oct 02, 2025 at 07:40:35PM +0100, Conor Dooley wrote:
> [EXTERNAL MAIL]
> Date: Thu, 2 Oct 2025 19:40:35 +0100
> From: Conor Dooley <conor@kernel.org>
> To: CL Wang <cl634@andestech.com>
> Cc: vkoul@kernel.org, dmaengine@vger.kernel.org, robh@kernel.org,
> krzk+dt@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
> linux-kernel@vger.kernel.org, tim609@andestech.com
> Subject: Re: [PATCH V1 1/2] dt-bindings: dmaengine: Add support for
> ATCDMAC300 DMA engine
>
> On Thu, Oct 02, 2025 at 09:16:58PM +0800, CL Wang wrote:
> > Document devicetree bindings for Andes ATCDMAC300 DMA engine
> >
> > Signed-off-by: CL Wang <cl634@andestech.com>
> > ---
> > .../bindings/dma/andestech,atcdmac300.yaml | 51 +++++++++++++++++++
> > MAINTAINERS | 6 +++
> > 2 files changed, 57 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/dma/andestech,atcdmac300.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/dma/andestech,atcdmac300.yaml b/Documentation/devicetree/bindings/dma/andestech,atcdmac300.yaml
> > new file mode 100644
> > index 000000000000..769694616517
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/dma/andestech,atcdmac300.yaml
> > @@ -0,0 +1,51 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/dma/andestech,atcdmac300.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Andes ATCDMAC300 DMA Controller
> > +
> > +maintainers:
> > + - CL Wang <cl634@andestech.com>
> > +
> > +allOf:
> > + - $ref: dma-controller.yaml#
> > +
> > +properties:
> > + compatible:
> > + const: andestech,atcdmac300
>
> "atcdmac300" sounds like the name of an IP block. What platforms are
> actually using this? They should have platform-specific compatibles, for
> example, "andestech,qilai-dma" if that's the platform where this is
> supported.
>
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > + "#dma-cells":
> > + const: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
> > + - "#dma-cells"
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > +
> > + soc {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > +
> > + dma-controller@f0c00000 {
> > + compatible = "andestech,atcdmac300";
> > + reg = <0x0 0xf0c00000 0x0 0x1000>;
> > + interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
> > + #dma-cells = <1>;
> > + };
> > + };
> > +...
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index fe168477caa4..dd3272cdadd6 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1778,6 +1778,12 @@ S: Supported
> > F: drivers/clk/analogbits/*
> > F: include/linux/clk/analogbits*
> >
> > +ANDES DMA DRIVER
> > +M: CL Wang <cl634@andestech.com>
> > +S: Supported
> > +F: Documentation/devicetree/bindings/dma/andestech,atcdmac300.yaml
> > +F: drivers/dma/atcdmac300*
> > +
> > ANDROID DRIVERS
> > M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > M: Arve Hjønnevåg <arve@android.com>
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2025-10-07 12:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 13:16 [PATCH V1 0/2] dmaengine: atcdmac300: Add Andes ATCDMAC300 DMA driver CL Wang
2025-10-02 13:16 ` [PATCH V1 1/2] dt-bindings: dmaengine: Add support for ATCDMAC300 DMA engine CL Wang
2025-10-02 18:40 ` Conor Dooley
2025-10-07 12:33 ` CL Wang [this message]
2025-10-07 14:27 ` Krzysztof Kozlowski
2025-10-08 3:13 ` CL Wang
2025-10-08 8:04 ` Krzysztof Kozlowski
2025-10-08 13:35 ` CL Wang
2025-10-08 20:45 ` Conor Dooley
2025-10-08 23:48 ` Krzysztof Kozlowski
2025-10-09 8:40 ` CL Wang
2025-10-02 13:16 ` [PATCH V1 2/2] dmaengine: atcdmac300: Add driver for Andes ATCDMAC300 DMA controller CL Wang
2025-10-03 17:36 ` kernel test robot
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=aOUIfaZY7-eUYoOS@swlinux02 \
--to=cl634@andestech.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tim609@andestech.com \
--cc=vkoul@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).