From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
herbert@gondor.apana.org.au, davem@davemloft.net,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_mmanikan@quicinc.com, quic_srichara@quicinc.com,
quic_varada@quicinc.com
Subject: Re: [PATCH v2 3/4] arm64: dts: qcom: ipq9574: update TRNG compatible
Date: Fri, 20 Dec 2024 10:46:11 +0100 [thread overview]
Message-ID: <49cccc44-09d5-4756-aaa0-1c8cef473c82@oss.qualcomm.com> (raw)
In-Reply-To: <20241220070036.3434658-4-quic_mdalam@quicinc.com>
On 20.12.2024 8:00 AM, Md Sadre Alam wrote:
> RNG hardware versions greater than 3.0 are Truly Random Number
> Generators (TRNG). In IPQ9574, the RNGblock is a TRNG.
>
> This patch corrects the compatible property which correctly describes
> the hardware without making any functional changes
>
> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2024-12-20 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 7:00 [PATCH v2 0/4] Enable TRNG support Md Sadre Alam
2024-12-20 7:00 ` [PATCH v2 1/4] dt-bindings: crypto: qcom,prng: document ipq9574, ipq5424 and ipq5322 Md Sadre Alam
2024-12-24 9:42 ` Krzysztof Kozlowski
2024-12-26 5:08 ` Md Sadre Alam
2024-12-20 7:00 ` [PATCH v2 2/4] arm64: dts: qcom: ipq5424: add TRNG node Md Sadre Alam
2024-12-20 7:00 ` [PATCH v2 3/4] arm64: dts: qcom: ipq9574: update TRNG compatible Md Sadre Alam
2024-12-20 9:46 ` Konrad Dybcio [this message]
2024-12-20 7:00 ` [PATCH v2 4/4] arm64: dts: qcom: ipq5332: " Md Sadre Alam
2024-12-20 9:46 ` Konrad Dybcio
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=49cccc44-09d5-4756-aaa0-1c8cef473c82@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=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=quic_mdalam@quicinc.com \
--cc=quic_mmanikan@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--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 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®