Devicetree
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Wei Xu <xuwei5@hisilicon.com>,
	dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: dma: Convert hisilicon,k3-dma-1.0 to DT schema
Date: Wed, 30 Sep 2026 15:30:50 -0400	[thread overview]
Message-ID: <ar1jarw-WgVlq2_G@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260928124448.3754740-1-robh@kernel.org>

On Mon, Sep 28, 2026 at 07:44:46AM -0500, Rob Herring (Arm) wrote:
> Convert the hisilicon,k3-dma-1.0 binding to DT schema format.
>
> Add dma-channel-mask, dma-no-cci, dma-type and interrupt-names
> properties which were not documented.
>
> The "hisilicon,hisi-pcm-asp-dma-1.0" doesn't have clocks, so make it
> optional.
>
> Assisted-by: LLM
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> v2:
>  - Fix example node name to 'dma-controller'
> ---
>  .../bindings/dma/hisilicon,k3-dma-1.0.yaml    | 87 +++++++++++++++++++
>  .../devicetree/bindings/dma/k3dma.txt         | 47 ----------
>  2 files changed, 87 insertions(+), 47 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/dma/hisilicon,k3-dma-1.0.yaml
>  delete mode 100644 Documentation/devicetree/bindings/dma/k3dma.txt
>
> diff --git a/Documentation/devicetree/bindings/dma/hisilicon,k3-dma-1.0.yaml b/Documentation/devicetree/bindings/dma/hisilicon,k3-dma-1.0.yaml
> new file mode 100644
> index 000000000000..e60f2a572272
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/hisilicon,k3-dma-1.0.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/dma/hisilicon,k3-dma-1.0.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Hisilicon K3 DMA controller
> +
> +maintainers:
> +  - Wei Xu <xuwei5@hisilicon.com>
> +
> +properties:
> +  compatible:
> +    items:
> +      - enum:
> +          - hisilicon,k3-dma-1.0
> +          - hisilicon,hisi-pcm-asp-dma-1.0
> +
> +  reg:
> +    maxItems: 1
> +
> +  clocks:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +
> +  '#dma-cells':
> +    const: 1
> +
> +  dma-channels:
> +    description: Number of physical DMA channels supported.
> +    maximum: 32
> +
> +  dma-requests:
> +    description: Number of virtual DMA request lines supported.
> +    maximum: 32
> +
> +  dma-channel-mask:
> +    description: Bitmask of usable DMA channels.
> +
> +  dma-no-cci:
> +    type: boolean
> +    description: DMA is not coherent with the CCI.
> +
> +  dma-type:
> +    $ref: /schemas/types.yaml#/definitions/string
> +    description: SoC-specific DMA type name.
> +    enum:
> +      - hi3660_dma
> +      - hi6220_dma
> +
> +  interrupt-names:
> +    maxItems: 1

It'd better move interrupt-names after interrupts property.

> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - '#dma-cells'
> +  - dma-channels
> +  - dma-requests
> +
> +allOf:
> +  - $ref: dma-controller.yaml#
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            const: hisilicon,k3-dma-1.0
> +    then:
> +      required:
> +        - clocks
> +
> +additionalProperties: false

there are $ref, should be unevaluatedProperties?

Frank

> +
> +examples:
> +  - |
> +    dma-controller@fcd02000 {
> +        compatible = "hisilicon,k3-dma-1.0";
> +        reg = <0xfcd02000 0x1000>;
> +        #dma-cells = <1>;
> +        dma-channels = <16>;
> +        dma-requests = <27>;
> +        interrupts = <0 12 4>;
> +        clocks = <&pclk>;
> +    };
> diff --git a/Documentation/devicetree/bindings/dma/k3dma.txt b/Documentation/devicetree/bindings/dma/k3dma.txt
> deleted file mode 100644
> index 10a2f15b08a3..000000000000
> --- a/Documentation/devicetree/bindings/dma/k3dma.txt
> +++ /dev/null
> @@ -1,47 +0,0 @@
> -* Hisilicon K3 DMA controller
> -
> -See dma.txt first
> -
> -Required properties:
> -- compatible: Must be one of
> --              "hisilicon,k3-dma-1.0"
> --              "hisilicon,hisi-pcm-asp-dma-1.0"
> -- reg: Should contain DMA registers location and length.
> -- interrupts: Should contain one interrupt shared by all channel
> -- #dma-cells: see dma.txt, should be 1, para number
> -- dma-channels: physical channels supported
> -- dma-requests: virtual channels supported, each virtual channel
> -		have specific request line
> -- clocks: clock required
> -
> -Example:
> -
> -Controller:
> -		dma0: dma@fcd02000 {
> -			compatible = "hisilicon,k3-dma-1.0";
> -			reg = <0xfcd02000 0x1000>;
> -			#dma-cells = <1>;
> -			dma-channels = <16>;
> -			dma-requests = <27>;
> -			interrupts = <0 12 4>;
> -			clocks = <&pclk>;
> -		};
> -
> -Client:
> -Use specific request line passing from dmax
> -For example, i2c0 read channel request line is 18, while write channel use 19
> -
> -		i2c0: i2c@fcb08000 {
> -			compatible = "snps,designware-i2c";
> -			dmas =	<&dma0 18          /* read channel */
> -				 &dma0 19>;        /* write channel */
> -			dma-names = "rx", "tx";
> -		};
> -
> -		i2c1: i2c@fcb09000 {
> -			compatible = "snps,designware-i2c";
> -			dmas =	<&dma0 20          /* read channel */
> -				 &dma0 21>;        /* write channel */
> -			dma-names = "rx", "tx";
> -		};
> -
> --
> 2.53.0
>

  parent reply	other threads:[~2026-09-30 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 12:44 [PATCH v2] dt-bindings: dma: Convert hisilicon,k3-dma-1.0 to DT schema Rob Herring (Arm)
2026-09-30  7:22 ` Wei Xu
2026-09-30 19:30 ` Frank Li [this message]
2026-10-02 14:34   ` Rob Herring
2026-10-05 15:43 ` Vinod Koul

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=ar1jarw-WgVlq2_G@lizhi-Precision-Tower-5810 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@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=vkoul@kernel.org \
    --cc=xuwei5@hisilicon.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