From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To: Md Sadre Alam <quic_mdalam@quicinc.com>, <andersson@kernel.org>,
<konradybcio@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <quic_srichara@quicinc.com>, <quic_varada@quicinc.com>
Subject: Re: [PATCH 0/3] Enable TRNG support
Date: Fri, 6 Dec 2024 12:59:08 +0530 [thread overview]
Message-ID: <11d49831-8d20-45ee-94ae-38248340fa1f@quicinc.com> (raw)
In-Reply-To: <20241206072057.1508459-1-quic_mdalam@quicinc.com>
On 12/6/2024 12:50 PM, Md Sadre Alam wrote:
> This patch series enables support for Truly Random Number
> Generators (TRNG) across various targets, including IPQ95xx,
> IPQ32xx, and IPQ54xx.
>
It should be IPQ53xx, not IPQ32xx.
--Manikanta.
> Md Sadre Alam (3):
> arm64: dts: qcom: ipq5424: Add TRNG node
> arm64: dts: qcom: ipq9574: Enable TRNG instead PRNG
> arm64: dts: qcom: ipq5332: Enable TRNG instead of PRNG
>
> arch/arm64/boot/dts/qcom/ipq5332.dtsi | 2 +-
> arch/arm64/boot/dts/qcom/ipq5424.dtsi | 7 +++++++
> arch/arm64/boot/dts/qcom/ipq9574.dtsi | 2 +-
> 3 files changed, 9 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2024-12-06 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 7:20 Md Sadre Alam
2024-12-06 7:20 ` [PATCH 1/3] arm64: dts: qcom: ipq5424: Add TRNG node Md Sadre Alam
2024-12-12 23:56 ` Konrad Dybcio
2024-12-06 7:20 ` [PATCH 2/3] arm64: dts: qcom: ipq9574: Enable TRNG instead PRNG Md Sadre Alam
2024-12-12 23:55 ` Konrad Dybcio
2024-12-13 8:44 ` Md Sadre Alam
2024-12-06 7:20 ` [PATCH 3/3] arm64: dts: qcom: ipq5332: Enable TRNG instead of PRNG Md Sadre Alam
2024-12-06 7:29 ` Manikanta Mylavarapu [this message]
2024-12-09 5:32 ` [PATCH 0/3] Enable TRNG support Md Sadre Alam
2024-12-13 8:46 ` Md Sadre Alam
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=11d49831-8d20-45ee-94ae-38248340fa1f@quicinc.com \
--to=quic_mmanikan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mdalam@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®