From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <herbert@gondor.apana.org.au>,
<krzysztof.kozlowski@canonical.com>, <robh+dt@kernel.org>
Cc: <nicolas.ferre@microchip.com>, <claudiu.beznea@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>,
"Tudor Ambarus" <tudor.ambarus@microchip.com>
Subject: [PACTH v3 0/3] dt-bindings: crypto: Convert atmel-crypto to YAML
Date: Fri, 11 Feb 2022 10:21:11 +0200 [thread overview]
Message-ID: <20220211082114.452911-1-tudor.ambarus@microchip.com> (raw)
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.
v3:
- update license to (GPL-2.0-only OR BSD-2-Clause)
- add "Copyright (C) 2022 Microchip Technology, Inc. and its subsidiaries"
- add Krzysztof's R-b tag on patch 3/3. Chose to keep "maxItems: 1" instead
of "items" and "description" because that's what the guide at [1] suggests:
"# Cases that have only a single entry just need to express that with
maxItems"
[1] https://www.kernel.org/doc/html/latest/devicetree/bindings/writing-schema.html#annotated-example-schema
v2:
- use generic "crypto" node name
- drop redundant status = "okay" - it's the default state anyway
- introduce empty line for readability
- be specific and rename the bindings to let room for future possible
lines of architectures.
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
.../crypto/atmel,at91sam9g46-aes.yaml | 66 ++++++++++++++++++
.../crypto/atmel,at91sam9g46-sha.yaml | 60 ++++++++++++++++
.../crypto/atmel,at91sam9g46-tdes.yaml | 64 +++++++++++++++++
.../bindings/crypto/atmel-crypto.txt | 68 -------------------
4 files changed, 190 insertions(+), 68 deletions(-)
create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml
create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-sha.yaml
create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-tdes.yaml
delete mode 100644 Documentation/devicetree/bindings/crypto/atmel-crypto.txt
--
2.25.1
next reply other threads:[~2022-02-11 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 8:21 Tudor Ambarus [this message]
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
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=20220211082114.452911-1-tudor.ambarus@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kavyasree.kotagiri@microchip.com \
--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=nicolas.ferre@microchip.com \
--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).