drivers/gpu/drm/armada

Marvell Armada 510/16x SoC LCD display controllers

Drives the on-chip LCD display controllers found in Marvell's Armada 510 and 16x application processors, ARM SoCs Marvell launched around 2009 for smartbooks, tablets, thin clients, and display-centric embedded devices like the Dell/Wyse T10 and CompuLab CM-A510 module.

keep-annotate conf=0.67 deploy=low replacement=none subsystem=gpu category=graphics-display
67%

recommendation

Worth keeping but flagging as legacy because the underlying Marvell Armada 510 chips date from 2009-era smartbooks, tablets, and thin clients, yet the code still saw routine upstream maintenance through late 2024 and a few embedded modules (CompuLab's CM-A510) and Wyse T10 thin clients are still findable for sale. Active maintenance and lingering hardware availability mean removal would be premature, but its user base is small enough to deserve a "niche/legacy" note.

repository signals

20 files
4,109 source lines
51 commits, 5y
+262 / −361 lines added / removed, 5y
19 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 51 total · active in 28/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 3 commits · +1 −36 2021-07: 0 commits · +0 −0 2021-08: 1 commit · +3 −4 2021-09: 0 commits · +0 −0 2021-10: 1 commit · +2 −0 2021-11: 0 commits · +0 −0 2021-12: 2 commits · +3 −1 2022-01: 0 commits · +0 −0 2022-02: 1 commit · +3 −14 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 2 commits · +3 −0 2022-07: 3 commits · +3 −10 2022-08: 1 commit · +3 −3 2022-09: 0 commits · +0 −0 2022-10: 1 commit · +4 −4 2022-11: 3 commits · +4 −2 2022-12: 0 commits · +0 −0 2023-01: 1 commit · +2 −2 2023-02: 1 commit · +3 −0 2023-03: 4 commits · +127 −76 2023-04: 1 commit · +1 −1 2023-05: 1 commit · +3 −5 2023-06: 1 commit · +0 −2 2023-07: 3 commits · +6 −8 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +8 −0 2023-10: 1 commit · +7 −17 2023-11: 1 commit · +4 −6 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: 1 commit · +1 −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: 2 commits · +19 −114 2024-10: 0 commits · +0 −0 2024-11: 1 commit · +1 −1 2024-12: 3 commits · +3 −4 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: 4 commits · +18 −11 2025-08: 0 commits · +0 −0 2025-09: 2 commits · +2 −7 2025-10: 3 commits · +8 −13 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 2 commits · +20 −20 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. git.kernel.org

    Kconfig identifies this as DRM support for Marvell Armada SoCs and specifically the LCD controllers found on Marvell Armada 510 and 16x families.

  2. lore.kernel.org

    The driver directory was still seeing upstream touches in late 2024 as part of ongoing DRM subsystem refactoring, which argues against abandonment.

  3. investor.marvell.com

    Marvell introduced the Armada 510 in 2009 for smartbooks, tablets, thin clients, and display-oriented embedded devices, placing the hardware family firmly in an older generation.

  4. compulab.com

    CompuLab still publishes a CM-A510 module page built around the Marvell Armada 510, indicating lingering niche embedded availability/use.

  5. esaitech.com

    A Marvell Armada 510-based Wyse T10 thin client was recently listed in new condition and in stock, suggesting limited new-old-stock sales persisted into the mid-2020s rather than complete market disappearance.

codex reasoning notes (technical)

Real driver directory, not an early-exit case. Chipset scope came from local source inspection plus canonical-recall kernel.org Kconfig URL. Upstream activity evidence came from `lore_file_timeline` on `drivers/gpu/drm/armada/armada_drv.c`, which showed continuing 2021-2024 traffic; within the available tool budget I found no concrete removal/deprecation thread, and a `lei` follow-up failed due local socket permissions. Market-age evidence came from the Marvell launch PR found by web search; current deployment/sales evidence came from web search hits for CM-A510 and Wyse T10 pages. Conclusion: hardware is old and niche, but not extinct, and the driver still receives enough upstream maintenance that deprecation would be premature; annotate as legacy/niche rather than remove.