From: <Tudor.Ambarus@microchip.com>
To: <krzysztof.kozlowski@canonical.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 1/3] dt-bindings: crypto: Convert Atmel AES to yaml
Date: Tue, 8 Feb 2022 04:10:25 +0000 [thread overview]
Message-ID: <ec358f0f-e3e2-a97b-e09a-d397edc65c72@microchip.com> (raw)
In-Reply-To: <f8387f12-24f9-4a39-e9b8-3b83f1de078d@canonical.com>
Hi, Krzysztof,
On 2/7/22 17:56, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 07/02/2022 04:24, 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>
>> ---
>> .../devicetree/bindings/crypto/atmel,aes.yaml | 65 +++++++++++++++++++
>> .../bindings/crypto/atmel-crypto.txt | 20 ------
>> 2 files changed, 65 insertions(+), 20 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/crypto/atmel,aes.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/crypto/atmel,aes.yaml b/Documentation/devicetree/bindings/crypto/atmel,aes.yaml
>> new file mode 100644
>> index 000000000000..f77ec04dbabe
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/crypto/atmel,aes.yaml
>> @@ -0,0 +1,65 @@
>> +# SPDX-License-Identifier: GPL-2.0-only
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/crypto/atmel,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>
>
> One empty line for readability.
Ok.
>
>> + aes: aes@f8038000 {
>
> Generic node name, so "crypto".
Hm, I'm not convinced why, would you please give more details about this
requirement? This IP is capable of doing just AES operations, I find it
generic enough. We use the "aes" name on all our SoCs that have a version
of this IP, that would be quite a change. So I would prefer to keep the
"aes" name if possible.
>
>> + compatible = "atmel,at91sam9g46-aes";
>> + reg = <0xe1810000 0x100>;
>> + 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";
>> + status= "okay";
>> + };
>
> Drop the status property.
Ok. Thanks for reviewing.
ta
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-02-08 4:10 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 [this message]
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
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=ec358f0f-e3e2-a97b-e09a-d397edc65c72@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=davem@davemloft.net \
--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).