From: <Claudiu.Beznea@microchip.com>
To: <Tudor.Ambarus@microchip.com>, <herbert@gondor.apana.org.au>,
<krzysztof.kozlowski@canonical.com>, <robh+dt@kernel.org>
Cc: <Nicolas.Ferre@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 08:55:33 +0000 [thread overview]
Message-ID: <edf01cb9-c887-83db-fe2c-4e4198ec93f9@microchip.com> (raw)
In-Reply-To: <20220211082114.452911-2-tudor.ambarus@microchip.com>
Hi Tudor,
On 11.02.2022 10: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
> +
> +maintainers:
> + - Tudor Ambarus <tudor.ambarus@microchip.com>
> +
> +properties:
> + compatible:
> + const: atmel,at91sam9g46-aes
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + const: aes_clk
> +
> + dmas:
> + items:
> + - description: TX DMA Channel
> + - description: RX DMA Channel
> +
> + dma-names:
> + items:
> + - const: tx
> + - const: rx
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> + - dmas
> + - dma-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/at91.h>
> + #include <dt-bindings/dma/at91.h>
> +
> + aes: crypto@f8038000 {
Address here ^
> + compatible = "atmel,at91sam9g46-aes";
> + reg = <0xe1810000 0x100>;
and here ^ don't match.
> + interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&pmc PMC_TYPE_PERIPHERAL 27>;
> + clock-names = "aes_clk";
> + dmas = <&dma0 AT91_XDMAC_DT_PERID(1)>,
> + <&dma0 AT91_XDMAC_DT_PERID(2)>;
> + dma-names = "tx", "rx";
> + };
> diff --git a/Documentation/devicetree/bindings/crypto/atmel-crypto.txt b/Documentation/devicetree/bindings/crypto/atmel-crypto.txt
> index f2aab3dc2b52..1353ebd0dcaa 100644
> --- a/Documentation/devicetree/bindings/crypto/atmel-crypto.txt
> +++ b/Documentation/devicetree/bindings/crypto/atmel-crypto.txt
> @@ -2,26 +2,6 @@
>
> These are the HW cryptographic accelerators found on some Atmel products.
>
> -* Advanced Encryption Standard (AES)
> -
> -Required properties:
> -- compatible : Should be "atmel,at91sam9g46-aes".
> -- reg: Should contain AES registers location and length.
> -- interrupts: Should contain the IRQ line for the AES.
> -- dmas: List of two DMA specifiers as described in
> - atmel-dma.txt and dma.txt files.
> -- dma-names: Contains one identifier string for each DMA specifier
> - in the dmas property.
> -
> -Example:
> -aes@f8038000 {
> - compatible = "atmel,at91sam9g46-aes";
> - reg = <0xf8038000 0x100>;
> - interrupts = <43 4 0>;
> - dmas = <&dma1 2 18>,
> - <&dma1 2 19>;
> - dma-names = "tx", "rx";
> -
> * Triple Data Encryption Standard (Triple DES)
>
> Required properties:
next prev parent reply other threads:[~2022-02-11 8:55 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
2022-02-11 8:55 ` Claudiu.Beznea [this message]
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=edf01cb9-c887-83db-fe2c-4e4198ec93f9@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).