devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Gatien Chevallier <gatien.chevallier@foss.st.com>,
	Olivia Mackall <olivia@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Lionel Debieve <lionel.debieve@foss.st.com>,
	<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>
Subject: Re: [PATCH v3 0/9] hwrng: stm32: support STM32MP13x platforms
Date: Mon, 9 Oct 2023 14:02:10 +0200	[thread overview]
Message-ID: <5bd1a669-9eab-717f-6f58-0ecb4587cf22@foss.st.com> (raw)
In-Reply-To: <20230921080301.253563-1-gatien.chevallier@foss.st.com>

Hi

On 9/21/23 10:02, Gatien Chevallier wrote:
> The STM32MP13x platforms have a RNG hardware block that supports
> customization, a conditional reset sequences that allows to
> recover from certain situations and a configuration locking
> mechanism.
> 
> This series adds support for the mentionned features. Note that
> the hardware RNG can and should be managed in the secure world
> for this platform, hence the rng not being default enabled on
> the STM32MP135F-DK board.
> 
> Changes in V2:
> 	- Use pm_ptr() and add __maybe_unused on PM API
> 	- Correct bug using WARN_ON
> 
> Changes in V3:
> 	- Squash of bindings patches
> 	- st,rng-lock-conf property declaration rework
> 	- Fix stm32_rng_pm_ops declaration in patch [5/9]
> 
> Gatien Chevallier (9):
>    dt-bindings: rng: introduce new compatible for STM32MP13x
>    hwrng: stm32 - use devm_platform_get_and_ioremap_resource() API
>    hwrng: stm32 - implement STM32MP13x support
>    hwrng: stm32 - implement error concealment
>    hwrng: stm32 - rework error handling in stm32_rng_read()
>    hwrng: stm32 - restrain RNG noise source clock
>    hwrng: stm32 - support RNG configuration locking mechanism
>    hwrng: stm32 - rework power management sequences
>    ARM: dts: stm32: add RNG node for STM32MP13x platforms
> 
>   .../devicetree/bindings/rng/st,stm32-rng.yaml |  20 +-
>   arch/arm/boot/dts/st/stm32mp131.dtsi          |   8 +
>   drivers/char/hw_random/stm32-rng.c            | 511 +++++++++++++++---
>   3 files changed, 455 insertions(+), 84 deletions(-)
> 

Patch[9] applied on stm32-next.

thanks
alex

      parent reply	other threads:[~2023-10-09 12:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  8:02 [PATCH v3 0/9] hwrng: stm32: support STM32MP13x platforms Gatien Chevallier
2023-09-21  8:02 ` [PATCH v3 1/9] dt-bindings: rng: introduce new compatible for STM32MP13x Gatien Chevallier
2023-09-22 20:49   ` Rob Herring
2023-09-21  8:02 ` [PATCH v3 2/9] hwrng: stm32 - use devm_platform_get_and_ioremap_resource() API Gatien Chevallier
2023-09-21  8:02 ` [PATCH v3 3/9] hwrng: stm32 - implement STM32MP13x support Gatien Chevallier
2023-09-21  8:02 ` [PATCH v3 4/9] hwrng: stm32 - implement error concealment Gatien Chevallier
2023-09-21  8:02 ` [PATCH v3 5/9] hwrng: stm32 - rework error handling in stm32_rng_read() Gatien Chevallier
2023-09-21  8:02 ` [PATCH v3 6/9] hwrng: stm32 - restrain RNG noise source clock Gatien Chevallier
2023-09-21  8:02 ` [PATCH v3 7/9] hwrng: stm32 - support RNG configuration locking mechanism Gatien Chevallier
2023-09-21  8:03 ` [PATCH v3 8/9] hwrng: stm32 - rework power management sequences Gatien Chevallier
2023-09-21  8:03 ` [PATCH v3 9/9] ARM: dts: stm32: add RNG node for STM32MP13x platforms Gatien Chevallier
2023-09-22  8:20   ` [EXTERNAL] " Kamlesh Gurudasani
2023-09-25  9:31     ` Gatien CHEVALLIER
2023-10-01  8:33 ` [PATCH v3 0/9] hwrng: stm32: support " Herbert Xu
2023-10-09 12:02 ` Alexandre TORGUE [this message]

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=5bd1a669-9eab-717f-6f58-0ecb4587cf22@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gatien.chevallier@foss.st.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=krzysztof.kozlowski+dt@linaro.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=mcoquelin.stm32@gmail.com \
    --cc=olivia@selenic.com \
    --cc=robh+dt@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).