From: "Rob Herring (Arm)" <robh@kernel.org>
To: "J. Neuschäfer" <j.ne@posteo.net>
Cc: Frank Li <Frank.Li@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Frank Li <Frank.li@nxp.com>
Subject: Re: [PATCH v3] dt-bindings: crypto: Convert fsl,sec-2.0 to YAML
Date: Fri, 21 Feb 2025 17:12:55 -0600 [thread overview]
Message-ID: <174017957412.293199.15568009985621401095.robh@kernel.org> (raw)
In-Reply-To: <20250220-ppcyaml-crypto-v3-1-99eedece4821@posteo.net>
On Thu, 20 Feb 2025 12:57:35 +0100, J. Neuschäfer wrote:
> Convert the Freescale security engine (crypto accelerator) binding from
> text form to YAML. The list of compatible strings reflects what was
> previously described in prose; not all combinations occur in existing
> devicetrees.
>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> ---
> V3:
> - split out as a single patch
> - Add Frank Li's R-b tag
> - fix typo in email address syntax
> - normalize spelling of "descriptor type", and reformat the description
> of fsl,descriptor-types-mask for readability
> - add missing end-of-document marker (...)
>
> V2:
> - part of series [PATCH v2 00/12] YAML conversion of several Freescale/PowerPC DT bindings
> Link: https://lore.kernel.org/lkml/20250207-ppcyaml-v2-3-8137b0c42526@posteo.net/
> - several improvements suggested by Rob Herring:
> - remove unnecessary multiline markers
> - constrain fsl,num-channels to enum: [1,4]
> - constrain fsl,channel-fifo-len to plausible limits
> - constrain fsl,exec-units-mask to maximum=0xfff
> - trim subject line (remove "binding")
> ---
> .../devicetree/bindings/crypto/fsl,sec2.0.yaml | 144 +++++++++++++++++++++
> .../devicetree/bindings/crypto/fsl-sec2.txt | 65 ----------
> 2 files changed, 144 insertions(+), 65 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-02-21 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 11:57 J. Neuschäfer via B4 Relay
2025-02-21 23:12 ` Rob Herring (Arm) [this message]
2025-03-02 8:12 ` Herbert Xu
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=174017957412.293199.15568009985621401095.robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=j.ne@posteo.net \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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®