All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumit Garg via OP-TEE <op-tee@lists.trustedfirmware.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Harshal Dev <harshal.dev@oss.qualcomm.com>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	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: Fri, 12 Dec 2025 10:14:29 +0900	[thread overview]
Message-ID: <aTtsdfNxulSTyyoJ@sumit-X1> (raw)
In-Reply-To: <309e0391-58a3-466b-a113-ab864188f6fe@kernel.org>

On Tue, Dec 09, 2025 at 06:58:27AM +0100, 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."
> 
> 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.

Harsal,

I remember myself following a list of instructions to run QTEE test
application on RB5 which were part of QTEE patch-set. And I do know there
are contributions going on in meta-qcom regarding those libraries here [1][2].

[1] https://github.com/qualcomm-linux/meta-qcom/pull/1167
[2] https://github.com/qualcomm-linux/meta-qcom/pull/1094

So, it would be nice if you could point people to a coherent
documentation which can list instructions to reproduce setup preferably
based on meta-qcom.

-Sumit

WARNING: multiple messages have this Message-ID (diff)
From: Sumit Garg <sumit.garg@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Harshal Dev <harshal.dev@oss.qualcomm.com>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Jens Wiklander <jens.wiklander@linaro.org>,
	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: Fri, 12 Dec 2025 10:14:29 +0900	[thread overview]
Message-ID: <aTtsdfNxulSTyyoJ@sumit-X1> (raw)
In-Reply-To: <309e0391-58a3-466b-a113-ab864188f6fe@kernel.org>

On Tue, Dec 09, 2025 at 06:58:27AM +0100, 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."
> 
> 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.

Harsal,

I remember myself following a list of instructions to run QTEE test
application on RB5 which were part of QTEE patch-set. And I do know there
are contributions going on in meta-qcom regarding those libraries here [1][2].

[1] https://github.com/qualcomm-linux/meta-qcom/pull/1167
[2] https://github.com/qualcomm-linux/meta-qcom/pull/1094

So, it would be nice if you could point people to a coherent
documentation which can list instructions to reproduce setup preferably
based on meta-qcom.

-Sumit

  parent reply	other threads:[~2025-12-12  1:14 UTC|newest]

Thread overview: 32+ 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 via OP-TEE
2025-12-08 12:18 ` Harshal Dev
2025-12-09  5:58 ` Krzysztof Kozlowski via OP-TEE
2025-12-09  5:58   ` Krzysztof Kozlowski
2025-12-09  6:14   ` Dmitry Baryshkov via OP-TEE
2025-12-09  6:14     ` Dmitry Baryshkov
2025-12-10  3:51     ` Bjorn Andersson via OP-TEE
2025-12-10  3:51       ` Bjorn Andersson
2025-12-10  5:20       ` Krzysztof Kozlowski via OP-TEE
2025-12-10  5:20         ` Krzysztof Kozlowski
2025-12-10  9:05       ` Harshal Dev via OP-TEE
2025-12-10  9:05         ` Harshal Dev
2025-12-12  1:25         ` Sumit Garg via OP-TEE
2025-12-12  1:25           ` Sumit Garg
2025-12-15 11:20           ` Harshal Dev via OP-TEE
2025-12-15 11:20             ` Harshal Dev
2025-12-22 16:56             ` Bjorn Andersson via OP-TEE
2025-12-22 16:56               ` Bjorn Andersson
2026-01-02  8:51               ` Harshal Dev via OP-TEE
2026-01-02  8:51                 ` Harshal Dev
2026-01-02 18:23                 ` Bjorn Andersson via OP-TEE
2026-01-02 18:23                   ` Bjorn Andersson
2026-01-07  6:20                   ` Harshal Dev via OP-TEE
2026-01-07  6:20                     ` Harshal Dev
2026-01-07 15:04                     ` Bjorn Andersson via OP-TEE
2026-01-07 15:04                       ` Bjorn Andersson
2026-01-08  9:46                       ` Harshal Dev via OP-TEE
2026-01-08  9:46                         ` Harshal Dev
2025-12-09  7:15   ` Harshal Dev via OP-TEE
2025-12-09  7:15     ` Harshal Dev
2025-12-12  1:14   ` Sumit Garg via OP-TEE [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=aTtsdfNxulSTyyoJ@sumit-X1 \
    --to=op-tee@lists.trustedfirmware.org \
    --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=harshal.dev@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.