From: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>
To: Harshal Dev <harshal.dev@oss.qualcomm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add TRNG node for x1e80100 SoC
Date: Tue, 9 Dec 2025 15:17:04 +0800 [thread overview]
Message-ID: <9a8a4774-1a04-405d-8022-73ef3e28bb71@oss.qualcomm.com> (raw)
In-Reply-To: <20251124-trng_dt_binding_x1e80100-v1-0-b4eafa0f1077@oss.qualcomm.com>
On 11/25/2025 1:08 AM, Harshal Dev wrote:
> Add device-tree nodes to enable TRNG for x1e80100 SoC
>
> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
> ---
> Harshal Dev (2):
> dt-bindings: crypto: qcom,prng: document x1e80100
> arm64: dts: qcom: x1e80100: add TRNG node
>
> Documentation/devicetree/bindings/crypto/qcom,prng.yaml | 1 +
> arch/arm64/boot/dts/qcom/x1e80100.dtsi | 5 +++++
> 2 files changed, 6 insertions(+)
> ---
> base-commit: d13f3ac64efb868d09cb2726b1e84929afe90235
> change-id: 20251124-trng_dt_binding_x1e80100-94ec1f83142b
>
> Best regards,
Tested-by: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com> # on x1e80100
root@ubuntu:/usr/Testools# cat /sys/class/misc/hw_random/rng_available
smccc_trng qcom_hwrng
root@ubuntu:/usr/Testools# cat /sys/class/misc/hw_random/rng_current
smccc_trng
root@ubuntu:/usr/Testools# echo qcom_hwrng > /sys/class/misc/hw_random/rng_current
root@ubuntu:/usr/Testools# cat /sys/class/misc/hw_random/rng_current
qcom_hwrng
root@ubuntu:/usr/Testools# cat /dev/random | rngtest -c 1000
rngtest 6.15
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
rngtest: starting FIPS tests...
rngtest: bits received from input: 20000032
rngtest: FIPS 140-2 successes: 1000
rngtest: FIPS 140-2 failures: 0
rngtest: FIPS 140-2(2001-10-10) Monobit: 0
rngtest: FIPS 140-2(2001-10-10) Poker: 0
rngtest: FIPS 140-2(2001-10-10) Runs: 0
rngtest: FIPS 140-2(2001-10-10) Long run: 0
rngtest: FIPS 140-2(2001-10-10) Continuous run: 0
rngtest: input channel speed: (min=2.328; avg=12.908; max=9.313)Gibits/s
rngtest: FIPS tests speed: (min=123.854; avg=204.373; max=254.313)Mibits/s
rngtest: Program run time: 94908 microseconds
Regards,
Wenjia
prev parent reply other threads:[~2025-12-09 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 17:08 Harshal Dev
2025-11-24 17:08 ` [PATCH 1/2] dt-bindings: crypto: qcom,prng: document x1e80100 Harshal Dev
2025-11-24 21:19 ` Krzysztof Kozlowski
2025-11-24 17:08 ` [PATCH 2/2] arm64: dts: qcom: x1e80100: add TRNG node Harshal Dev
2025-11-26 1:36 ` Dmitry Baryshkov
2025-12-09 7:17 ` Wenjia Zhang [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=9a8a4774-1a04-405d-8022-73ef3e28bb71@oss.qualcomm.com \
--to=wenjia.zhang@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=harshal.dev@oss.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®