From: Leo Liang <ycliang@andestech.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Rick Chen <rick@andestech.com>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Anup Patel <apatel@ventanamicro.com>,
Kautuk Consul <kconsul@ventanamicro.com>,
Chanho Park <chanho61.park@samsung.com>, <u-boot@lists.denx.de>
Subject: Re: [RFC v2 2/2] rng: Provide a RNG based on the RISC-V Zkr ISA extension
Date: Mon, 30 Oct 2023 16:25:11 +0800 [thread overview]
Message-ID: <ZT9oZ7rf1GiWeP9j@swlinux02> (raw)
In-Reply-To: <20231029084533.44607-3-heinrich.schuchardt@canonical.com>
On Sun, Oct 29, 2023 at 09:45:33AM +0100, Heinrich Schuchardt wrote:
> The Zkr ISA extension (ratified Nov 2021) introduced the seed CSR. It
> provides an interface to a physical entropy source.
>
> A RNG driver based on the seed CSR is provided. It depends on
> mseccfg.sseed being set in the SBI firmware.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> v2:
> Resume after exception if seed CSR cannot be read.
> ---
> drivers/rng/Kconfig | 8 +++
> drivers/rng/Makefile | 1 +
> drivers/rng/riscv_zkr_rng.c | 116 ++++++++++++++++++++++++++++++++++++
> 3 files changed, 125 insertions(+)
> create mode 100644 drivers/rng/riscv_zkr_rng.c
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
next prev parent reply other threads:[~2023-10-30 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 8:45 [RFC v2 0/2] rng: Provide a RNG based on the RISC-V Zkr ISA extension Heinrich Schuchardt
2023-10-29 8:45 ` [RFC v2 1/2] riscv: allow resume after exception Heinrich Schuchardt
2023-10-30 8:24 ` Leo Liang
2023-10-31 7:53 ` Xiang W
2023-10-31 12:09 ` Heinrich Schuchardt
2023-10-31 15:19 ` Xiang W
2023-10-29 8:45 ` [RFC v2 2/2] rng: Provide a RNG based on the RISC-V Zkr ISA extension Heinrich Schuchardt
2023-10-30 8:25 ` Leo Liang [this message]
2023-10-31 6:16 ` merle w
2023-10-31 6:38 ` Heinrich Schuchardt
2023-10-31 6:43 ` Leo Liang
2023-10-31 7:55 ` Xiang W
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=ZT9oZ7rf1GiWeP9j@swlinux02 \
--to=ycliang@andestech.com \
--cc=apatel@ventanamicro.com \
--cc=chanho61.park@samsung.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=kconsul@ventanamicro.com \
--cc=rick@andestech.com \
--cc=sughosh.ganu@linaro.org \
--cc=u-boot@lists.denx.de \
/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