[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97ae9fa0-0a6c-41d2-8a6c-1706b920d7ea@linaro.org>
Date: Tue, 7 Nov 2023 17:40:24 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Corentin Labbe <clabbe@...libre.com>, davem@...emloft.net,
heiko@...ech.de, herbert@...dor.apana.org.au,
krzysztof.kozlowski+dt@...aro.org, mturquette@...libre.com,
p.zabel@...gutronix.de, robh+dt@...nel.org, sboyd@...nel.org
Cc: ricardo@...dini.net, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH 1/6] dt-bindings: crypto: add support for
rockchip,crypto-rk3588
On 07/11/2023 16:55, Corentin Labbe wrote:
> Add device tree binding documentation for the Rockchip cryptographic
> offloader V2.
>
> Signed-off-by: Corentin Labbe <clabbe@...libre.com>
> ---
> .../crypto/rockchip,rk3588-crypto.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/crypto/rockchip,rk3588-crypto.yaml
>
> diff --git a/Documentation/devicetree/bindings/crypto/rockchip,rk3588-crypto.yaml b/Documentation/devicetree/bindings/crypto/rockchip,rk3588-crypto.yaml
> new file mode 100644
> index 000000000000..07024cf4fb0e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/crypto/rockchip,rk3588-crypto.yaml
> @@ -0,0 +1,65 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/crypto/rockchip,rk3588-crypto.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Rockchip cryptographic offloader V2
v2? Where is any documentation of this versioning? From where does it
come from?
> +
> +maintainers:
> + - Corentin Labbe <clabbe@...libre.com>
> +
> +properties:
> + compatible:
> + enum:
> + - rockchip,rk3568-crypto
> + - rockchip,rk3588-crypto
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + minItems: 3
You also must describe the items instead.
Where do you see any binding using minItems alone?
> +
> + clock-names:
> + items:
> + - const: core
> + - const: a
> + - const: h
> +
> + resets:
> + minItems: 1
No, maxItems.
> +
> + reset-names:
> + items:
> + - const: core
Drop reset-names, not really needed and not useful.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> + - resets
> + - reset-names
Best regards,
Krzysztof
Powered by blists - more mailing lists