From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shresth Prasad <shresthprasad7@gmail.com>,
vkoul@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
javier.carrasco.cruz@gmail.com
Subject: Re: [PATCH] dt-bindings: dma: mv-xor-v2: Convert to dtschema
Date: Mon, 24 Jun 2024 07:17:16 +0200 [thread overview]
Message-ID: <62c05c34-0b69-4091-8c3a-d0b8befa9150@kernel.org> (raw)
In-Reply-To: <20240623124507.27297-2-shresthprasad7@gmail.com>
On 23/06/2024 14:45, Shresth Prasad wrote:
> Convert txt bindings of Marvell XOR v2 engines to dtschema to allow
> for validation.
>
> Signed-off-by: Shresth Prasad <shresthprasad7@gmail.com>
> ---
> Tested against `marvell/armada-7040-db.dtb`, `marvell/armada-7040-mochabin.dtb`
> and `marvell/armada-8080-db.dtb`
>
> .../bindings/dma/marvell,xor-v2.yaml | 69 +++++++++++++++++++
> .../devicetree/bindings/dma/mv-xor-v2.txt | 28 --------
> 2 files changed, 69 insertions(+), 28 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/dma/marvell,xor-v2.yaml
> delete mode 100644 Documentation/devicetree/bindings/dma/mv-xor-v2.txt
>
> diff --git a/Documentation/devicetree/bindings/dma/marvell,xor-v2.yaml b/Documentation/devicetree/bindings/dma/marvell,xor-v2.yaml
> new file mode 100644
> index 000000000000..3d7481c1917e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/marvell,xor-v2.yaml
> @@ -0,0 +1,69 @@
> +# SPDX-License-Identifier: GPL-2.0
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/dma/marvell,xor-v2.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Marvell XOR v2 engines
> +
> +maintainers:
> + - Vinod Koul <vkoul@kernel.org>
Should be rather platform maintainer.
> +
> +properties:
> + compatible:
> + contains:
This cannot be unspecific. Drop contains.
> + enum:
> + - marvell,armada-7k-xor
> + - marvell,xor-v2
> +
> + reg:
> + items:
> + - description: DMA registers location and length
> + - description: global registers location and length
Drop "location and length", redundant.
> +
> + clocks:
> + minItems: 1
> + maxItems: 2
> +
> + clock-names:
> + items:
> + - const: core
> + - const: reg
This does not match number of items in clocks:
> +
> + msi-parent:
> + description:
> + Phandle to the MSI-capable interrupt controller used for
> + interrupts.
> + maxItems: 1
> +
> + dma-coherent: true
This was not present in the binding and commit msg did not explain why
this is needed. Are devices really DMA coherent?
> +
> +required:
> + - compatible
> + - reg
> + - msi-parent
> + - dma-coherent
> +
> +if:
Put it under allOf: in this place.
> + required:
> + - clocks
This does not work and does not make much sense. Probably you want to
list the items per variant?
> + properties:
> + clocks:
> + minItems: 2
> + maxItems: 2
Instead list and describe the items.
> +then:
> + required:
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + xor0@6a0000 {
> + compatible = "marvell,armada-7k-xor", "marvell,xor-v2";
This totally does not match your binding.
Please, read example-schema, other bindings, my old talks and other
resources before doing conversions, so we can avoid such trivial
mistakes. You enumerated compatibles (enum), but here have a list. A
list is not an enumeration, obviously...
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-24 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 12:45 [PATCH] dt-bindings: dma: mv-xor-v2: Convert to dtschema Shresth Prasad
2024-06-24 5:17 ` Krzysztof Kozlowski [this message]
2024-06-24 10:14 ` Shresth Prasad
2024-06-24 11:08 ` Krzysztof Kozlowski
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=62c05c34-0b69-4091-8c3a-d0b8befa9150@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shresthprasad7@gmail.com \
--cc=skhan@linuxfoundation.org \
--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).