From: "lianfeng.ouyang" <lianfeng.ouyang@starfivetech.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>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 1/2] dt-bindings: Add bindings for StarFive JHB100 SoC trng controller.
Date: Tue, 12 May 2026 14:24:03 +0800 [thread overview]
Message-ID: <20260512062404.4540-2-lianfeng.ouyang@starfivetech.com> (raw)
In-Reply-To: <20260512062404.4540-1-lianfeng.ouyang@starfivetech.com>
From: Lianfeng Ouyang <lianfeng.ouyang@starfivetech.com>
Signed-off-by: Lianfeng Ouyang <lianfeng.ouyang@starfivetech.com>
---
Documentation/devicetree/bindings/rng/starfive,jh7110-trng.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/rng/starfive,jh7110-trng.yaml b/Documentation/devicetree/bindings/rng/starfive,jh7110-trng.yaml
index 4639247e9e51..11346d77b2f6 100644
--- a/Documentation/devicetree/bindings/rng/starfive,jh7110-trng.yaml
+++ b/Documentation/devicetree/bindings/rng/starfive,jh7110-trng.yaml
@@ -13,8 +13,8 @@ properties:
compatible:
oneOf:
- items:
- - const: starfive,jh8100-trng
- const: starfive,jh7110-trng
+ - const: starfive,jhb100-trng
- const: starfive,jh7110-trng
reg:
--
2.43.0
next prev parent reply other threads:[~2026-05-12 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 6:24 [PATCH v1 0/2] Add trng driver to JHB100 lianfeng.ouyang
2026-05-12 6:24 ` lianfeng.ouyang [this message]
2026-05-12 17:15 ` [PATCH v1 1/2] dt-bindings: Add bindings for StarFive JHB100 SoC trng controller Conor Dooley
2026-05-12 19:35 ` Conor Dooley
2026-05-14 6:41 ` 回复: " Lianfeng Ouyang
2026-05-13 5:17 ` sashiko-bot
2026-05-12 6:24 ` [PATCH v1 2/2] hwrng: starfive: Update clk and reset sequence lianfeng.ouyang
2026-05-13 5:56 ` sashiko-bot
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=20260512062404.4540-2-lianfeng.ouyang@starfivetech.com \
--to=lianfeng.ouyang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=p.zabel@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.