public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Tudor Ambarus <tudor.ambarus@microchip.com>,
	herbert@gondor.apana.org.au, robh+dt@kernel.org
Cc: nicolas.ferre@microchip.com, claudiu.beznea@microchip.com,
	alexandre.belloni@bootlin.com, linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kavyasree.kotagiri@microchip.com,
	devicetree@vger.kernel.org
Subject: Re: [PACTH v3 1/3] dt-bindings: crypto: Convert Atmel AES to yaml
Date: Fri, 11 Feb 2022 09:26:48 +0100	[thread overview]
Message-ID: <8e44a919-cd2b-669c-aff3-bb79f16c6541@canonical.com> (raw)
In-Reply-To: <20220211082114.452911-2-tudor.ambarus@microchip.com>

On 11/02/2022 09:21, Tudor Ambarus wrote:
> Convert Atmel AES documentation to yaml format. With the conversion the
> clock and clock-names properties are made mandatory. The driver returns
> -EINVAL if "aes_clk" is not found, reflect that in the bindings and make
> the clock and clock-names properties mandatory. Update the example to
> better describe how one should define the dt node.
> 
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
>  .../crypto/atmel,at91sam9g46-aes.yaml         | 66 +++++++++++++++++++
>  .../bindings/crypto/atmel-crypto.txt          | 20 ------
>  2 files changed, 66 insertions(+), 20 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml
> 
> diff --git a/Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml b/Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml
> new file mode 100644
> index 000000000000..fe59ad30b171
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (C) 2022 Microchip Technology, Inc. and its subsidiaries
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/crypto/atmel,at91sam9g46-aes.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Atmel Advanced Encryption Standard (AES) HW cryptographic accelerator
> +


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>


Best regards,
Krzysztof

  reply	other threads:[~2022-02-11  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  8:21 [PACTH v3 0/3] dt-bindings: crypto: Convert atmel-crypto to YAML Tudor Ambarus
2022-02-11  8:21 ` [PACTH v3 1/3] dt-bindings: crypto: Convert Atmel AES to yaml Tudor Ambarus
2022-02-11  8:26   ` Krzysztof Kozlowski [this message]
2022-02-11  8:55   ` Claudiu.Beznea
2022-02-11  8:21 ` [PACTH v3 2/3] dt-bindings: crypto: Convert Atmel TDES " Tudor Ambarus
2022-02-11  8:27   ` Krzysztof Kozlowski
2022-02-11  8:21 ` [PACTH v3 3/3] dt-bindings: crypto: Convert Atmel SHA " Tudor Ambarus

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=8e44a919-cd2b-669c-aff3-bb79f16c6541@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kavyasree.kotagiri@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh+dt@kernel.org \
    --cc=tudor.ambarus@microchip.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