devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Guo Mengqi <guomengqi3@huawei.com>,
	vkoul@kernel.org, dmaengine@vger.kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Cc: xuqiang36@huawei.com
Subject: Re: [PATCH 2/2] dt-bindings: dma: hisi: Add bindings for Hisi Ascend sdma
Date: Mon, 14 Aug 2023 10:51:28 +0200	[thread overview]
Message-ID: <2a4751d4-2955-b4d7-f16b-7a3a90fbab3a@linaro.org> (raw)
In-Reply-To: <20230811034822.107229-3-guomengqi3@huawei.com>

On 11/08/2023 05:48, Guo Mengqi wrote:
> Add device-tree binding documentation for the Hisi Ascend sdma
> controller.
> 
> Signed-off-by: Guo Mengqi <guomengqi3@huawei.com>
> ---
>  .../bindings/dma/hisi,ascend-sdma.yaml        | 82 +++++++++++++++++++
>  1 file changed, 82 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/dma/hisi,ascend-sdma.yaml
> 
> diff --git a/Documentation/devicetree/bindings/dma/hisi,ascend-sdma.yaml b/Documentation/devicetree/bindings/dma/hisi,ascend-sdma.yaml
> new file mode 100644
> index 000000000000..beb2b3597f4d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/hisi,ascend-sdma.yaml
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/dma/hisi,ascend-sdma.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: HISI Ascend System DMA (SDMA) controller
> +
> +description: |
> +  The Ascend SDMA controller is used for transferring data

What is Ascend? SoC? Family? Model?

> +  in system memory. It utilizes IOMMU SVA feature and accepts
> +  virtual address from user process.
> +
> +maintainers:
> +  - Guo Mengqi <guomengqi3@huawei.com>
> +
> +allOf:
> +  - $ref: dma-controller.yaml#
> +
> +properties:
> +  compatible:
> +    const: hisilicon,sdma

Way too generic compatible. It must be *model specific*.

> +
> +  reg:
> +    maxItems: 1
> +
> +  '#dma-cells':
> +    const: 1
> +    description:
> +      Clients specify a single cell with channel number.
> +
> +  ascend_sdma_channel_map:

Missing vendor prefix, no underscores in property names, missing type/$ref.


I doubt this was ever tested.

> +    description: |
> +      bitmap, each bit stands for a channel that is allowed to
> +      use by this system. Maximum 32 bits.
> +    maximum: 0xffffffff
> +
> +  ascend_sdma_channel_iomem_size:
> +    description: |
> +      depends on different platforms to be released. There are

Ah, so compatible is not specific enough? No, please make compatibles
specific and drop this property.

> +      currently two possible values. A default value is used if
> +      the property is not set.
> +      - enum:
> +        - 0x400
> +        - 0x1000
> +
> +  iommus:
> +    maxItems: 1
> +
> +  pasid-num-bits:
> +    description: |
> +      sdma utilizes iommu sva feature to transfer user space data.
> +      It act as a basic dma controller if not bound to user space.
> +    const: 0x10
> +
> +  dma-coherent: true
> +
> +  dma-can-stall: true
> +
> +required:
> +  - compatible
> +  - reg
> +  - ascend_sdma_channel_map
> +  - '#dma-cells'
> +  - iommus
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    sdma: dma-controller@880E0000 {

Use lowercase hex and drop unused label.

> +      compatible = "hisilicon,sdma";
> +        reg = <0x880e0000 0x10000>;

Broken indentation.




Best regards,
Krzysztof


      reply	other threads:[~2023-08-14  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  3:48 [PATCH 0/2] Add sdma driver for HiSilicon Ascend platform Guo Mengqi
2023-08-11  3:48 ` [PATCH 1/2] dmaengine: Add HiSilicon Ascend SDMA engine support Guo Mengqi
2023-08-11  9:50   ` kernel test robot
2023-08-11 11:55   ` kernel test robot
2023-08-14  8:54   ` Krzysztof Kozlowski
2023-08-18 10:20     ` guomengqi (A)
2023-08-11  3:48 ` [PATCH 2/2] dt-bindings: dma: hisi: Add bindings for Hisi Ascend sdma Guo Mengqi
2023-08-14  8:51   ` Krzysztof Kozlowski [this message]

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=2a4751d4-2955-b4d7-f16b-7a3a90fbab3a@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=guomengqi3@huawei.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=xuqiang36@huawei.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;
as well as URLs for NNTP newsgroup(s).