[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5563605-7b61-c23e-68ec-6e315efb268d@canonical.com>
Date: Tue, 8 Feb 2022 12:58:44 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Tudor Ambarus <tudor.ambarus@...rochip.com>,
herbert@...dor.apana.org.au
Cc: nicolas.ferre@...rochip.com, claudiu.beznea@...rochip.com,
alexandre.belloni@...tlin.com, linux-crypto@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kavyasree.kotagiri@...rochip.com, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: crypto: Convert Atmel AES to yaml
On 08/02/2022 11:49, 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@...rochip.com>
> ---
> .../crypto/atmel,at91sam9g46-aes.yaml | 65 +++++++++++++++++++
> .../bindings/crypto/atmel-crypto.txt | 20 ------
> 2 files changed, 65 insertions(+), 20 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml
>
I understand that you keep the license GPL-2.0 (not recommended mix)
because of example coming from previous bindings or from DTS (both GPL-2.0)?
Best regards,
Krzysztof
Powered by blists - more mailing lists