Linux-Amlogic Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexey Romanov <avromanov@salutedevices.com>,
	neil.armstrong@linaro.org, clabbe@baylibre.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, khilman@baylibre.com, jbrunet@baylibre.com,
	martin.blumenstingl@googlemail.com
Cc: linux-crypto@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kernel@salutedevices.com
Subject: Re: [PATCH v3 16/20] dt-bindings: crypto: meson: support new SoC's
Date: Thu, 8 Feb 2024 09:38:36 +0100	[thread overview]
Message-ID: <b2e4ac25-5b07-46c7-a96f-8390a95584ea@linaro.org> (raw)
In-Reply-To: <20240205155521.1795552-17-avromanov@salutedevices.com>

On 05/02/2024 16:55, Alexey Romanov wrote:
> Now crypto module available at G12A/G12B/S4/A1/SM1/AXG.
> 
> 1. Add new compatibles:
>   - amlogic,g12a-crypto
>   - amlogic,s4-crypto (uses g12a-crypto as fallback)
>   - amlogic,a1-crypto (uses g12a-crypto as fallback)
>   - amlogic,axg-crypto
> 
> 2. All SoC's, exclude GXL, doesn't take a clock input for
> Crypto IP. Make it required only for amlogic,gxl-crypto.
> 
> 3. All SoC's, exclude GXL, uses only one interrupt flow
> for Crypto IP.
> 
> 4. Add power-domains in schema.
> 
> Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
> ---
>  .../bindings/crypto/amlogic,gxl-crypto.yaml   | 44 +++++++++++++++----
>  1 file changed, 36 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/crypto/amlogic,gxl-crypto.yaml b/Documentation/devicetree/bindings/crypto/amlogic,gxl-crypto.yaml
> index 948e11ebe4ee..62f772036b06 100644
> --- a/Documentation/devicetree/bindings/crypto/amlogic,gxl-crypto.yaml
> +++ b/Documentation/devicetree/bindings/crypto/amlogic,gxl-crypto.yaml
> @@ -11,20 +11,30 @@ maintainers:
>  
>  properties:
>    compatible:
> -    items:
> -      - const: amlogic,gxl-crypto
> +    oneOf:
> +      - items:
> +          - enum:
> +              - amlogic,a1-crypto
> +              - amlogic,s4-crypto
> +          - const: amlogic,g12a-crypto
> +      - items:
> +          - const: amlogic,gxl-crypto
> +      - items:
> +          - const: amlogic,axg-crypto
> +      - items:
> +          - const: amlogic,g12a-crypto

You just ignored my comment, so repeat: that's just enum with three entries.

>  
>    reg:
>      maxItems: 1
>  
> -  interrupts:
> -    items:
> -      - description: Interrupt for flow 0
> -      - description: Interrupt for flow 1
> +  interrupts: true

No, you need widest constraints here.

>  
>    clocks:
>      maxItems: 1
>  
> +  power-domains:
> +    maxItems: 1
> +
>    clock-names:
>      const: blkmv
>  
> @@ -32,8 +42,26 @@ required:
>    - compatible
>    - reg
>    - interrupts
> -  - clocks
> -  - clock-names
> +
> +allOf:
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            const: amlogic,gxl-crypto
> +    then:
> +      required:
> +        - clocks
> +        - clock-names
> +      properties:
> +        interrupts:
> +          maxItems: 2
> +          minItems: 2

Instead describe items like it was in original code.

> +    else:
> +      properties:
> +        interrupts:
> +          maxItems: 1
> +          minItems: 1

and what interrupt is expected here?

>  
>  additionalProperties: false
>  

Best regards,
Krzysztof


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2024-02-08  8:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 15:55 [PATCH v3 00/20] Support more Amlogic SoC families in crypto driver Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 01/20] drivers: crypto: meson: don't hardcode IRQ count Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 02/20] drviers: crypto: meson: add platform data Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 03/20] drivers: crypto: meson: make CLK controller optional Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 04/20] drivers: crypto: meson: add MMIO helpers Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 05/20] drivers: crypto: meson: move get_engine_number() Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 06/20] drivers: crypto: meson: drop status field from meson_flow Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 07/20] drivers: crypto: meson: move algs definition and cipher API to cipher.c Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 08/20] drivers: crypto: meson: cleanup defines Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 09/20] drivers: crypto: meson: process more than MAXDESCS descriptors Alexey Romanov
2024-02-06 13:13   ` neil.armstrong
2024-02-06 14:07   ` Vadim Fedorenko
2024-02-05 15:55 ` [PATCH v3 10/20] drivers: crypto: meson: avoid kzalloc in engine thread Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 11/20] drivers: crypto: meson: introduce hasher Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 12/20] drivers: crypto: meson: add support for AES-CTR Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 13/20] drivers: crypto: meson: use fallback for 192-bit keys Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 14/20] drivers: crypto: meson: add support for G12-series Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 15/20] drivers: crypto: meson: add support for AXG-series Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 16/20] dt-bindings: crypto: meson: support new SoC's Alexey Romanov
2024-02-08  8:38   ` Krzysztof Kozlowski [this message]
2024-02-05 15:55 ` [PATCH v3 17/20] arch: arm64: dts: meson: a1: add crypto node Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 18/20] arch: arm64: dts: meson: s4: " Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 19/20] arch: arm64: dts: meson: g12: " Alexey Romanov
2024-02-05 15:55 ` [PATCH v3 20/20] arch: arm64: dts: meson: axg: " Alexey Romanov

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=b2e4ac25-5b07-46c7-a96f-8390a95584ea@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=avromanov@salutedevices.com \
    --cc=clabbe@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@salutedevices.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@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