mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <Tudor.Ambarus@microchip.com>, <herbert@gondor.apana.org.au>,
	<krzysztof.kozlowski@canonical.com>, <robh+dt@kernel.org>
Cc: <Nicolas.Ferre@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>
Subject: Re: [PACTH v4 0/3] dt-bindings: crypto: Convert atmel-crypto to YAML
Date: Fri, 11 Feb 2022 10:14:02 +0000	[thread overview]
Message-ID: <0e5a2956-7a43-04cb-a042-65bbc5f9b164@microchip.com> (raw)
In-Reply-To: <20220211093922.456634-1-tudor.ambarus@microchip.com>

On 11.02.2022 11:39, Tudor Ambarus wrote:
> 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.
> 
> v4:
> - fix the AES example: match the node's address with the reg's address
> - collect Krzysztof's R-b tags
> 
> 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

Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>

> 
>  .../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
> 


      parent reply	other threads:[~2022-02-11 10:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  9:39 Tudor Ambarus
2022-02-11  9:39 ` [PACTH v4 1/3] dt-bindings: crypto: Convert Atmel AES to yaml Tudor Ambarus
2022-02-17 23:28   ` Rob Herring
2022-02-11  9:39 ` [PACTH v4 2/3] dt-bindings: crypto: Convert Atmel TDES " Tudor Ambarus
2022-02-17 23:28   ` Rob Herring
2022-02-11  9:39 ` [PACTH v4 3/3] dt-bindings: crypto: Convert Atmel SHA " Tudor Ambarus
2022-02-17 23:29   ` Rob Herring
2022-02-11 10:14 ` Claudiu.Beznea [this message]

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=0e5a2956-7a43-04cb-a042-65bbc5f9b164@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Kavyasree.Kotagiri@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --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

all inboxes | Powered by JetHome®