[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220207032405.70733-1-tudor.ambarus@microchip.com>
Date: Mon, 7 Feb 2022 05:24:02 +0200
From: Tudor Ambarus <tudor.ambarus@...rochip.com>
To: <herbert@...dor.apana.org.au>, <robh+dt@...nel.org>
CC: <davem@...emloft.net>, <nicolas.ferre@...rochip.com>,
<claudiu.beznea@...rochip.com>, <alexandre.belloni@...tlin.com>,
<linux-crypto@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
"Tudor Ambarus" <tudor.ambarus@...rochip.com>
Subject: [PATCH 0/3] dt-bindings: crypto: Convert atmel-{aes,tdes,sha} to YAML
Convert Atmel AES, TDES and SHA documentation to yaml format. There is one
binding defined per file. Keeping all bindings under the same yaml does
not make sense, as these are individual IPs. With the conversion the clock
and clock-names properties are made mandatory, to reflect how the drivers
treat them: when these properties are not provided, the drivers return
error.
Tudor Ambarus (3):
dt-bindings: crypto: Convert Atmel AES to yaml
dt-bindings: crypto: Convert Atmel TDES to yaml
dt-bindings: crypto: Convert Atmel SHA to yaml
.../devicetree/bindings/crypto/atmel,aes.yaml | 65 ++++++++++++++++++
.../devicetree/bindings/crypto/atmel,sha.yaml | 59 ++++++++++++++++
.../bindings/crypto/atmel,tdes.yaml | 63 +++++++++++++++++
.../bindings/crypto/atmel-crypto.txt | 68 -------------------
4 files changed, 187 insertions(+), 68 deletions(-)
create mode 100644 Documentation/devicetree/bindings/crypto/atmel,aes.yaml
create mode 100644 Documentation/devicetree/bindings/crypto/atmel,sha.yaml
create mode 100644 Documentation/devicetree/bindings/crypto/atmel,tdes.yaml
delete mode 100644 Documentation/devicetree/bindings/crypto/atmel-crypto.txt
--
2.25.1
Powered by blists - more mailing lists