Enable config for the QCOMTEE driver to facilitate communication with the Qualcomm Trusted Execution Environment (QTEE) on Qualcomm platforms.
Signed-off-by: Harshal Dev harshal.dev@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..57b2b09d0479 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=y CONFIG_MUX_GPIO=m CONFIG_MUX_MMIO=y CONFIG_SLIMBUS=m
--- base-commit: 47b7b5e32bb7264b51b89186043e1ada4090b558 change-id: 20251202-qcom_qcomtee_defconfig-8dc0fed1411b
Best regards,
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? Why this cannot be a module?
Signed-off-by: Harshal Dev harshal.dev@oss.qualcomm.com
arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+)
Best regards, Krzysztof
On 02/12/2025 10:43, 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? Why this cannot be a module?
Also, you did not really cc necessary lists. Use get_maintainers.pl on qcom soc code for example.
Best regards, Krzysztof
Hi, Krzysztof
On 12/2/2025 3:15 PM, Krzysztof Kozlowski wrote:
On 02/12/2025 10:43, 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? Why this cannot be a module?
Also, you did not really cc necessary lists. Use get_maintainers.pl on qcom soc code for example.
Sure, thanks for pointing this out, I will add the folks from Qcom SoC code in the next patch. :)
Regards, Harshal
Best regards, Krzysztof
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-ob...
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
op-tee@lists.trustedfirmware.org
-
Harshal Dev -
Krzysztof Kozlowski