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, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.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: [PATCH v5 0/2] STM32 CRYP crypto driver
Date: Thu, 19 Oct 2017 17:10:28 +0200 [thread overview]
Message-ID: <1508425830-13565-1-git-send-email-fabien.dessenne@st.com> (raw)
This set of patches adds a new crypto driver for STMicroelectronics stm32 HW.
This drivers uses the crypto API and provides with HW-enabled block cipher
algorithms.
This driver was successfully tested with tcrypt / testmgr.
Changes since v5:
-add timeout in wait_busy function
-clear key after use
-misc : remove unused functions, use -Exx, use dev_err
Changes since v4:
- remove AEAD support from crypto engine as proposed by Herbert : waiting for
the crypto_engine interface clean up before
[https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1474434.html]
- remove AES GCM & CCM algorithms
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 (2):
dt-bindings: Document STM32 CRYP bindings
crypto: stm32 - Support for STM32 CRYP crypto module
.../devicetree/bindings/crypto/st,stm32-cryp.txt | 19 +
drivers/crypto/stm32/Kconfig | 9 +
drivers/crypto/stm32/Makefile | 3 +-
drivers/crypto/stm32/stm32-cryp.c | 1172 ++++++++++++++++++++
4 files changed, 1202 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/crypto/st,stm32-cryp.txt
create mode 100644 drivers/crypto/stm32/stm32-cryp.c
--
2.7.4
next reply other threads:[~2017-10-19 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 15:10 Fabien Dessenne [this message]
2017-10-19 15:10 ` [PATCH v5 1/2] dt-bindings: Document STM32 CRYP bindings Fabien Dessenne
[not found] ` <1508425830-13565-1-git-send-email-fabien.dessenne-qxv4g6HH51o@public.gmane.org>
2017-10-19 15:10 ` [PATCH v5 2/2] crypto: stm32 - Support for STM32 CRYP crypto module Fabien Dessenne
[not found] ` <1508425830-13565-3-git-send-email-fabien.dessenne-qxv4g6HH51o@public.gmane.org>
2017-10-22 7:26 ` Corentin Labbe
2017-11-07 14:40 ` Fabien DESSENNE
[not found] ` <d924a278-90d0-969e-f1ae-a12f92e8972d-qxv4g6HH51o@public.gmane.org>
2017-11-13 10:30 ` Fabien DESSENNE
2017-11-28 9:47 ` Fabien DESSENNE
2017-11-29 6:29 ` [PATCH v5 0/2] STM32 CRYP crypto driver 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=1508425830-13565-1-git-send-email-fabien.dessenne@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;
as well as URLs for NNTP newsgroup(s).