From: Gatien Chevallier <gatien.chevallier@foss.st.com>
To: 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>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Lionel Debieve <lionel.debieve@foss.st.com>, <marex@denx.de>
Cc: <linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Gatien Chevallier <gatien.chevallier@foss.st.com>
Subject: [PATCH v3 0/4] Add support for stm32mp25x RNG
Date: Tue, 15 Oct 2024 18:48:53 +0200 [thread overview]
Message-ID: <20241015-rng-mp25-v2-v3-0-87630d73e5eb@foss.st.com> (raw)
This patchset adds support for the Random Number
Generator(RNG) present on the stm32mp25x platforms.
On these platforms, the clock management and the RNG
parameters are different.
While there, update the RNG max clock frequency on
stm32mp15 platforms according to the latest specs.
Tested on the stm32mp257f-ev1 platform with a deep
power sequence with rngtest before/after the sequence with
satisfying results.
Same was done on stm32mp135f-dk to make sure no regression was added.
On stm32mp157c-dk2, I didn't perform a power sequence but the rngtest
results were satisfying.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
---
Changes in v3:
- Add restriction on clock-names some compatibles
- Use clk_bulk APIs in the RNG driver to avoid manually handling clocks.
- Link to v2: https://lore.kernel.org/r/20241011-rng-mp25-v2-v2-0-76fd6170280c@foss.st.com
Changes in V2:
-Fixes in bindings
-Removed MP25 RNG example
-Renamed RNG clocks for mp25 to "core" and "bus"
---
Gatien Chevallier (4):
dt-bindings: rng: add st,stm32mp25-rng support
hwrng: stm32 - implement support for STM32MP25x platforms
hwrng: stm32 - update STM32MP15 RNG max clock frequency
arm64: dts: st: add RNG node on stm32mp251
.../devicetree/bindings/rng/st,stm32-rng.yaml | 34 +++++++++-
arch/arm64/boot/dts/st/stm32mp251.dtsi | 10 +++
drivers/char/hw_random/stm32-rng.c | 76 ++++++++++++++++------
3 files changed, 100 insertions(+), 20 deletions(-)
---
base-commit: 8e929cb546ee42c9a61d24fae60605e9e3192354
change-id: 20241011-rng-mp25-v2-b6460ef11e1f
Best regards,
--
Gatien Chevallier <gatien.chevallier@foss.st.com>
next reply other threads:[~2024-10-15 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 16:48 Gatien Chevallier [this message]
2024-10-15 16:48 ` [PATCH v3 1/4] dt-bindings: rng: add st,stm32mp25-rng support Gatien Chevallier
2024-10-15 22:17 ` Rob Herring
2024-10-16 7:49 ` Gatien CHEVALLIER
2024-10-16 8:00 ` Gatien CHEVALLIER
2024-10-15 16:48 ` [PATCH v3 2/4] hwrng: stm32 - implement support for STM32MP25x platforms Gatien Chevallier
2024-10-15 16:57 ` Marek Vasut
2024-10-15 16:48 ` [PATCH v3 3/4] hwrng: stm32 - update STM32MP15 RNG max clock frequency Gatien Chevallier
2024-10-15 16:48 ` [PATCH v3 4/4] arm64: dts: st: add RNG node on stm32mp251 Gatien Chevallier
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=20241015-rng-mp25-v2-v3-0-87630d73e5eb@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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-stm32@st-md-mailman.stormreply.com \
--cc=lionel.debieve@foss.st.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivia@selenic.com \
--cc=robh@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).