NXP i.MX8Q Amphion Video Processing Unit (Windsor/Malone)
Hardware video encoder and decoder block (Amphion's Windsor encoder and Malone decoder) embedded in NXP's i.MX 8QuadXPlus and i.MX 8QuadMax application processors, used in industrial, automotive, and embedded multimedia products to accelerate H.264, HEVC, and other codecs without burning CPU cycles.
recommendation
It should stay in the kernel because the underlying NXP i.MX 8QuadMax and i.MX 8QuadXPlus SoCs are still actively sold in 2025 under NXP's longevity program, the development boards remain available, and upstream traffic from 2025 shows ongoing feature work (HEVC decoder latency tuning) and routine cleanups rather than any move toward removal.
repository signals
sources
- lists.openwall.net
March 26, 2025 review traffic shows active upstream work on Amphion HEVC decoder latency improvements rather than deprecation/removal.
- lists.openwall.net
June 14, 2025 cleanup patch against amphion indicates the driver is still maintained in normal upstream hygiene flow, not orphaned.
- nxp.com
NXP lists the i.MX 8 family as Active and in its longevity program, indicating the underlying SoC family remained commercially live in 2025.
- nxp.com
NXP still advertises the i.MX 8QuadMax/QuadPlus MEK, showing ongoing new-development availability for supported Amphion-capable i.MX8Q platforms.
- phoronix.com
Contemporary reporting on the upstreaming effort ties the driver to NXP i.MX8QXP and i.MX8QM VPU hardware, matching the in-tree driver scope.
codex reasoning notes (technical)
Local tree inspection via shell (`rg`, `sed`) identified this as the V4L2 Amphion VPU driver for NXP/Freescale i.MX8Q, with Windsor encoder and Malone decoder blocks and support centered on i.MX8QXP/i.MX8QM. Web search was used because lore MCP/`lei` were unavailable in this environment: openwall results show 2025 feature-review and cleanup traffic, and no removal/deprecation thread surfaced. NXP product pages obtained via web search show i.MX8 family still marked Active and MEK hardware still offered, so this is not legacy-only hardware. Given the provided static history (103 substantive commits in 5y, latest touch 2026-01-13, 20 authors) plus current product availability, the driver should be kept, not deprecated.