Qualcomm Trusted Execution Environment (QTEE) interface
Linux-side interface to the Qualcomm Trusted Execution Environment, the secure operating system that runs alongside Android/Linux on Snapdragon SoCs. It lets the kernel communicate with QTEE for tasks like secure key storage, DRM, biometric matching, and platform attestation on current Qualcomm mobile and embedded chips.
recommendation
It should stay because the code is brand new, landing in mainline in 2025 with bug-fix activity continuing into 2026, and it is the only upstream path for talking to QTEE on shipping Snapdragon hardware. Qualcomm engineers are actively developing it on the lists, and Qualcomm's own current security documentation positions QTEE as a core part of new Snapdragon platforms, so demand will only grow.
repository signals
sources
- kernel.org
Official kernel documentation describes qcomtee/QTEE as the Linux driver for Qualcomm Trusted Execution Environment, indicating a maintained in-tree subsystem interface.
- cateee.net
LKDDb shows CONFIG_QCOMTEE present in mainline kernels 6.18-6.19 and 7.0-rc+HEAD, confirming current upstream enablement rather than retirement.
- lore.kernel.org
Lore thread for the qcomtee patch series shows active 2025 upstream development and review, with no removal/deprecation context.
- qualcomm.com
Qualcomm's recent Snapdragon security paper describes Qualcomm TEE as part of current mobile-platform security architecture, supporting continued deployment in new hardware.
codex reasoning notes (technical)
Real driver directory with module/Kconfig entry and Qualcomm SoC dependency. Local exec_command evidence: git log for drivers/tee/qcomtee shows introduction in 2025 and bug-fix activity through 2026-01-05, with no sign of stasis. Source acquisition: kernel.org doc and LKDDb page were obtained via web search then opened; the lore URL was obtained from web search results/snippets for the qcomtee patch series after MCP/lei were unavailable; Qualcomm PDF was obtained via web search then opened. The driver is very new, actively maintained, tied to current Snapdragon/QTEE deployments, and has no natural upstream replacement for the same secure-OS backend, so keep is the defensible recommendation.