From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: "Andrey Smirnov" <andrew.smirnov@gmail.com>,
"Chris Healy" <cphealy@gmail.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Iuliana Prodan" <iuliana.prodan@nxp.com>,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: [PATCH v2 0/6] enable CAAM's HWRNG as default
Date: Mon, 18 Nov 2019 07:38:37 -0800 [thread overview]
Message-ID: <20191118153843.28136-1-andrew.smirnov@gmail.com> (raw)
Everyone:
This series is a continuation of original [discussion]. I don't know
if what's in the series is enough to use CAAMs HWRNG system wide, but
I am hoping that with enough iterations and feedback it will be.
Changes since [v1]:
- Original hw_random replaced with the one using output of TRNG directly
- SEC4 DRNG IP block exposed via crypto API
- Small fix regarding use of GFP_DMA added to the series
Feedback is welcome!
Thanks,
Andrey Smirnov
[discussion] https://patchwork.kernel.org/patch/9850669/
[v1] lore.kernel.org/lkml/20191029162916.26579-1-andrew.smirnov@gmail.com
Andrey Smirnov (6):
crypto: caam - RNG4 TRNG errata
crypto: caam - enable prediction resistance in HRWNG
crypto: caam - allocate RNG instantiation descriptor with GFP_DMA
crypto: caam - move RNG presense check into a shared function
crypto: caam - replace DRNG with TRNG for use with hw_random
crypto: caam - expose SEC4 DRNG via crypto RNG API
drivers/crypto/caam/Kconfig | 15 +-
drivers/crypto/caam/Makefile | 3 +-
drivers/crypto/caam/caamrng.c | 358 ----------------------------------
drivers/crypto/caam/ctrl.c | 29 ++-
drivers/crypto/caam/desc.h | 2 +
drivers/crypto/caam/drng.c | 175 +++++++++++++++++
drivers/crypto/caam/intern.h | 32 ++-
drivers/crypto/caam/jr.c | 3 +-
drivers/crypto/caam/regs.h | 14 +-
drivers/crypto/caam/trng.c | 85 ++++++++
10 files changed, 334 insertions(+), 382 deletions(-)
delete mode 100644 drivers/crypto/caam/caamrng.c
create mode 100644 drivers/crypto/caam/drng.c
create mode 100644 drivers/crypto/caam/trng.c
--
2.21.0
next reply other threads:[~2019-11-18 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 15:38 Andrey Smirnov [this message]
2019-11-18 15:38 ` [PATCH v2 1/6] crypto: caam - RNG4 TRNG errata Andrey Smirnov
2019-11-18 15:38 ` [PATCH v2 2/6] crypto: caam - enable prediction resistance in HRWNG Andrey Smirnov
2019-11-18 15:38 ` [PATCH v2 3/6] crypto: caam - allocate RNG instantiation descriptor with GFP_DMA Andrey Smirnov
2019-11-18 15:38 ` [PATCH v2 4/6] crypto: caam - move RNG presense check into a shared function Andrey Smirnov
2019-11-18 15:38 ` [PATCH v2 5/6] crypto: caam - replace DRNG with TRNG for use with hw_random Andrey Smirnov
2019-11-18 15:50 ` Lucas Stach
2019-11-19 15:28 ` Andrey Smirnov
2019-11-18 15:38 ` [PATCH v2 6/6] crypto: caam - expose SEC4 DRNG via crypto RNG API Andrey Smirnov
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=20191118153843.28136-1-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=iuliana.prodan@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@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).