From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <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>,
"Tudor Ambarus" <tudor.ambarus@microchip.com>
Subject: [PATCH 0/3] dt-bindings: crypto: Convert atmel-{aes,tdes,sha} to YAML
Date: Mon, 7 Feb 2022 05:24:02 +0200 [thread overview]
Message-ID: <20220207032405.70733-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.
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
next reply other threads:[~2022-02-07 5:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 3:24 Tudor Ambarus [this message]
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
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=20220207032405.70733-1-tudor.ambarus@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--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).