From: Om Prakash Singh <quic_omprsing@quicinc.com>
To: <quic_omprsing@quicinc.com>
Cc: <neil.armstrong@linaro.org>, <konrad.dybcio@linaro.org>,
<agross@kernel.org>, <andersson@kernel.org>,
<conor+dt@kernel.org>, <davem@davemloft.net>,
<devicetree@vger.kernel.org>, <herbert@gondor.apana.org.au>,
<krzysztof.kozlowski+dt@linaro.org>,
<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>
Subject: [PATCH V1 0/4] Enable TRNG for SA8775P and SC7280
Date: Mon, 16 Oct 2023 01:08:57 +0530 [thread overview]
Message-ID: <20231015193901.2344590-1-quic_omprsing@quicinc.com> (raw)
Add device-tree nodes to enable TRNG for SA8775P and SC7280
*** BLURB HERE ***
Om Prakash Singh (4):
dt-bindings: crypto: qcom,prng: document SA8775P
dt-bindings: crypto: qcom,prng: document SC7280
arm64: dts: qcom: sa8775p: add TRNG node
arm64: dts: qcom: sc7280: add TRNG node
Documentation/devicetree/bindings/crypto/qcom,prng.yaml | 2 ++
arch/arm64/boot/dts/qcom/sa8775p.dtsi | 5 +++++
arch/arm64/boot/dts/qcom/sc7280.dtsi | 5 +++++
3 files changed, 12 insertions(+)
--
2.25.1
next reply other threads:[~2023-10-15 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 19:38 Om Prakash Singh [this message]
2023-10-15 19:38 ` [PATCH V1 1/4] dt-bindings: crypto: qcom,prng: document SA8775P Om Prakash Singh
2023-10-16 2:41 ` Bjorn Andersson
2023-10-15 19:38 ` [PATCH V1 2/4] dt-bindings: crypto: qcom,prng: document SC7280 Om Prakash Singh
2023-10-16 5:23 ` Krzysztof Kozlowski
2023-10-16 5:24 ` Krzysztof Kozlowski
2023-10-15 19:39 ` [PATCH V1 3/4] arm64: dts: qcom: sa8775p: add TRNG node Om Prakash Singh
2023-10-15 19:39 ` [PATCH V1 4/4] arm64: dts: qcom: sc7280: " Om Prakash Singh
2023-10-16 3:32 ` (subset) [PATCH V1 0/4] Enable TRNG for SA8775P and SC7280 Bjorn Andersson
2023-10-17 16:29 ` 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=20231015193901.2344590-1-quic_omprsing@quicinc.com \
--to=quic_omprsing@quicinc.com \
--cc=agross@kernel.org \
--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=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=neil.armstrong@linaro.org \
--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