linux-drivers/
drivers/gpu/drm/xlnx

AMD/Xilinx Zynq UltraScale+ MPSoC DisplayPort Subsystem

The DisplayPort output controller integrated into AMD/Xilinx Zynq UltraScale+ MPSoC chips, a family of FPGA-plus-ARM system-on-chip devices used in embedded video, industrial control, medical imaging, and aerospace gear. It drives the on-chip display pipeline that feeds an external DisplayPort monitor or panel.

keep conf=0.88 deploy=low replacement=none subsystem=gpu category=graphics-display
88%

recommendation

It should stay because it is the only Linux driver for the DisplayPort output block built into AMD/Xilinx Zynq UltraScale+ MPSoC chips, which AMD still sells new in 2025 for embedded and industrial use. Upstream activity is healthy, with patches landing as recently as 2026 for API updates and link-retraining fixes, and there is no generic replacement that could take over.

repository signals

12 files
5,686 source lines
139 commits, 5y
+3,581 / −1,930 lines added / removed, 5y
38 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 139 total · active in 37/61 months
2021 2022 2023 2024 2025 2026 2021-04: 3 commits · +3 −2 2021-05: 1 commit · +22 −17 2021-06: 2 commits · +1 −3 2021-07: 0 commits · +0 −0 2021-08: 33 commits · +1,427 −1,153 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 2 commits · +7 −3 2021-12: 1 commit · +2 −1 2022-01: 2 commits · +2 −1 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 2 commits · +3 −2 2022-05: 0 commits · +0 −0 2022-06: 1 commit · +1 −0 2022-07: 3 commits · +3 −3 2022-08: 3 commits · +10 −10 2022-09: 1 commit · +93 −41 2022-10: 0 commits · +0 −0 2022-11: 2 commits · +5 −4 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 2 commits · +3 −3 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +2 −4 2023-06: 1 commit · +3 −1 2023-07: 1 commit · +2 −2 2023-08: 1 commit · +3 −7 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 1 commit · +0 −1 2024-01: 5 commits · +16 −8 2024-02: 1 commit · +4 −0 2024-03: 4 commits · +11 −11 2024-04: 17 commits · +320 −121 2024-05: 5 commits · +36 −26 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 9 commits · +805 −58 2024-09: 2 commits · +5 −1 2024-10: 3 commits · +531 −103 2024-11: 2 commits · +2 −3 2024-12: 4 commits · +3 −3 2025-01: 1 commit · +2 −0 2025-02: 6 commits · +63 −105 2025-03: 1 commit · +2 −1 2025-04: 2 commits · +3 −8 2025-05: 1 commit · +11 −21 2025-06: 0 commits · +0 −0 2025-07: 3 commits · +8 −36 2025-08: 1 commit · +5 −2 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 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

    Upstream activity is current: April 13, 2026 patch updates zynqmp_dp for DRM bridge API changes.

  2. lore.kernel.org

    Upstream activity includes functional bug-fix work: January 6, 2026 patch retrains the link after HPD when needed.

  3. amd.com

    The underlying Zynq UltraScale+ MPSoC family is an actively marketed AMD product line, supporting the conclusion that new hardware was still sold in 2025.

  4. cateee.net

    LKDDb identifies CONFIG_DRM_ZYNQMP_DPSUB as the Linux driver for the ZynqMP DisplayPort controller/subsystem.

codex reasoning notes (technical)

`keep`: local tree inspection (`exec_command`) shows this is the SoC-specific ZynqMP DisplayPort DRM driver (`DRM_ZYNQMP_DPSUB`) with no generic successor. Lore evidence was obtained via `lore_file_timeline` on `drivers/gpu/drm/xlnx/zynqmp_dp.c`, which showed dense activity through 2024-2026 and yielded the cited April 2026 API-conversion patch and January 2026 functional fix. A removal/deprecation subject scan via `lore_regex` did not produce evidence of an active removal series in this sampled pass. Product/LKDDb URLs are canonical-recall sources used to identify the hardware family and confirm ongoing market presence; this points to continued but niche embedded/industrial deployments, so `deployments_today` is `low` rather than `none`.