Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Khalid Faisal Ansari <khalid.ansari@oss.qualcomm.com>,
	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] arm64: dts: qcom: shikra: Enable dTPM on EVK boards
Date: Tue, 25 Aug 2026 15:33:14 +0200	[thread overview]
Message-ID: <c4bf7a4b-48a9-4bfb-b133-858189627639@kernel.org> (raw)
In-Reply-To: <e4058fd8-23e8-4031-906d-7ff4ec525508@oss.qualcomm.com>

On 25/08/2026 12:06, Khalid Faisal Ansari wrote:
> 
> On 8/20/2026 2:52 PM, Konrad Dybcio wrote:
>> On 8/20/26 11:16 AM, Khalid Faisal Ansari wrote:
>>> The Shikra EVK boards (CQM, CQS, IQS) carry an ST33 discrete TPM
>>> connected via SPI5. Enable the SPI controller and add the TPM node
>>> with the ST33HTPM compatible and a 20 MHz max clock.
>>>
>>> Depends-on:https://lore.kernel.org/all/20260820085347.822-1-xueyao.an@oss.qualcomm.com/
>> This is not a valid tag to put in the commit message
>>
>> Why haven't you sent the two clearly interdependent patches together?
> 
> I referenced the SPI5 enabling patch because the TPM node addition 
> depends on that change being present. I had followed a similar approach 
> used in an earlier submission 
> (https://lore.kernel.org/all/0afa55d5-20bf-487b-abe0-4e2126ccf453@oss.qualcomm.com/), 
> where the dependency was mentioned in the commit message.
> 
> Since the two changes originate from different internal ownership areas 
> but are functionally interdependent, we have been handling them as 
> separate submissions while documenting the dependency between them.

You have been already told TWICE and you keep arguing.

> 
>>> Signed-off-by: Khalid Faisal Ansari<khalid.ansari@oss.qualcomm.com>
>>> ---
>>> The Shikra EVK boards (CQM, CQS, IQS) have an ST33 discrete TPM (dTPM)
>>> connected over SPI5. Enable the SPI controller and add the TPM node for
>>> all three board variants.
>>>
>>> This series depends on the SPI5 node addition in shikra-evk.dtsi:
>>>    https://lore.kernel.org/all/20260820085347.822-1-xueyao.an@oss.qualcomm.com/
>>> ---
>>>   arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts | 10 ++++++++++
>>>   arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts | 10 ++++++++++
>>>   arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts | 10 ++++++++++
>> Turn this into a single addition to shikra-evk.dtsi
> 
> I intentionally kept the changes in the individual board DTS files 
> rather than placing them in shikra-evk.dtsi. While the current EVK 
> variants (CQM, CQS, and IQS) all carry the ST33 dTPM, a future board 
> could potentially reuse shikra-evk.dtsi without supporting the TPM 
> hardware. Keeping the node in the board-specific DTS files makes the 
> hardware dependency explicit and avoids enabling TPM on boards where it 
> may not be present.

Do not paste us LLM answers, I find it disrespectful in regard to my time.

Which future board could reuse shikra-evk.dtsi? This the DTSI FOR THIS
EVK. Not some future boards.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-08-25 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  9:16 [PATCH] arm64: dts: qcom: shikra: Enable dTPM on EVK boards Khalid Faisal Ansari
2026-08-20  9:22 ` Konrad Dybcio
2026-08-25 10:12   ` Khalid Faisal Ansari
2026-08-25 10:35   ` Khalid Faisal Ansari
     [not found]   ` <e4058fd8-23e8-4031-906d-7ff4ec525508@oss.qualcomm.com>
2026-08-25 13:33     ` Krzysztof Kozlowski [this message]
2026-08-20  9:31 ` Abel Vesa

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=c4bf7a4b-48a9-4bfb-b133-858189627639@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khalid.ansari@oss.qualcomm.com \
    --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