From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Khalid Faisal Ansari <khalid.ansari@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 v3] arm64: dts: qcom: hamoa-iot-evk: Enable TPM (ST33) on SPI11
Date: Wed, 12 Nov 2025 12:09:26 +0100 [thread overview]
Message-ID: <dc500814-3b1d-4cf9-8f73-6fd71ddac28f@oss.qualcomm.com> (raw)
In-Reply-To: <55eb7543-7b88-42e2-bb11-7c54c4e59801@oss.qualcomm.com>
On 11/12/25 10:28 AM, Konrad Dybcio wrote:
> On 11/12/25 8:42 AM, Khalid Faisal Ansari wrote:
>> Enable ST33HTPM TPM over SPI11 on the Hamoa IoT EVK by adding the
>> required SPI and TPM nodes.
>>
>> Signed-off-by: Khalid Faisal Ansari <khalid.ansari@oss.qualcomm.com>
>> ---
>> Testing:
>> - TPM detected via tpm_tis_spi
>> - Verified functionality using tpm2-tools (e.g. tpm2_getrandom, tpm2_rsadecrypt)
>>
>> Depends on:
>> - <20251106102448.3585332-1-xueyao.an@oss.qualcomm.com>
>> Link: https://lore.kernel.org/linux-arm-msm/20251106102448.3585332-1-xueyao.an@oss.qualcomm.com/
>> ---
>> Changes in v3:
>> - Squashed patches touching the same file into one.
>
> Doesn't seem to be the case
The author was referring to a faulty previous revision, not my
suggestion of coupling this with the dependency
for this change:
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2025-11-12 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 7:42 [PATCH v3] arm64: dts: qcom: hamoa-iot-evk: Enable TPM (ST33) on SPI11 Khalid Faisal Ansari
2025-11-12 9:28 ` Konrad Dybcio
2025-11-12 11:09 ` Konrad Dybcio [this message]
2025-12-10 9:28 ` Khalid Faisal Ansari
2026-01-07 10:26 ` Khalid Faisal Ansari
2026-01-10 19:11 ` Bjorn Andersson
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=dc500814-3b1d-4cf9-8f73-6fd71ddac28f@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khalid.ansari@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