From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Andersson <bjorn.andersson@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] arm64: defconfig: Enable QCOMTEE for Qualcomm SoCs
Date: Fri, 5 Dec 2025 13:08:41 +0530 [thread overview]
Message-ID: <f20833a4-1571-41f8-875a-d27086be3090@oss.qualcomm.com> (raw)
In-Reply-To: <ba60f51f-7676-402d-b602-c327d7496f34@kernel.org>
Hi Krzysztof,
On 12/2/2025 3:13 PM, Krzysztof Kozlowski wrote:
> On 02/12/2025 10:37, Harshal Dev wrote:
>> Enable config for the QCOMTEE driver to facilitate communication with the
>> Qualcomm Trusted Execution Environment (QTEE) on Qualcomm platforms.
>
> Which platforms use it?
The Qualcomm Trusted Execution Environment (QTEE) firmware is available on all
Qualcomm platforms. However, certain platforms like db410c (APQ8016), where QTEE
does not support Object-IPC (the communication protocol implemented by QCOMTEE driver)
a graceful -EIO is returned by qcom_scm_qtee_init() which is in-charge of dynamically
registering the QCOMTEE driver as a platform driver during qcom_scm_probe().
More details available here: https://lore.kernel.org/op-tee/20250820-qcom-tee-using-tee-ss-without-mem-obj-v8-0-7066680f138a@oss.qualcomm.com/T/#m1eba97cb921c958034ffe7e2bfb776177ba48eb6
And so, the QCOMTEE driver can be safely enabled on all Qualcomm platforms regardless
of QTEE firmware version.
> Why this cannot be a module?
Upon a bit of reflection, I have realized that it is completely fine to have this driver
built as an in-tree module. I have also validated that this presents no issues during
loading/unloading of the driver.
I will send a new patch and update the CONFIG_QCOMTEE flag to m.
Regards,
Harshal
>
>>
>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>> ---
>> arch/arm64/configs/defconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
> Best regards,
> Krzysztof
prev parent reply other threads:[~2025-12-05 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 9:37 Harshal Dev
2025-12-02 9:43 ` Krzysztof Kozlowski
2025-12-02 9:45 ` Krzysztof Kozlowski
2025-12-05 7:40 ` Harshal Dev
2025-12-05 7:38 ` Harshal Dev [this message]
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=f20833a4-1571-41f8-875a-d27086be3090@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=geert+renesas@glider.be \
--cc=jens.wiklander@linaro.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
all inboxes | Powered by JetHome®