From: Fabien DESSENNE <fabien.dessenne@st.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Benjamin GAIGNARD <benjamin.gaignard@st.com>,
Lionel DEBIEVE <lionel.debieve@st.com>,
Ludovic BARRE <ludovic.barre@st.com>
Subject: Re: [PATCH v3 0/3] STM32 CRYP crypto driver
Date: Mon, 18 Sep 2017 09:40:02 +0000 [thread overview]
Message-ID: <7be8c468-2e95-c781-3af3-d411acc80598@st.com> (raw)
In-Reply-To: <1503047946-27799-1-git-send-email-fabien.dessenne@st.com>
Just a gentle ping ... or have I missed out on a reply?
On 18/08/17 11:19, Fabien Dessenne wrote:
> This set of patches adds a new crypto driver for STMicroelectronics stm32 HW.
> This drivers uses the crypto API and provides with HW-enabled AEAD and block
> cipher algorithms.
> It makes use of the crypto engine which is upgraded in order to support AEAD
> requests.
>
> This driver was successfully tested with tcrypt / testmgr.
>
> Changes since v3:
> - update dt-bindings with Rob Herring remarks
>
> Changes since v2:
> - update dt-bindings (interrupts description)
> - rebase on STM32 crypto patches (L. Debieve : update CRC32 + add HASH)
>
> Fabien Dessenne (3):
> crypto: engine - permit to enqueue aead_request
> dt-bindings: Document STM32 CRYP bindings
> crypto: stm32 - Support for STM32 CRYP crypto module
>
> .../devicetree/bindings/crypto/st,stm32-cryp.txt | 19 +
> crypto/crypto_engine.c | 101 +
> drivers/crypto/stm32/Kconfig | 9 +
> drivers/crypto/stm32/Makefile | 3 +-
> drivers/crypto/stm32/stm32-cryp.c | 1962 ++++++++++++++++++++
> include/crypto/engine.h | 16 +
> 6 files changed, 2109 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-cryp.txt
> create mode 100644 drivers/crypto/stm32/stm32-cryp.c
>
prev parent reply other threads:[~2017-09-18 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 9:19 Fabien Dessenne
2017-08-18 9:19 ` [PATCH v3 1/3] crypto: engine - permit to enqueue aead_request Fabien Dessenne
2017-09-22 9:09 ` Herbert Xu
2017-10-03 7:48 ` Fabien DESSENNE
2017-10-05 3:39 ` Herbert Xu
2017-10-06 9:26 ` Fabien DESSENNE
2017-08-18 9:19 ` [PATCH v3 2/3] dt-bindings: Document STM32 CRYP bindings Fabien Dessenne
2017-08-18 9:19 ` [PATCH v3 3/3] crypto: stm32 - Support for STM32 CRYP crypto module Fabien Dessenne
2017-09-18 9:40 ` Fabien DESSENNE [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=7be8c468-2e95-c781-3af3-d411acc80598@st.com \
--to=fabien.dessenne@st.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.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=lionel.debieve@st.com \
--cc=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.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
all inboxes | Powered by JetHome®