drivers/soc/ti

Texas Instruments Sitara, Keystone, and K3 SoC support blocks

Support code for Texas Instruments ARM-based systems-on-chip, including Keystone, AM335x/AMx3 Sitara, the newer K3 generation such as AM62x, the Programmable Real-time Unit subsystem (PRUSS), and the SmartReflex voltage controller. These chips are widely used in industrial automation, robotics, and embedded gear from the BeagleBone era through products still shipping in 2025.

keep conf=0.90 deploy=medium replacement=none subsystem=soc category=platform-vendor
90%

recommendation

It should stay because the hardware is still actively sold by TI, including current Sitara AM62x parts and starter kits as well as long-lived AM335x modules that remain orderable for industrial use. Upstream development is also clearly alive, with feature work like a 2026 reset-reason addition to the K3 SoC info driver landing recently, so there is no path toward removal.

repository signals

14 files
8,631 source lines
118 commits, 5y
+1,130 / −1,885 lines added / removed, 5y
56 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 118 total · active in 43/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 3 commits · +3 −7 2021-07: 0 commits · +0 −0 2021-08: 3 commits · +25 −32 2021-09: 1 commit · +15 −12 2021-10: 1 commit · +1 −1 2021-11: 1 commit · +3 −2 2021-12: 9 commits · +55 −91 2022-01: 2 commits · +9 −8 2022-02: 1 commit · +1 −0 2022-03: 4 commits · +24 −31 2022-04: 8 commits · +134 −16 2022-05: 2 commits · +79 −2 2022-06: 2 commits · +2 −9 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 1 commit · +0 −4 2022-10: 3 commits · +30 −32 2022-11: 6 commits · +8 −9 2022-12: 1 commit · +7 −0 2023-01: 1 commit · +3 −2 2023-02: 0 commits · +0 −0 2023-03: 4 commits · +9 −10 2023-04: 6 commits · +350 −5 2023-05: 2 commits · +2 −2 2023-06: 1 commit · +4 −3 2023-07: 4 commits · +10 −1,219 2023-08: 2 commits · +7 −13 2023-09: 8 commits · +14 −36 2023-10: 4 commits · +62 −24 2023-11: 0 commits · +0 −0 2023-12: 1 commit · +2 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 1 commit · +2 −5 2024-04: 0 commits · +0 −0 2024-05: 1 commit · +2 −2 2024-06: 2 commits · +4 −4 2024-07: 3 commits · +11 −28 2024-08: 4 commits · +168 −186 2024-09: 3 commits · +4 −6 2024-10: 1 commit · +9 −9 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 1 commit · +12 −1 2025-02: 0 commits · +0 −0 2025-03: 4 commits · +14 −18 2025-04: 2 commits · +3 −2 2025-05: 1 commit · +3 −5 2025-06: 0 commits · +0 −0 2025-07: 1 commit · +1 −1 2025-08: 1 commit · +1 −1 2025-09: 1 commit · +10 −0 2025-10: 0 commits · +0 −0 2025-11: 3 commits · +9 −9 2025-12: 0 commits · +0 −0 2026-01: 6 commits · +16 −36 2026-02: 2 commits · +2 −2 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Upstream activity is current: March 2026 patch adds reset-reason support to `k3-socinfo`, indicating ongoing feature work rather than removal.

  2. ti.com

    TI still markets current Sitara processors in the AM62x family and associated starter kits, showing the SoC family served by this directory remains in active sale/use.

  3. ti.com

    An AM335x-based module was still listed as orderable on TI's site in recent crawl data, supporting continued legacy/industrial deployment of older Sitara parts also covered here.

codex reasoning notes (technical)

`drivers/soc/ti` is real driver code: local `rg` plus `Kconfig`/`Makefile` inspection via shell showed Keystone, AMx3, K3, PRUSS, and SmartReflex support blocks. Obtained `https://lore.kernel.org/linux-devicetree/20260316070429.1545707-4-alexander.sverdlin@siemens.com/` via `lore_activity(file=drivers/soc/ti/k3-socinfo.c, since=5y)`, which showed fresh 2026 feature development; a parallel `lore_activity` on `pruss.c` also returned ongoing stable-tree traffic. Obtained the two TI URLs via web search on `ti.com`; they show both current Sitara AM62x products and still-orderable AM335x ecosystem hardware. This directory spans active TI SoC support IP used on still-sold embedded/industrial platforms, and there is no single upstream replacement driver for the same scope, so removal/deprecation is not indicated.