mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
To: Sumit Garg <sumit.garg@kernel.org>,
	Harshal Dev <harshal.dev@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	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>,
	Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] arm64: defconfig: Enable QCOMTEE module for QTEE-enabled Qualcomm SoCs
Date: Thu, 29 Jan 2026 16:34:05 +1100	[thread overview]
Message-ID: <5cede166-8527-4360-a87d-ba090ad420da@oss.qualcomm.com> (raw)
In-Reply-To: <aWoNut1UzpL8Il9V@sumit-xelite>



On 1/16/2026 9:06 PM, Sumit Garg wrote:
> On Wed, Jan 14, 2026 at 01:49:14PM +0530, Harshal Dev wrote:
>> All Qualcomm SoCs starting from SM8650 provide access to the Qualcomm
>> Trusted Execution Environment (QTEE) through the SMCInvoke interface,
>> implemented by the QCOMTEE driver. QTEE runs in the Secure World domain
>> on ARM64 CPUs and exposes secure services to Linux running in the Normal
>> World domain.
>>
>> This change enables the QCOMTEE driver as a module to support
>> communication with QTEE.
>>
>> QCOMTEE has been tested on a Qualcomm RB3Gen2 board by loading and
>> executing a Trusted Application via tests hosted at
>> github.com/qualcomm/minkipc.
>>
>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>> ---
>> Changes in v4:
>> - Updated the commit message as per discussion to clarify the following:
>> - Why we are enabling QCOMTEE for all arm64 boards.
>> - From which Qualcomm SoC onwards the driver is applicable.
>> - What functionality the driver provides.
>> - How the functionality has been tested and on which board.
>> - Link to v3: https://lore.kernel.org/r/20251208-qcom_qcomtee_defconfig-v3-1-b50dcf8ab45e@oss.qualcomm.com
> 
> Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> 
> -Sumit
> 

Reviewed-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>

- Amir

>>
>> 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
>>
>> Changes in v2:
>> - Updated CONFIG_QCOMTEE flag to 'm' since QCOMTEE can be built as a module.
>> - Link to v1: https://lore.kernel.org/r/20251202-qcom_qcomtee_defconfig-v1-1-11bfe40a8ea4@oss.qualcomm.com
>> ---
>>  arch/arm64/configs/defconfig | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>> index cdb7d69e3b24..e952d24bef77 100644
>> --- a/arch/arm64/configs/defconfig
>> +++ b/arch/arm64/configs/defconfig
>> @@ -1789,6 +1789,7 @@ CONFIG_FPGA_MGR_ZYNQMP_FPGA=m
>>  CONFIG_FPGA_MGR_VERSAL_FPGA=m
>>  CONFIG_TEE=y
>>  CONFIG_OPTEE=y
>> +CONFIG_QCOMTEE=m
>>  CONFIG_MUX_GPIO=m
>>  CONFIG_MUX_MMIO=y
>>  CONFIG_SLIMBUS=m
>>
>> ---
>> base-commit: 47b7b5e32bb7264b51b89186043e1ada4090b558
>> change-id: 20251202-qcom_qcomtee_defconfig-8dc0fed1411b
>>
>> Best regards,
>> -- 
>> Harshal Dev <harshal.dev@oss.qualcomm.com>
>>


  reply	other threads:[~2026-01-29  5:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14  8:19 Harshal Dev
2026-01-16 10:06 ` Sumit Garg
2026-01-29  5:34   ` Amirreza Zarrabi [this message]
2026-02-13 10:24 ` Kuldeep Singh
2026-02-13 10:26   ` Krzysztof Kozlowski
2026-02-13 10:56     ` Harshal Dev
2026-02-13 11:18       ` Krzysztof Kozlowski
2026-02-16  5:18     ` Kuldeep Singh
2026-02-16  7:24       ` Krzysztof Kozlowski
2026-02-16 10:36       ` Harshal Dev
2026-02-16 10:39         ` Krzysztof Kozlowski
2026-02-16 12:08           ` Harshal Dev
2026-03-11 20:56 ` Bjorn Andersson

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=5cede166-8527-4360-a87d-ba090ad420da@oss.qualcomm.com \
    --to=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=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

all inboxes | Powered by JetHome®