From: Herbert Xu <herbert@gondor.apana.org.au>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Boris Brezillon <bbrezillon@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: crypto: Convert Marvell CESA to DT schema
Date: Mon, 19 May 2025 14:00:37 +0800 [thread overview]
Message-ID: <aCrJBaAlN8cZAv-A@gondor.apana.org.au> (raw)
In-Reply-To: <20250513184125.3052705-1-robh@kernel.org>
On Tue, May 13, 2025 at 01:41:23PM -0500, Rob Herring (Arm) wrote:
> Convert the Marvell CESA binding to DT schema format. The
> marvell-cesa.txt and mv_cesa.txt are duplicate bindings.
>
> The clock properties are quite varied for each platform hence the
> if/then schemas. The old binding was fairly accurate with reality.
>
> The original binding didn't mention there is 1 interrupt per CESA
> engine. Based on users, there's a maximum of 2 engines.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> .../bindings/crypto/marvell,orion-crypto.yaml | 133 ++++++++++++++++++
> .../bindings/crypto/marvell-cesa.txt | 44 ------
> .../devicetree/bindings/crypto/mv_cesa.txt | 32 -----
> 3 files changed, 133 insertions(+), 76 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml
> delete mode 100644 Documentation/devicetree/bindings/crypto/marvell-cesa.txt
> delete mode 100644 Documentation/devicetree/bindings/crypto/mv_cesa.txt
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2025-05-19 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 18:41 [PATCH] dt-bindings: crypto: Convert Marvell CESA to DT schema Rob Herring (Arm)
2025-05-19 6:00 ` Herbert Xu [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=aCrJBaAlN8cZAv-A@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=andrew@lunn.ch \
--cc=bbrezillon@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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