Trusted Execution Environment (TEE) subsystem: OP-TEE, AMD-TEE, Qualcomm QTEE
A kernel framework that lets Linux talk to secure-world firmware running alongside the OS on modern CPUs, used for DRM key handling, secure boot attestation, biometrics, and confidential computing. Back-ends cover Arm TrustZone (OP-TEE), AMD SEV on EPYC servers, Qualcomm QTEE on Snapdragon, and Arm Trusted Services.
recommendation
It should stay because the subsystem underpins security features on hardware actively shipping in 2025, including AMD EPYC 7000/8000/9000 confidential-computing servers, Qualcomm and other Arm SoCs in phones and embedded boards, and AMD/Xilinx Zynq MPSoCs. Upstream development is healthy, with new feature work landing on tee_core and the OP-TEE driver as recently as January 2026, so there is no obsolescence case to make.
repository signals
sources
- lore.kernel.org
`drivers/tee/tee_core.c` saw active upstream feature work in January 2026 (`tee: add revision sysfs attribute`) with review on LKML, indicating the subsystem is maintained rather than in retirement.
- lore.kernel.org
`drivers/tee/optee/core.c` also saw active upstream feature work in January 2026 (`tee: optee: store OS revision for TEE core`), showing continued investment in a concrete in-tree TEE driver.
- optee.readthedocs.io
Official OP-TEE documentation describes OP-TEE as the Linux-kernel TEE framework/driver companion for Arm TrustZone systems, showing this is a current upstream and ecosystem-relevant interface rather than legacy-only hardware.
- optee.readthedocs.io
Official OP-TEE docs list supported AMD/Xilinx Zynq MPSoC boards, evidence that TEE-backed Arm SoCs using this stack remain in active embedded deployments.
- amd.com
AMD states SEV creates a TEE and is built into current EPYC 7000/8000/9000 server CPUs, showing `drivers/tee/amdtee` maps to hardware still shipping in 2025-era products.
codex reasoning notes (technical)
Not an early-exit case: local shell inspection (`ls`, `rg`, `sed` on `drivers/tee/Kconfig` and `Makefile`) showed real in-tree driver code plus active subdrivers (`optee`, `amdtee`, `qcomtee`, `tstee`). Lore evidence came from `lore_activity` on `drivers/tee/tee_core.c` and `drivers/tee/optee/core.c`, which returned 2025-2026 patches with review, so this is actively maintained. `lore_file_timeline` on the directory path returned no matches, which looks like a path-granularity limitation rather than a removal signal; no concrete removal thread was found. Deployment evidence came from web `search/open/find` on official OP-TEE docs and AMD EPYC confidential-computing pages. Because TEE hardware/interfaces are still shipping across Arm embedded/mobile and AMD server confidential-computing platforms, there is no obsolescence case here; keep the directory.