linux-drivers/
drivers/pmdomain/ti

Texas Instruments OMAP, Sitara, and K3 power-domain controllers

Power-domain controllers on Texas Instruments application processors, covering older OMAP4/5, DRA7, and AM3/AM4 Sitara chips as well as newer K3-generation parts like the AM62x and AM65x. These SoCs are common in industrial controllers, automotive infotainment, and embedded Linux gear from the early 2010s through parts TI still ships new today.

keep conf=0.92 deploy=medium replacement=none subsystem=pmdomain category=power-management
92%

recommendation

It should stay because the code drives power domains on TI processors that are still actively sold in 2025, including the AM625, AM3358, and AM5728 used in industrial and embedded systems. Upstream patches were still being reviewed and merged in mid-to-late 2025, so this is living, maintained code with a real install base rather than a legacy fragment.

repository signals

4 files
1,321 source lines
16 commits, 5y
+1,370 / −24 lines added / removed, 5y
11 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 16 total · active in 10/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: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 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: 3 commits · +1,225 −3 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 1 commit · +2 −0 2024-02: 1 commit · +1 −1 2024-03: 0 commits · +0 −0 2024-04: 1 commit · +19 −1 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: 0 commits · +0 −0 2024-10: 3 commits · +11 −14 2024-11: 0 commits · +0 −0 2024-12: 3 commits · +81 −0 2025-01: 1 commit · +1 −1 2025-02: 0 commits · +0 −0 2025-03: 1 commit · +6 −2 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 1 commit · +1 −1 2025-08: 0 commits · +0 −0 2025-09: 1 commit · +23 −1 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: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. spinics.net

    July 15, 2025 patch thread shows active upstream maintenance of drivers/pmdomain/ti Kconfig for TI PM domains, and it was applied for next.

  2. patchew.org

    September 2025 RFC v2 discusses functional TI SCI power-domain behavior, indicating ongoing development rather than retirement.

  3. ti.com

    TI lists AM625 as ACTIVE and orderable, showing current K3/Sitara deployments still map to this driver family.

  4. ti.com

    TI lists AM3358 as ACTIVE, showing the older AM3/OMAP-derived PRM-backed side is still sold for embedded use.

  5. ti.com

    TI lists AM5728 as ACTIVE, supporting continued DRA7/OMAP5-class deployment relevance.

codex reasoning notes (technical)

Shell inspection of local source showed this directory contains real platform/genpd drivers (`omap_prm.c`, `ti_sci_pm_domains.c`) covering `ti,omap4/5`, `ti,dra7`, `ti,am3/4`, and `ti,sci-pm-domain`; local `git log` also showed substantive fixes in 2024-2025 from many authors. Web `search_query` found 2025 Spinics and Patchew patch threads for this exact area, with active review/application and no removal discussion found in the searched results. Web `search_query` also found TI product pages marking AM625, AM3358, and AM5728 ACTIVE in 2025, so this is not legacy-only hardware. Mixed old+current embedded/industrial deployments justify `keep`, not deprecate/remove.