From: Corentin Labbe <clabbe@baylibre.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
linus.walleij@linaro.org, linux@armlinux.org.uk,
robh+dt@kernel.org, ulli.kroll@googlemail.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Corentin Labbe <clabbe@baylibre.com>
Subject: [PATCH v2 0/5] crypto: add gemini/sl3516 crypto driver
Date: Tue, 1 Jun 2021 15:11:27 +0000 [thread overview]
Message-ID: <20210601151132.1893443-1-clabbe@baylibre.com> (raw)
The gemini SL3516 SoC has a crypto IP.
This serie had support for it.
It was tested with CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y.
Furthermore, it survives hours and gigs of write/read to a luks2 using xts(ecb-aes-sl3516).
Performance is quite good.
On a luks2 partition (2To with bs=4096), a fsck comes from 14m26(without CE) to 8m48(with CE).
So it is really usefull.
With bs=512, the performance is similar with software.
Changes since v1:
- reworded dt-binding subject patch
- fixed build with CRYPTO_DEV_SL3516_DEBUG
Corentin Labbe (5):
dt-bindings: crypto: Add documentation for sl3516-ce
crypto: Add sl3516 crypto engine
ARM: dts: gemini: add crypto node
ARM: gemini_config: enable sl3516-ce crypto
MAINTAINERS: add gemini crypto sl3516-ce
.../crypto/cortina,sl3516-crypto.yaml | 50 ++
MAINTAINERS | 7 +
arch/arm/boot/dts/gemini.dtsi | 8 +
arch/arm/configs/gemini_defconfig | 1 +
drivers/crypto/Kconfig | 19 +
drivers/crypto/Makefile | 1 +
drivers/crypto/gemini/Makefile | 2 +
drivers/crypto/gemini/sl3516-ce-cipher.c | 388 +++++++++++++
drivers/crypto/gemini/sl3516-ce-core.c | 535 ++++++++++++++++++
drivers/crypto/gemini/sl3516-ce-rng.c | 61 ++
drivers/crypto/gemini/sl3516-ce.h | 347 ++++++++++++
11 files changed, 1419 insertions(+)
create mode 100644 Documentation/devicetree/bindings/crypto/cortina,sl3516-crypto.yaml
create mode 100644 drivers/crypto/gemini/Makefile
create mode 100644 drivers/crypto/gemini/sl3516-ce-cipher.c
create mode 100644 drivers/crypto/gemini/sl3516-ce-core.c
create mode 100644 drivers/crypto/gemini/sl3516-ce-rng.c
create mode 100644 drivers/crypto/gemini/sl3516-ce.h
--
2.31.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-06-01 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 15:11 Corentin Labbe [this message]
2021-06-01 15:11 ` [PATCH v2 1/5] dt-bindings: crypto: Add documentation for sl3516-ce Corentin Labbe
2021-06-01 15:11 ` [PATCH v2 2/5] crypto: Add sl3516 crypto engine Corentin Labbe
2021-06-01 15:11 ` [PATCH v2 3/5] ARM: dts: gemini: add crypto node Corentin Labbe
2021-06-01 15:11 ` [PATCH v2 4/5] ARM: gemini_config: enable sl3516-ce crypto Corentin Labbe
2021-06-01 15:11 ` [PATCH v2 5/5] MAINTAINERS: add gemini crypto sl3516-ce Corentin Labbe
2021-06-11 7:17 ` [PATCH v2 0/5] crypto: add gemini/sl3516 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=20210601151132.1893443-1-clabbe@baylibre.com \
--to=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=ulli.kroll@googlemail.com \
/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).