drivers/media/platform/allegro-dvt · keep

Allegro DVT AL5E/AL5D video encoder on AMD/Xilinx Zynq UltraScale+ EV

The hardware H.264/H.265 video encoder block (Allegro DVT AL5E/AL5D, branded as the VCU) embedded in AMD/Xilinx Zynq UltraScale+ MPSoC "EV" family chips. These FPGA-plus-ARM SoCs are used in industrial cameras, broadcast gear, medical imaging, drones, and other embedded video appliances, and have been shipping since the mid-2010s.

keep conf=0.83 last_sold=2025 deploy=low replacement=none subsystem=media category=media-other

83%

recommendation

It should stay because the underlying Zynq UltraScale+ EV silicon is still actively sold by AMD in 2025 with long lifecycle commitments, AMD's own 2025.1 VCU product guide lists this as the supported Linux driver for the codec block, and the code has seen substantive commits and a healthy spread of contributors within the last five years. Deployments are niche (embedded video appliances rather than mass-market gear), but there is no replacement driver covering the same hardware.

repository signals

11 files

7,716 source lines

43 commits, 5y

+983 / −300 lines added / removed, 5y

21 authors, 5y

monthly commits · 2021-04-21 → 2026-04-21 · 43 total · active in 17/61 months

sources

docs.amd.com
AMD's 2025.1 VCU product guide names allegro/al5e/al5d as the core VCU Linux kernel drivers, indicating current vendor-supported use rather than obsolescence.
amd.com
AMD still markets Zynq UltraScale+ MPSoC EV devices with integrated H.264/H.265 video codec and long lifecycle language, supporting continued new-hardware availability in 2025.
cateee.net
LKDDb shows CONFIG_VIDEO_ALLEGRO_DVT present through current kernel series and ties it to compatible string allegro,al5e-1.1 and ZynqMP EV-family VCU hardware.

codex reasoning notes (technical)

Real driver, not an early-exit case. Local tree inspection (exec_command `rg`/`sed`) shows `module_platform_driver`, OF match `allegro,al5e-1.1`, and module description `Allegro DVT encoder driver`. Lore-first attempt used MCP `lore_file_timeline` on the directory path, which returned no hits for the dir-prefix form; follow-up MCP `lore_path_mentions`/`lore_regex` timed out, so I fell back to the provided static commit metadata showing substantive touches through 2025-10-20 and 16 authors in 5y, which argues against deprecation. URLs were obtained by web search (`turn0search0`, `turn0search6`, `turn2search0`). Hardware is niche embedded/industrial video-encode SoC IP, so deployments today are low, but still present in new designs; no obvious upstream replacement driver covers the same VCU block.