From: Corentin Labbe <clabbe@baylibre.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
mripard@kernel.org, wens@csie.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com,
Corentin Labbe <clabbe@baylibre.com>
Subject: [PATCH 0/9] crypto: sun8i-ce: support TRNG, PRNG and hashes
Date: Mon, 13 Apr 2020 09:58:00 +0000 [thread overview]
Message-ID: <1586771889-3299-1-git-send-email-clabbe@baylibre.com> (raw)
Hello
The main goal of this serie is to add support for TRNG, PRNG and hashes
to the sun8i-ce.
The whole serie is tested with CRYPTO_EXTRA_TESTS enabled and loading
tcrypt.
The PRNG and TRNG are tested with rngtest.
Note that the first patch is common with the recent sun8i-ss PRNG+hashes serie.
Regards
Corentin Labbe (9):
crypto: rng - add missing __crypto_rng_cast to the rng header
crypto: sun8i-ce: move iv data to request context
crypto: sun8i-ce: split into prepare/run/unprepare
crypto: sun8i-ce: handle different error registers
crypto: sun8i-ce: rename has_t_dlen_in_bytes to cipher_t_dlen_in_bytes
crypto: sun8i-ce: support hash algorithms
crypto: sun8i-ce: Add stat_bytes debugfs
crypto: sun8i-ce: Add support for the PRNG
crypto: sun8i-ce: Add support for the TRNG
drivers/crypto/allwinner/Kconfig | 26 ++
drivers/crypto/allwinner/sun8i-ce/Makefile | 3 +
.../allwinner/sun8i-ce/sun8i-ce-cipher.c | 99 ++++-
.../crypto/allwinner/sun8i-ce/sun8i-ce-core.c | 365 ++++++++++++++-
.../crypto/allwinner/sun8i-ce/sun8i-ce-hash.c | 415 ++++++++++++++++++
.../crypto/allwinner/sun8i-ce/sun8i-ce-prng.c | 191 ++++++++
.../crypto/allwinner/sun8i-ce/sun8i-ce-trng.c | 123 ++++++
drivers/crypto/allwinner/sun8i-ce/sun8i-ce.h | 135 +++++-
include/crypto/rng.h | 5 +
9 files changed, 1323 insertions(+), 39 deletions(-)
create mode 100644 drivers/crypto/allwinner/sun8i-ce/sun8i-ce-hash.c
create mode 100644 drivers/crypto/allwinner/sun8i-ce/sun8i-ce-prng.c
create mode 100644 drivers/crypto/allwinner/sun8i-ce/sun8i-ce-trng.c
--
2.24.1
next reply other threads:[~2020-04-13 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 9:58 Corentin Labbe [this message]
2020-04-13 9:58 ` [PATCH 1/9] crypto: rng - add missing __crypto_rng_cast to the rng header Corentin Labbe
2020-04-13 9:58 ` [PATCH 2/9] crypto: sun8i-ce: move iv data to request context Corentin Labbe
2020-04-13 9:58 ` [PATCH 3/9] crypto: sun8i-ce: split into prepare/run/unprepare Corentin Labbe
2020-04-13 9:58 ` [PATCH 4/9] crypto: sun8i-ce: handle different error registers Corentin Labbe
2020-04-13 9:58 ` [PATCH 5/9] crypto: sun8i-ce: rename has_t_dlen_in_bytes to cipher_t_dlen_in_bytes Corentin Labbe
2020-04-13 9:58 ` [PATCH 6/9] crypto: sun8i-ce: support hash algorithms Corentin Labbe
2020-04-13 9:58 ` [PATCH 7/9] crypto: sun8i-ce: Add stat_bytes debugfs Corentin Labbe
2020-04-13 9:58 ` [PATCH 8/9] crypto: sun8i-ce: Add support for the PRNG Corentin Labbe
2020-04-13 9:58 ` [PATCH 9/9] crypto: sun8i-ce: Add support for the TRNG Corentin Labbe
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=1586771889-3299-1-git-send-email-clabbe@baylibre.com \
--to=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--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=linux-sunxi@googlegroups.com \
--cc=mripard@kernel.org \
--cc=wens@csie.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).