linux-kernel - Re: [PATCH v4] arm64: defconfig: Enable QCOMTEE module for QTEE-enabled Qualcomm SoCs

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] [day] [month] [year] [list]

Message-ID: <aWoNut1UzpL8Il9V@sumit-xelite>
Date: Fri, 16 Jan 2026 15:36:50 +0530
From: Sumit Garg <sumit.garg@...nel.org>
To: Harshal Dev <harshal.dev@....qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
	Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
	Konrad Dybcio <konradybcio@...nel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
	Jens Wiklander <jens.wiklander@...aro.org>,
	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 v4] arm64: defconfig: Enable QCOMTEE module for
 QTEE-enabled Qualcomm SoCs

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@....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@....qualcomm.com>

-Sumit

> 
> 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@....qualcomm.com>
>