From: <conor.dooley@microchip.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<linux-riscv@lists.infradead.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [v2] Add support for hwrng on PolarFire SoC
Date: Fri, 8 Apr 2022 10:09:11 +0000 [thread overview]
Message-ID: <20220408100911.1638478-1-conor.dooley@microchip.com> (raw)
From: Conor Dooley <conor.dooley@microchip.com>
As it says on the tin, add support for the hardware rng on PolarFire
SoC, which is accessed via the system controller.
I dropped the maintainers entry change that v1 had, I will send a
single update via RISCV to avoid any conflicts.
On v1 I replied saying there was a refcount issue, but that's not
actually the case, so no changes required there.
Thanks,
Conor
Changes since v1:
- Rebased on v5.18-rc1
- Dropped the MAINTAINERS change
- Added quality estimation
Conor Dooley (1):
hwrng: mpfs - add polarfire soc hwrng support
drivers/char/hw_random/Kconfig | 13 ++++
drivers/char/hw_random/Makefile | 1 +
drivers/char/hw_random/mpfs-rng.c | 104 ++++++++++++++++++++++++++++++
3 files changed, 118 insertions(+)
create mode 100644 drivers/char/hw_random/mpfs-rng.c
--
2.35.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-04-08 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 10:09 conor.dooley [this message]
2022-04-08 10:09 ` [PATCH v2 1/1] hwrng: mpfs - add polarfire soc hwrng support conor.dooley
2022-04-15 8:37 ` hwrng: mpfs - Enable COMPILE_TEST Herbert Xu
2022-04-15 10:18 ` Conor.Dooley
2022-04-15 10:20 ` Conor.Dooley
2022-04-15 8:40 ` [PATCH v2 1/1] hwrng: mpfs - add polarfire soc hwrng support 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=20220408100911.1638478-1-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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