drivers/gpu/drm/logicvc

Xylon LogiCVC-ML FPGA display controller

A programmable display controller IP core from Xylon (logicBRICKS) that runs inside Xilinx/AMD Zynq-7000, UltraScale, and UltraScale+ FPGAs to drive LCD and embedded panels. It is used in specialized industrial, automotive, and embedded systems where the display pipeline is built into custom FPGA hardware rather than a fixed GPU.

keep-annotate conf=0.85 deploy=low replacement=none subsystem=gpu category=graphics-display
85%

recommendation

Worth keeping but flagging as niche, because the IP block is still sold by Xylon in 2026 and the kernel code is actively receiving bug fixes (including stable-tree backports as recently as January 2026), yet real-world deployments are limited to FPGA-based embedded products. No other in-tree DRM driver covers this vendor-specific hardware, so removal would orphan existing users; documenting its low-volume, FPGA-only scope is the appropriate middle ground.

repository signals

15 files
2,210 source lines
28 commits, 5y
+2,285 / −54 lines added / removed, 5y
16 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 28 total · active in 16/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: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 1 commit · +2,223 −0 2022-06: 7 commits · +7 −5 2022-07: 2 commits · +2 −3 2022-08: 3 commits · +13 −14 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 3 commits · +13 −4 2022-12: 0 commits · +0 −0 2023-01: 1 commit · +0 −2 2023-02: 0 commits · +0 −0 2023-03: 1 commit · +2 −2 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +2 −4 2023-06: 1 commit · +2 −0 2023-07: 1 commit · +1 −1 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +9 −0 2023-10: 0 commits · +0 −0 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: 1 commit · +5 −12 2024-10: 0 commits · +0 −0 2024-11: 1 commit · +1 −1 2024-12: 2 commits · +1 −2 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: 1 commit · +2 −2 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 1 commit · +2 −2 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. logicbricks.com

    Vendor product page was live in 2026, lists current pricing, Linux software support, and support for AMD Zynq 7000 / UltraScale / UltraScale+ families, so the IP is still commercially sold.

  2. spinics.net

    Public patch thread from 2026-01-30 shows current upstream bug-fix traffic for drm/logicvc, with no removal proposal in that thread.

  3. git.kernel.org

    Stable-kernel commit for a 2026 logicvc fix indicates the driver is still maintained enough to receive upstream/stable fixes.

  4. git.kernel.org

    Kconfig identifies this directory as the DRM driver for the Xylon LogiCVC programmable logic block.

codex reasoning notes (technical)

Real driver, not an early-exit case: local file inspection (`rg`, `sed`) shows `module_platform_driver`, OF compatibles `xylon,logicvc-*`, and Kconfig naming Xylon LogiCVC. Local history (`git -c safe.directory ... log`) shows substantive touches through 2026-01-30, so it is not abandoned. lore MCP was unavailable and `lei` was not installed; I checked public mailing-list evidence via web search/open instead, finding active fix traffic but no removal discussion. Vendor product pages obtained by web search/open show the IP is still marketed in 2026, but as a specialized FPGA display IP core, implying niche industrial/embedded deployments rather than broad new-volume adoption. No natural in-tree replacement covers the same vendor-specific IP block, so removal is not justified; annotate as niche/low-deployment instead.