linux-drivers/
drivers/gpu/drm/omapdrm

TI OMAP2/3/4/5 Display Subsystem (omapdrm)

The display controller built into Texas Instruments' OMAP2, OMAP3, OMAP4, and OMAP5 application processors, which powered smartphones, tablets, BeagleBoard/PandaBoard hobbyist boards, and industrial panels from the mid-2000s through about 2013. It drives LCD panels, HDMI output, and DSI/DPI interfaces on those SoCs.

keep-annotate conf=0.78 last_sold=2013 deploy=low replacement=none subsystem=gpu category=graphics-display
78%

recommendation

Worth keeping but documenting its legacy status. The OMAP family is no longer sold for new designs — TI stepped back from the smartphone/tablet market in 2012 and the last OMAP5 parts shipped in 2013 — but the driver is still receiving real upstream attention, including DRM bridge and state-readout refactoring work as recently as 2026. It mostly serves long-lived BeagleBoard-class hobbyist boards and industrial deployments, so removal would hurt those users while maintenance cost remains modest.

repository signals

56 files
30,951 source lines
132 commits, 5y
+1,702 / −1,213 lines added / removed, 5y
46 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 132 total · active in 48/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 2 commits · +8 −3 2021-07: 4 commits · +4 −11 2021-08: 4 commits · +21 −105 2021-09: 0 commits · +0 −0 2021-10: 2 commits · +3 −1 2021-11: 10 commits · +935 −107 2021-12: 2 commits · +11 −8 2022-01: 4 commits · +124 −97 2022-02: 4 commits · +12 −18 2022-03: 1 commit · +1 −1 2022-04: 0 commits · +0 −0 2022-05: 1 commit · +1 −1 2022-06: 4 commits · +9 −0 2022-07: 2 commits · +3 −3 2022-08: 1 commit · +1 −3 2022-09: 2 commits · +19 −13 2022-10: 3 commits · +2 −9 2022-11: 5 commits · +5 −44 2022-12: 1 commit · +1 −1 2023-01: 2 commits · +3 −4 2023-02: 2 commits · +3 −1 2023-03: 0 commits · +0 −0 2023-04: 5 commits · +122 −92 2023-05: 3 commits · +21 −40 2023-06: 1 commit · +0 −2 2023-07: 5 commits · +26 −48 2023-08: 0 commits · +0 −0 2023-09: 2 commits · +12 −5 2023-10: 1 commit · +5 −4 2023-11: 1 commit · +10 −4 2023-12: 0 commits · +0 −0 2024-01: 2 commits · +21 −13 2024-02: 2 commits · +35 −7 2024-03: 2 commits · +1 −1 2024-04: 3 commits · +4 −3 2024-05: 0 commits · +0 −0 2024-06: 1 commit · +1 −1 2024-07: 2 commits · +2 −2 2024-08: 4 commits · +19 −34 2024-09: 3 commits · +67 −121 2024-10: 2 commits · +4 −161 2024-11: 1 commit · +1 −1 2024-12: 4 commits · +9 −29 2025-01: 2 commits · +4 −10 2025-02: 2 commits · +4 −6 2025-03: 1 commit · +12 −6 2025-04: 1 commit · +1 −1 2025-05: 6 commits · +42 −72 2025-06: 3 commits · +5 −8 2025-07: 3 commits · +9 −8 2025-08: 5 commits · +27 −29 2025-09: 1 commit · +1 −1 2025-10: 3 commits · +12 −10 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 4 commits · +58 −59 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    omapdrm was still receiving upstream code changes in April 2026, indicating active maintenance rather than abandonment.

  2. lore.kernel.org

    omapdrm core files were included in broader DRM subsystem work in April 2026, showing continuing integration work.

  3. git.kernel.org

    The in-tree Kconfig describes DRM_OMAP as the display driver for OMAP2/3/4 based boards, tying the driver to an older TI OMAP hardware generation.

  4. ti.com

    TI's notable late-family OMAP5432 industrial push dates to 2013, consistent with the family being legacy rather than a current-volume 2025 design win.

  5. en.wikipedia.org

    Wikipedia summarizes TI's 2012 retreat from smartphone/tablet OMAP and notes the last OMAP5 chips were released in Q2 2013, supporting an old/legacy market position.

codex reasoning notes (technical)

Lore evidence came from `lore_file_timeline` and `lore_activity` on drivers/gpu/drm/omapdrm/omap_drv.c; both showed fresh 2026 patches and no visible driver-removal series, so this is not a removal candidate. The Kconfig URL is a canonical kernel.org source-tree page recalled from stable project structure and used to anchor supported hardware scope. Deployment/market-age evidence came from web search results: TI's 2013 OMAP5432 announcement and the Wikipedia OMAP history page. Conclusion: hardware is legacy with low present-day deployment, but upstream attention is still real; keep the driver and annotate it as legacy rather than deprecate/remove.