linux-drivers/
drivers/video/fbdev/omap2/omapfb/dss

TI OMAP2/3/4/5 Display Subsystem (OMAPDSS) framebuffer support

The display subsystem found on Texas Instruments OMAP2, OMAP3 (including 3630), OMAP4, and OMAP5 application processors, which drove LCD panels, DVI, and HDMI outputs on smartphones, tablets, set-top boxes, and embedded boards from roughly the mid-2000s through the mid-2010s, including BeagleBoard and Pandaboard development kits.

keep-annotate conf=0.76 last_sold=2016 deploy=low replacement=drivers/gpu/drm/omapdrm subsystem=video category=graphics-display
76%

recommendation

Worth keeping but worth flagging as legacy, because the same display hardware is also handled by the modern omapdrm DRM/KMS driver, which is the natural successor for new development. The fbdev version still receives occasional upstream cleanup work (a Thomas Zimmermann patch landed in June 2025), so it is not abandoned, but the hardware itself stopped appearing in mainstream designs around 2016 and remaining users are mostly embedded or industrial boards.

repository signals

39 files
27,068 source lines
33 commits, 5y
+174 / −345 lines added / removed, 5y
25 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 33 total · active in 21/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 1 commit · +1 −3 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 1 commit · +26 −26 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 1 commit · +6 −3 2022-02: 1 commit · +1 −7 2022-03: 0 commits · +0 −0 2022-04: 1 commit · +1 −7 2022-05: 0 commits · +0 −0 2022-06: 1 commit · +1 −1 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 1 commit · +12 −24 2022-10: 0 commits · +0 −0 2022-11: 1 commit · +0 −2 2022-12: 1 commit · +18 −10 2023-01: 1 commit · +10 −7 2023-02: 0 commits · +0 −0 2023-03: 2 commits · +19 −29 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −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: 1 commit · +9 −23 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 3 commits · +3 −19 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 2 commits · +3 −6 2024-10: 3 commits · +31 −127 2024-11: 0 commits · +0 −0 2024-12: 1 commit · +0 −18 2025-01: 3 commits · +4 −8 2025-02: 0 commits · +0 −0 2025-03: 2 commits · +7 −8 2025-04: 1 commit · +1 −1 2025-05: 0 commits · +0 −0 2025-06: 2 commits · +10 −2 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 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: 3 commits · +11 −14 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    The fbdev/omap2 DSS code still received upstream maintenance in June 2025, indicating it is not abandoned.

  2. git.kernel.org

    The fbdev DSS code targets legacy TI OMAP generations such as OMAP24xx, OMAP34xx/3630, OMAP4 and OMAP5.

  3. git.kernel.org

    Upstream has a DRM/KMS driver, DRM_OMAP, described as the display driver for OMAP2/3/4 based boards.

  4. git.kernel.org

    The DRM_OMAP driver builds its own `dss/` implementation, showing it is the natural upstream successor for the same display subsystem.

codex reasoning notes (technical)

Real driver directory: exec_command inspection found module/platform-driver code and SoC-specific DSS support. lore_file_timeline on `dss/core.c` showed 16 touches since 2023, latest 2025-06-12 (source URL obtained via `lore_file_timeline`), which argues against removal now. exec_command also showed fbdev Kconfig names OMAP4/OMAP5 HDMI support and `dss_features.c` enumerates OMAP2/3/4/5-era variants; the matching git.kernel.org URLs are canonical-recall mappings of the inspected local files. `drivers/gpu/drm/omapdrm` clearly covers the same DSS blocks, so replacement exists, but active 2025 maintenance means back off from deprecate/remove to keep-annotate. Hardware appears confined to legacy embedded/industrial boards rather than new mainstream designs, so present deployments are low and new-2025 sales are unlikely.