From: Andre Przywara <andre.przywara@arm.com> To: Matt Mackall <mpm@selenic.com>, Herbert Xu <herbert@gondor.apana.org.au>, Mark Rutland <mark.rutland@arm.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Sudeep Holla <sudeep.holla@arm.com> Cc: linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Ard Biesheuvel <ardb@kernel.org>, Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>, Ali Saidi <alisaidi@amazon.com>, Jon Nettleton <jon@solid-run.com> Subject: [PATCH v3 0/2] hwrng: Add Arm SMCCC TRNG based driver Date: Mon, 26 Jul 2021 18:56:08 +0100 [thread overview] Message-ID: <20210726175610.3311-1-andre.przywara@arm.com> (raw) The "Arm True Random Number Generator Firmware Interface"[1] provides an SMCCC based interface to a true hardware random number generator. So far we are using that in arch_get_random_seed(), but it might be useful to expose the entropy through the /dev/hwrng device as well. This allows to assess the quality of the implementation, by using "rngtest" from the rng-tools package, for example. Patch 1 creates a platform device, triggered by the previous discovery of the SMCCC TRNG service. Patch 2 implements a hw_random platform driver, which is instantiated through this said platform device. The driver can be loaded as module, or built into the kernel. [1] https://developer.arm.com/documentation/den0098/latest/ Changelog v2 ... v3: - split platform device and driver Changelog v1 ... v2: - fix building as a module - de-register device upon exit - mention module name in Kconfig Andre Przywara (2): firmware: smccc: Register smccc_trng platform device hwrng: Add Arm SMCCC TRNG based driver drivers/char/hw_random/Kconfig | 14 +++ drivers/char/hw_random/Makefile | 1 + drivers/char/hw_random/arm_smccc_trng.c | 134 ++++++++++++++++++++++++ drivers/firmware/smccc/smccc.c | 17 +++ 4 files changed, 166 insertions(+) create mode 100644 drivers/char/hw_random/arm_smccc_trng.c -- 2.17.6
WARNING: multiple messages have this Message-ID (diff)
From: Andre Przywara <andre.przywara@arm.com> To: Matt Mackall <mpm@selenic.com>, Herbert Xu <herbert@gondor.apana.org.au>, Mark Rutland <mark.rutland@arm.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Sudeep Holla <sudeep.holla@arm.com> Cc: linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Ard Biesheuvel <ardb@kernel.org>, Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>, Ali Saidi <alisaidi@amazon.com>, Jon Nettleton <jon@solid-run.com> Subject: [PATCH v3 0/2] hwrng: Add Arm SMCCC TRNG based driver Date: Mon, 26 Jul 2021 18:56:08 +0100 [thread overview] Message-ID: <20210726175610.3311-1-andre.przywara@arm.com> (raw) The "Arm True Random Number Generator Firmware Interface"[1] provides an SMCCC based interface to a true hardware random number generator. So far we are using that in arch_get_random_seed(), but it might be useful to expose the entropy through the /dev/hwrng device as well. This allows to assess the quality of the implementation, by using "rngtest" from the rng-tools package, for example. Patch 1 creates a platform device, triggered by the previous discovery of the SMCCC TRNG service. Patch 2 implements a hw_random platform driver, which is instantiated through this said platform device. The driver can be loaded as module, or built into the kernel. [1] https://developer.arm.com/documentation/den0098/latest/ Changelog v2 ... v3: - split platform device and driver Changelog v1 ... v2: - fix building as a module - de-register device upon exit - mention module name in Kconfig Andre Przywara (2): firmware: smccc: Register smccc_trng platform device hwrng: Add Arm SMCCC TRNG based driver drivers/char/hw_random/Kconfig | 14 +++ drivers/char/hw_random/Makefile | 1 + drivers/char/hw_random/arm_smccc_trng.c | 134 ++++++++++++++++++++++++ drivers/firmware/smccc/smccc.c | 17 +++ 4 files changed, 166 insertions(+) create mode 100644 drivers/char/hw_random/arm_smccc_trng.c -- 2.17.6 _______________________________________________ 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-07-26 17:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-26 17:56 Andre Przywara [this message] 2021-07-26 17:56 ` [PATCH v3 0/2] hwrng: Add Arm SMCCC TRNG based driver Andre Przywara 2021-07-26 17:56 ` [PATCH v3 1/2] firmware: smccc: Register smccc_trng platform device Andre Przywara 2021-07-26 17:56 ` Andre Przywara 2021-07-26 17:56 ` [PATCH v3 2/2] hwrng: Add Arm SMCCC TRNG based driver Andre Przywara 2021-07-26 17:56 ` Andre Przywara 2021-07-26 22:37 ` Mark Brown 2021-07-26 22:37 ` Mark Brown 2021-07-27 0:30 ` Andre Przywara 2021-07-27 0:30 ` Andre Przywara 2021-07-27 0:59 ` Mark Brown 2021-07-27 0:59 ` Mark Brown
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=20210726175610.3311-1-andre.przywara@arm.com \ --to=andre.przywara@arm.com \ --cc=alisaidi@amazon.com \ --cc=ardb@kernel.org \ --cc=benh@kernel.crashing.org \ --cc=broonie@kernel.org \ --cc=herbert@gondor.apana.org.au \ --cc=jon@solid-run.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=mark.rutland@arm.com \ --cc=mpm@selenic.com \ --cc=sudeep.holla@arm.com \ --cc=will@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.