drivers/crypto/qce

Qualcomm Crypto Engine (QCE) accelerator

An on-chip cryptographic accelerator block built into Qualcomm Snapdragon and IoT SoCs, used to offload AES, SHA, and related symmetric-crypto operations from the CPU. It appears in a wide range of current Qualcomm platforms including the QCS8250 IoT processor and recent mobile/automotive SoCs such as SM8650, SM8750, QCS8300, and IPQ9574.

keep conf=0.89 deploy=medium replacement=none subsystem=crypto category=crypto
89%

recommendation

It should stay in the kernel because the hardware is still shipping on new Qualcomm SoCs in 2025 (with product longevity commitments stretching into the mid-2030s for parts like the QCS8250) and the driver is actively maintained — Qualcomm engineers were posting functional patches to linux-crypto as recently as 2026. No alternative driver covers the same on-SoC crypto offload role, so removing it would regress real, currently-sold platforms.

repository signals

14 files
3,647 source lines
37 commits, 5y
+1,273 / −211 lines added / removed, 5y
17 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 37 total · active in 13/61 months
2021 2022 2023 2024 2025 2026 2021-04: 7 commits · +1,098 −31 2021-05: 3 commits · +18 −11 2021-06: 1 commit · +6 −2 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 3 commits · +3 −3 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 1 commit · +11 −9 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 1 commit · +23 −22 2023-01: 1 commit · +2 −2 2023-02: 3 commits · +20 −4 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 1 commit · +2 −3 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 1 commit · +1 −1 2024-11: 0 commits · +0 −0 2024-12: 11 commits · +78 −113 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 2 commits · +5 −4 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 2 commits · +6 −6 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    QCE still receives active upstream functional work in 2026; this patch updates DMA handling in the driver.

  2. cateee.net

    LKDDb shows CONFIG_CRYPTO_DEV_QCE is a current upstream driver covering Qualcomm QCE hardware and matching OF compatibles including qcom,crypto-v5.1, qcom,crypto-v5.4, and qcom,qce.

  3. qualcomm.com

    Qualcomm still markets Linux-relevant IoT SoCs in this family timeframe; the 2024 QCS8250 brief lists enterprise/commercial IoT target applications and expected product longevity through February 2036.

codex reasoning notes (technical)

Keep. lore_activity on drivers/crypto/qce/core.c showed multiple 2026 linux-crypto patches, so this is maintained rather than orphaned. No removal signal was found in the limited lore checks; the attempted directory timeline returned no hits, which looks like a path-coverage limitation rather than real inactivity. Web search + open on LKDDb confirmed the driver remains present in current kernels. Web search + open on Qualcomm's QCS8250 product brief supports ongoing new Qualcomm SoC deployments. Local exec_command grep of in-tree DTs also found current QCE compatibles on modern Qualcomm platforms (for example sm8650, sm8750, qcs8300, ipq9574), reinforcing that the hardware class is still shipping. No single upstream replacement driver covers the same on-SoC crypto offload role.