From: Khalid Faisal Ansari <khalid.ansari@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: shikra: enable ST33 TPM
Date: Wed, 26 Aug 2026 16:59:15 +0530 [thread overview]
Message-ID: <4bb2ff3f-8047-4212-b845-62ba87142a22@oss.qualcomm.com> (raw)
In-Reply-To: <72be72cc-57c0-4b17-ae7d-0b28752bc708@oss.qualcomm.com>
On 8/26/2026 2:41 PM, Konrad Dybcio wrote:
> On 8/25/26 9:13 PM, Khalid Faisal Ansari wrote:
>> Enable ST33HTPM TPM over SPI5 on the Shikra IoT EVK by adding the
>> required SPI and TPM nodes.
>>
>> Signed-off-by: Khalid Faisal Ansari <khalid.ansari@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/shikra-evk.dtsi | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-evk.dtsi b/arch/arm64/boot/dts/qcom/shikra-evk.dtsi
>> index 6eb4184f7642..9f3a880e95e6 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-evk.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/shikra-evk.dtsi
>> @@ -12,3 +12,13 @@ &qupv3_0 {
>> &uart0 {
>> status = "okay";
>> };
>> +
>> +&spi5 {
> Please keep the alphabetical order of node references
Noted. This will be corrected in an upcoming patch.
>
> Konrad
prev parent reply other threads:[~2026-08-26 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 19:13 [PATCH v4 0/2] arm64: dts: qcom: shikra: enable ST33 TPM support Khalid Faisal Ansari
2026-08-25 19:13 ` [PATCH v4 1/2] arm64: dts: qcom: shikra: unreserve GPIOs 14-17 Khalid Faisal Ansari
2026-08-26 9:10 ` Konrad Dybcio
2026-08-26 9:11 ` Konrad Dybcio
2026-08-26 11:12 ` Khalid Faisal Ansari
2026-08-25 19:13 ` [PATCH v4 2/2] arm64: dts: qcom: shikra: enable ST33 TPM Khalid Faisal Ansari
2026-08-26 9:11 ` Konrad Dybcio
2026-08-26 11:29 ` Khalid Faisal Ansari [this message]
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=4bb2ff3f-8047-4212-b845-62ba87142a22@oss.qualcomm.com \
--to=khalid.ansari@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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