linux-kernel - Re: [PATCH v3] arm64: defconfig: Enable QCOMTEE on Qualcomm SM8650+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <309e0391-58a3-466b-a113-ab864188f6fe@kernel.org>
Date: Tue, 9 Dec 2025 06:58:27 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Harshal Dev <harshal.dev@....qualcomm.com>,
 Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
 Konrad Dybcio <konradybcio@...nel.org>,
 Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
 Sumit Garg <sumit.garg@...nel.org>,
 Jens Wiklander <jens.wiklander@...aro.org>
Cc: Amirreza Zarrabi <amirreza.zarrabi@....qualcomm.com>,
 Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven <geert+renesas@...der.be>,
 op-tee@...ts.trustedfirmware.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] arm64: defconfig: Enable QCOMTEE on Qualcomm SM8650+

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@....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."

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.

Best regards,
Krzysztof