From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Om Prakash Singh <quic_omprsing@quicinc.com>
Cc: andersson@kernel.org, conor+dt@kernel.org, davem@davemloft.net,
devicetree@vger.kernel.org, herbert@gondor.apana.org.au,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, marijn.suijten@somainline.org,
robh+dt@kernel.org, vkoul@kernel.org,
Harshal Dev <harshal.dev@oss.qualcomm.com>
Subject: Re: [PATCH 1/3] dt-bindings: crypto: qcom,prng: Add SM8450
Date: Tue, 20 Jan 2026 11:41:13 +0100 [thread overview]
Message-ID: <947f59dc-4eda-406c-a82d-6b16fbbc9077@oss.qualcomm.com> (raw)
In-Reply-To: <20230818161720.3644424-1-quic_omprsing@quicinc.com>
On 8/18/23 6:17 PM, Om Prakash Singh wrote:
> Instead of having SoC name "qcom,sm8450-prng-ee" we could use "qcom,rng-ee" as
> new IP core is not longer pseudo random number generator. so "prng" can be
> changed to "rng". Clock configuration is not needed on sm8550 as well. So it is
> better to use generic compatible string.
(updated the email addresses of various recipients)
Sorry for digging out this old thread, but I can't seem to find
supporting evidence for this, at least described in a in-your-face
way..
Can we determine whether the RNG generates pseudo-random numbers based
on a version number, or some other register? Would RNGv3.0 be a good
check?
I see that today we describe kodiak and talos marked as having a TRNG,
but they're much much older than 8450..
Konrad
next prev parent reply other threads:[~2026-01-20 10:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 20:50 [PATCH 0/3] Introduce PRNG on SM8450 Konrad Dybcio
2023-08-11 20:50 ` [PATCH 1/3] dt-bindings: crypto: qcom,prng: Add SM8450 Konrad Dybcio
2023-08-13 9:48 ` Conor Dooley
2023-08-18 16:17 ` Om Prakash Singh
2023-08-19 7:45 ` Krzysztof Kozlowski
2023-08-21 0:52 ` Om Prakash Singh
2023-08-21 6:07 ` Krzysztof Kozlowski
2023-08-22 4:27 ` Om Prakash Singh
2026-01-20 10:41 ` Konrad Dybcio [this message]
2023-08-11 20:50 ` [PATCH 2/3] crypto: qcom-rng: Make the core clock optional regardless of ACPI presence Konrad Dybcio
2023-08-14 2:39 ` Bjorn Andersson
2023-08-11 20:50 ` [PATCH 3/3] arm64: dts: qcom: sm8450: Add PRNG Konrad Dybcio
2023-08-14 3:27 ` (subset) [PATCH 0/3] Introduce PRNG on SM8450 Bjorn Andersson
2023-08-18 10:26 ` Herbert Xu
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=947f59dc-4eda-406c-a82d-6b16fbbc9077@oss.qualcomm.com \
--to=konrad.dybcio@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=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_omprsing@quicinc.com \
--cc=robh+dt@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®