From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-crypto@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Lionel Debieve <lionel.debieve@foss.st.com>,
phone-devel@vger.kernel.org, devicetree@vger.kernel.org,
Stefan Hansson <newbyte@disroot.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH] dt-bindings: crypto: Add ST-Ericsson Ux500 CRYP
Date: Mon, 25 Jul 2022 16:38:09 -0600 [thread overview]
Message-ID: <20220725223809.GA2874868-robh@kernel.org> (raw)
In-Reply-To: <20220721163010.1060062-1-linus.walleij@linaro.org>
On Thu, 21 Jul 2022 18:30:10 +0200, Linus Walleij wrote:
> This adds device tree bindings for the Ux500 CRYP block.
>
> This has been used for ages in the kernel device tree for
> Ux500 but was never documented, so fill in the gap.
>
> Cc: devicetree@vger.kernel.org
> Cc: Lionel Debieve <lionel.debieve@foss.st.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> The relationship to the existing STM32 CRYP block is pretty
> obvious when looking at the register map. If preferred, I
> can just extend the STM32 bindings with these extra
> (generic) properties and compatibles as well.
> ---
> .../crypto/stericsson,ux500-cryp.yaml | 67 +++++++++++++++++++
> 1 file changed, 67 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/crypto/stericsson,ux500-cryp.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2022-07-25 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 16:30 [PATCH] dt-bindings: crypto: Add ST-Ericsson Ux500 CRYP Linus Walleij
2022-07-25 22:38 ` Rob Herring [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=20220725223809.GA2874868-robh@kernel.org \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linus.walleij@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=lionel.debieve@foss.st.com \
--cc=newbyte@disroot.org \
--cc=phone-devel@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;
as well as URLs for NNTP newsgroup(s).