From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Tudor Ambarus <tudor.ambarus@microchip.com>,
herbert@gondor.apana.org.au, robh+dt@kernel.org
Cc: davem@davemloft.net, nicolas.ferre@microchip.com,
claudiu.beznea@microchip.com, alexandre.belloni@bootlin.com,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: crypto: Convert Atmel TDES to yaml
Date: Mon, 7 Feb 2022 17:04:04 +0100 [thread overview]
Message-ID: <c7e160b0-16fb-79ca-c291-05571bbe8341@canonical.com> (raw)
In-Reply-To: <20220207032405.70733-3-tudor.ambarus@microchip.com>
On 07/02/2022 04:24, Tudor Ambarus wrote:
> Convert Atmel TDES documentation to yaml format. With the conversion the
> clock and clock-names properties are made mandatory. The driver returns
> -EINVAL if "tdes_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>
> ---
> .../bindings/crypto/atmel,tdes.yaml | 63 +++++++++++++++++++
> .../bindings/crypto/atmel-crypto.txt | 23 -------
> 2 files changed, 63 insertions(+), 23 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/atmel,tdes.yaml
>
> diff --git a/Documentation/devicetree/bindings/crypto/atmel,tdes.yaml b/Documentation/devicetree/bindings/crypto/atmel,tdes.yaml
> new file mode 100644
> index 000000000000..7efa5e4acaa1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/crypto/atmel,tdes.yaml
> @@ -0,0 +1,63 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/crypto/atmel,tdes.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Atmel Triple Data Encryption Standard (TDES) HW cryptographic accelerator
> +
> +maintainers:
> + - Tudor Ambarus <tudor.ambarus@microchip.com>
> +
> +properties:
> + compatible:
> + const: atmel,at91sam9g46-tdes
> +
Same comments as for patch 1 plus one new (also applying to previous
one). You named the file quite generic "atmel,tdes" or "atmel,aes", but
what if something newer comes for at91? Maybe name it instead
"atmel,at91sam9-aes"?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-02-07 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 3:24 [PATCH 0/3] dt-bindings: crypto: Convert atmel-{aes,tdes,sha} to YAML Tudor Ambarus
2022-02-07 3:24 ` [PATCH 1/3] dt-bindings: crypto: Convert Atmel AES to yaml Tudor Ambarus
2022-02-07 15:56 ` Krzysztof Kozlowski
2022-02-08 4:10 ` Tudor.Ambarus
2022-02-08 8:59 ` Krzysztof Kozlowski
2022-02-08 9:49 ` Tudor.Ambarus
2022-02-08 9:55 ` Krzysztof Kozlowski
2022-02-07 3:24 ` [PATCH 2/3] dt-bindings: crypto: Convert Atmel TDES " Tudor Ambarus
2022-02-07 16:04 ` Krzysztof Kozlowski [this message]
2022-02-08 4:04 ` Tudor.Ambarus
2022-02-08 9:01 ` Krzysztof Kozlowski
2022-02-08 9:19 ` Tudor.Ambarus
2022-02-07 3:24 ` [PATCH 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=c7e160b0-16fb-79ca-c291-05571bbe8341@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--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
all inboxes | Powered by JetHome®