Texas Instruments DTHE V2 crypto accelerator on AM62L K3 SoCs
A hardware cryptography engine (Data Transform and Hashing Engine, version 2) embedded in Texas Instruments' K3-family system-on-chip processors, starting with the AM62L line of low-power Arm application processors aimed at industrial and embedded designs. It offloads AES encryption from the CPU so that small embedded Linux systems can do bulk symmetric crypto more efficiently than in software.
recommendation
It should stay in the kernel because it is brand new, actively maintained, and tied to silicon TI is currently selling. The initial driver landed upstream in August 2025 with AES ECB/CBC support and gained AES-XTS just two months later, and TI still lists the AM62L as an active product, so this is fresh hardware enablement rather than legacy code.
repository signals
sources
- git.kernel.org
Kconfig describes this as the TI DTHE V2 cryptography engine found on TI K3 SoCs.
- git.kernel.org
The OF match table binds the driver to compatible string "ti,am62l-dthev2", tying it to AM62L hardware.
- git.kernel.org
The driver was introduced upstream in August 2025 as a new AES ECB/CBC hardware offload driver, indicating very recent upstream enablement rather than obsolescence.
- git.kernel.org
The driver gained AES-XTS support in October 2025, showing active feature work after initial merge.
- ti.com
TI lists AM62L as ACTIVE in its product page, which supports the conclusion that related hardware was still sold new in 2025.
codex reasoning notes (technical)
Real driver, not an early-exit case. Local shell inspection (`rg`, `sed`) showed a platform driver with OF match `ti,am62l-dthev2` and Kconfig help text for TI K3 SoCs. Local `git -c safe.directory=... log/show` showed all 4 substantive commits are from 2025, including initial merge and later AES-XTS support; the two git.kernel.org URLs were constructed from those locally obtained paths/commit IDs using canonical stable kernel.org URL patterns. Web search found the TI AM62L product page, which explicitly shows ACTIVE status. A web lore search for removal/deprecation terms returned no hits, so there is no evidence of an upstream removal discussion. This is a newly added, still-expanding embedded accelerator driver with niche but current deployments, so `keep` is the defensible recommendation.