drivers/crypto/xilinx

AMD/Xilinx Zynq UltraScale+ and Versal SoC crypto accelerators

Hardware crypto blocks built into AMD (formerly Xilinx) Zynq UltraScale+ MPSoC and Versal adaptive SoC chips, exposing firmware-backed AES-GCM encryption, SHA-3 hashing, and a true random number generator. These chips are widely used in industrial, aerospace, networking, and embedded systems where an FPGA fabric is paired with ARM cores.

keep conf=0.93 deploy=medium replacement=none subsystem=crypto category=crypto
93%

recommendation

It should stay because the hardware is current AMD product line silicon still being sold new in 2025, with stated product availability stretching toward 2045, and the driver itself is actively maintained — AMD engineers were adding new GCM(AES) functionality for Versal in late 2025 and posting fixes into early 2026. Software crypto cannot substitute for these on-chip accelerators, so removing it would strand real users.

repository signals

4 files
1,715 source lines
30 commits, 5y
+1,701 / −433 lines added / removed, 5y
11 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 30 total · active in 15/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 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: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 1 commit · +284 −0 2022-03: 1 commit · +8 −27 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: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 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: 1 commit · +1 −2 2023-08: 2 commits · +18 −19 2023-09: 0 commits · +0 −0 2023-10: 3 commits · +4 −9 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 1 commit · +3 −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: 1 commit · +1 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 1 commit · +2 −2 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 3 commits · +45 −55 2025-05: 1 commit · +19 −11 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 1 commit · +406 −0 2025-09: 1 commit · +31 −6 2025-10: 1 commit · +1 −1 2025-11: 0 commits · +0 −0 2025-12: 10 commits · +873 −296 2026-01: 2 commits · +5 −5 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Upstream was still adding new functionality in late 2025: GCM(AES) support for AMD/Xilinx Versal in this driver area.

  2. lore.kernel.org

    The driver still received linux-crypto maintenance in January 2026, indicating current upstream attention rather than abandonment.

  3. amd.com

    AMD was still marketing Zynq UltraScale+ MPSoCs as current products, with stated long product lifespans through 2045 for UltraScale+ adaptive SoCs/FPGAs.

  4. amd.com

    AMD was still marketing Versal adaptive SoCs as an active product family, supporting ongoing new deployments.

codex reasoning notes (technical)

Local source inspection via `rg` showed three real hardware-backed crypto drivers: ZynqMP AES-GCM, ZynqMP SHA3, and Versal TRNG. `lore_file_timeline` on the directory path returned no hits (likely exact-path/file-oriented behavior), so I used `lore_activity` on `drivers/crypto/xilinx/zynqmp-aes-gcm.c`, which showed late-2025 feature work and a January 27, 2026 fix on lore URLs above. Web search found current AMD product pages for Zynq UltraScale+ MPSoC and Versal, supporting that the hardware remained sold new in 2025. No natural in-tree replacement covers the same SoC firmware-backed crypto blocks; software crypto exists but is not a like-for-like driver replacement.