From: Daniel Golle <daniel@makrotopia.org>
To: "Daniel Golle" <daniel@makrotopia.org>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Olivia Mackall" <olivia@selenic.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Uwe Kleine-König" <ukleinek@debian.org>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Anand Moon" <linux.amoon@gmail.com>,
"Dragan Simic" <dsimic@manjaro.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Martin Kaiser" <martin@kaiser.cx>,
"Ard Biesheuvel" <ardb@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] hwrng: add hwrng support for Rockchip RK3568
Date: Fri, 21 Jun 2024 02:24:17 +0100 [thread overview]
Message-ID: <cover.1718921174.git.daniel@makrotopia.org> (raw)
Rockchip SoCs used to have a random number generator as part of their
crypto device, and support for it has to be added to the corresponding
driver.
However newer Rockchip SoCs like the RK3568 have an independent True
Random Number Generator device. This patchset adds a driver for it and
enable it in the device tree.
v2 of this patchset has been submitted by Aurelien Jarno in November
2022. A follow-up submission addressing the comments received for v2
never happened.
As I believe that using the TRNG is generally desireable as it reduces
the time needed to boot significantly as userspace no longer waits due
blocking read of /dev/random while still lacking entropy I have picked
up Aurelien's previous work and completed it.
Link to v2: https://patchwork.kernel.org/project/linux-arm-kernel/cover/20221128184718.1963353-1-aurelien@aurel32.net/
v2 -> v3:
* Patch 1: address comments of Krzysztof Kozlowski, add MAINTAINERS
- improved description
- meaningful clock-names
- add entry in MAINTAINERS files
* Patch 2: numerous code-style improvements
- drop misleading rk_rng_write_ctl(), simplify I/O writes
- drop unused TRNG_RNG_DOUT_[1-7] macros
- handle error handling for pm_runtime_get_sync()
- use memcpy_fromio() instead of open coding for-loop
- some minor white-spaces fixes
* Patch 3:
- use clock-names as defined in dt-bindings
v1 -> v2:
* Patch 1: fix issues reported by Rob Herring and Krzysztof Kozlowski:
- Rename rockchip-rng.yaml into rockchip,rk3568-rng.yaml
- Fix binding title and description
- Fix compatible property
- Rename clocks and add the corresponding descriptions
- Drop reset-names
- Add a bus definition with #address-cells and #size-cells to the
example.
* Patch 2: fix issue reported by kernel test robot <lkp@intel.com>
- Do not read the random registers as big endian, looking at the
RK3568 TRM this is actually not needed. This fixes a sparse
warning.
* Patch 3: unchanged
Aurelien Jarno (3):
dt-bindings: RNG: Add Rockchip RNG bindings
hwrng: add Rockchip SoC hwrng driver
arm64: dts: rockchip: add DT entry for RNG to RK356x
.../bindings/rng/rockchip,rk3568-rng.yaml | 60 +++++
MAINTAINERS | 7 +
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 9 +
drivers/char/hw_random/Kconfig | 14 ++
drivers/char/hw_random/Makefile | 1 +
drivers/char/hw_random/rockchip-rng.c | 229 ++++++++++++++++++
6 files changed, 320 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rng/rockchip,rk3568-rng.yaml
create mode 100644 drivers/char/hw_random/rockchip-rng.c
--
2.45.2
next reply other threads:[~2024-06-21 1:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 1:24 Daniel Golle [this message]
2024-06-21 1:25 ` [PATCH v3 1/3] dt-bindings: RNG: Add Rockchip RNG bindings Daniel Golle
2024-06-21 9:12 ` Diederik de Haas
2024-06-21 9:39 ` Diederik de Haas
2024-06-21 9:52 ` Krzysztof Kozlowski
2024-06-21 1:25 ` [PATCH v3 2/3] hwrng: add Rockchip SoC hwrng driver Daniel Golle
2024-06-21 9:32 ` Diederik de Haas
2024-06-21 9:57 ` Krzysztof Kozlowski
2024-06-21 10:18 ` Chen-Yu Tsai
2024-06-21 18:13 ` Dragan Simic
2024-06-21 22:16 ` Uwe Kleine-König
2024-06-22 10:29 ` Dragan Simic
2024-06-22 20:26 ` Heiko Stübner
2024-06-22 20:45 ` Dragan Simic
2024-06-23 0:20 ` Uwe Kleine-König
2024-06-23 5:41 ` Dragan Simic
2024-06-22 18:05 ` Krzysztof Kozlowski
2024-06-22 19:10 ` Dragan Simic
2024-06-21 10:04 ` Chen-Yu Tsai
2024-06-21 11:41 ` Philipp Zabel
2024-06-21 1:25 ` [PATCH v3 3/3] arm64: dts: rockchip: add DT entry for RNG to RK356x Daniel Golle
2024-06-21 9:36 ` Diederik de Haas
2024-06-21 9:49 ` Heiko Stübner
2024-06-22 9:58 ` [PATCH v3 0/3] hwrng: add hwrng support for Rockchip RK3568 Aurelien Jarno
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=cover.1718921174.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=ardb@kernel.org \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux.amoon@gmail.com \
--cc=martin@kaiser.cx \
--cc=olivia@selenic.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
--cc=ukleinek@debian.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).