[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <947f59dc-4eda-406c-a82d-6b16fbbc9077@oss.qualcomm.com>
Date: Tue, 20 Jan 2026 11:41:13 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Om Prakash Singh <quic_omprsing@...cinc.com>
Cc: andersson@...nel.org, conor+dt@...nel.org, davem@...emloft.net,
devicetree@...r.kernel.org, herbert@...dor.apana.org.au,
Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>,
linux-arm-msm@...r.kernel.org, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, marijn.suijten@...ainline.org,
robh+dt@...nel.org, vkoul@...nel.org,
Harshal Dev <harshal.dev@....qualcomm.com>
Subject: Re: [PATCH 1/3] dt-bindings: crypto: qcom,prng: Add SM8450
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
Powered by blists - more mailing lists