The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Sumit Garg <sumit.garg@kernel.org>,
	Jens Wiklander <jens.wiklander@linaro.org>
Cc: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arm64: defconfig: Enable QCOMTEE on Qualcomm SM8650+
Date: Tue, 9 Dec 2025 12:45:58 +0530	[thread overview]
Message-ID: <948b35bc-8479-4d94-a5f7-e8893de8fbf1@oss.qualcomm.com> (raw)
In-Reply-To: <309e0391-58a3-466b-a113-ab864188f6fe@kernel.org>

Hi Krzysztof,

On 12/9/2025 11:28 AM, Krzysztof Kozlowski wrote:
> On 08/12/2025 13:18, Harshal Dev wrote:
>> Enable QCOMTEE driver on Qualcomm SM8650+ SoCs to facilitate communication
>> with the Qualcomm Trusted Execution Environment (QTEE).
>> (No enablement required in DTS files since QCOMTEE device is dynamically
>> registered by the QCOM_SCM firmware driver)
>>
>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>> ---
>> Changes in v3:
>> - Updated the commit message to reflect the supported Qualcomm platforms.
>> - Link to v2: https://lore.kernel.org/r/20251205-qcom_qcomtee_defconfig-v2-1-c92560b0346e@qti.qualcomm.com
>>
> 
> I gave you the exact example to follow. Maybe it is not that important
> for others, so I will not object, but OTOH it is important for me, thus
> I will not give reviewed by. I damn asked VERY CLEARLY:
> 
> "Just mention which UPSTREAM boards (which you called Qualcomm
> platforms) use this driver."
> 

I did highlight my reasons for wondering if a board needs to be mentioned, perhaps I should
take some more time before sending the next patch to ensure we've actually concluded the
discussion on the last one:

"since the driver is related to SoC firmware and
not on the board, I will mention SM8650+ as the supported SoCs since we began enabling
the driver from that chip on-wards. I hope this reasoning is fine."

> Usage of something on SoC is not a proof that it actually is used by
> upstream platforms and we absolutely do not care at all about downstream
> users. I spent way too much time on this and even very specific
> instructions were not working, so I don't know how else I can help.
> 

I understand the frustration. Let's take a breather, I will reflect and take a week off
before I try again or ask someone else to.

Thanks,
Harshal

> Best regards,
> Krzysztof


  parent reply	other threads:[~2025-12-09  7:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 12:18 [PATCH v3] arm64: defconfig: Enable QCOMTEE on Qualcomm SM8650+ Harshal Dev
2025-12-09  5:58 ` Krzysztof Kozlowski
2025-12-09  6:14   ` Dmitry Baryshkov
2025-12-10  3:51     ` Bjorn Andersson
2025-12-10  5:20       ` Krzysztof Kozlowski
2025-12-10  9:05       ` Harshal Dev
2025-12-12  1:25         ` Sumit Garg
2025-12-15 11:20           ` Harshal Dev
2025-12-22 16:56             ` Bjorn Andersson
2026-01-02  8:51               ` Harshal Dev
2026-01-02 18:23                 ` Bjorn Andersson
2026-01-07  6:20                   ` Harshal Dev
2026-01-07 15:04                     ` Bjorn Andersson
2026-01-08  9:46                       ` Harshal Dev
2025-12-09  7:15   ` Harshal Dev [this message]
2025-12-12  1:14   ` Sumit Garg

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=948b35bc-8479-4d94-a5f7-e8893de8fbf1@oss.qualcomm.com \
    --to=harshal.dev@oss.qualcomm.com \
    --cc=amirreza.zarrabi@oss.qualcomm.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=geert+renesas@glider.be \
    --cc=jens.wiklander@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=sumit.garg@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