From: Conor Dooley <conor@kernel.org>
To: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Daniel Golle <daniel@makrotopia.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 2/7] dt-bindings: rng: add binding for Rockchip RK3588 RNG
Date: Thu, 30 Jan 2025 18:42:09 +0000 [thread overview]
Message-ID: <20250130-anything-scholar-01f4c9145893@spud> (raw)
In-Reply-To: <20250130-rk3588-trng-submission-v1-2-97ff76568e49@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 3961 bytes --]
On Thu, Jan 30, 2025 at 05:31:16PM +0100, Nicolas Frattaroli wrote:
> The Rockchip RK3588 SoC has two hardware RNGs accessible to the
> non-secure world: an RNG in the Crypto IP, and a standalone RNG that is
> new to this SoC.
>
> Add a binding for this new standalone RNG.
>
> The RNG is capable of firing an interrupt when entropy is ready, but
> all known driver implementations choose to poll instead for performance
> reasons. Hence, make the interrupt optional, as it may disappear in
> future hardware revisions entirely and certainly isn't needed for the
> hardware to function.
>
> The reset is optional as well, as the RNG functions without an explicit
> reset. Rockchip's downstream driver does not use the reset at all,
> indicating that their engineers have deemed it unnecessary.
>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> ---
> .../bindings/rng/rockchip,rk3588-rng.yaml | 61 ++++++++++++++++++++++
> MAINTAINERS | 2 +
> 2 files changed, 63 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/rng/rockchip,rk3588-rng.yaml b/Documentation/devicetree/bindings/rng/rockchip,rk3588-rng.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..dff843fa4bf9d5704bbcd106398328588d80b02d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rng/rockchip,rk3588-rng.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/rng/rockchip,rk3588-rng.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Rockchip RK3588 TRNG
> +
> +description: True Random Number Generator on Rockchip RK3588 SoC
> +
> +maintainers:
> + - Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> +
> +properties:
> + compatible:
> + enum:
> + - rockchip,rk3588-rng
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: TRNG AHB clock
> +
> + # Optional, not used by some driver implementations
> + interrupts:
> + maxItems: 1
> +
> + # Optional, hardware works without explicit reset
These sorts of comments are not needed, "required" conveys this
information.
> + resets:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/rockchip,rk3588-cru.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/reset/rockchip,rk3588-cru.h>
> + bus {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + rng@fe378000 {
> + compatible = "rockchip,rk3588-rng";
> + reg = <0x0 0xfe378000 0x0 0x200>;
> + interrupts = <GIC_SPI 400 IRQ_TYPE_LEVEL_HIGH 0>;
> + clocks = <&scmi_clk SCMI_HCLK_SECURE_NS>;
> + resets = <&scmi_reset SCMI_SRST_H_TRNG_NS>;
> + status = "disabled";
> + };
> + };
> +
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index bc8ce7af3303f747e0ef028e5a7b29b0bbba99f4..7daf9bfeb0cb4e9e594b809012c7aa243b0558ae 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -20420,8 +20420,10 @@ F: include/uapi/linux/rkisp1-config.h
> ROCKCHIP RK3568 RANDOM NUMBER GENERATOR SUPPORT
> M: Daniel Golle <daniel@makrotopia.org>
> M: Aurelien Jarno <aurelien@aurel32.net>
> +M: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
^^
tbh, not really sure this part of the change should be in this patch
> S: Maintained
> F: Documentation/devicetree/bindings/rng/rockchip,rk3568-rng.yaml
> +F: Documentation/devicetree/bindings/rng/rockchip,rk3588-rng.yaml
> F: drivers/char/hw_random/rockchip-rng.c
>
> ROCKCHIP RASTER 2D GRAPHIC ACCELERATION UNIT DRIVER
>
> --
> 2.48.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-01-30 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 16:31 [PATCH 0/7] RK3588 Hardware Random Number Generator Driver Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 1/7] dt-bindings: reset: Add SCMI reset IDs for RK3588 Nicolas Frattaroli
2025-01-30 18:46 ` Conor Dooley
2025-01-30 16:31 ` [PATCH 2/7] dt-bindings: rng: add binding for Rockchip RK3588 RNG Nicolas Frattaroli
2025-01-30 18:42 ` Conor Dooley [this message]
2025-01-31 8:30 ` Krzysztof Kozlowski
2025-01-31 9:43 ` Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 3/7] hwrng: rockchip: store dev pointer in driver struct Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 4/7] hwrng: rockchip: eliminate some unnecessary dereferences Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 5/7] hwrng: rockchip: add support for rk3588's standalone TRNG Nicolas Frattaroli
2025-01-31 8:34 ` Krzysztof Kozlowski
2025-01-30 16:31 ` [PATCH 6/7] arm64: dts: rockchip: Add rng node to RK3588 Nicolas Frattaroli
2025-01-31 10:16 ` Krzysztof Kozlowski
2025-01-30 16:31 ` [PATCH 7/7] mailmap: add entry for Nicolas Frattaroli Nicolas Frattaroli
2025-01-31 8:36 ` Krzysztof Kozlowski
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=20250130-anything-scholar-01f4c9145893@spud \
--to=conor@kernel.org \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.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=nicolas.frattaroli@collabora.com \
--cc=olivia@selenic.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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