Texas Instruments Sitara, Jacinto, and K3 SoC PHY drivers
A collection of low-level PHY (physical-layer) drivers for the Ethernet, USB, PCIe, and SerDes interfaces built into Texas Instruments' Sitara, Jacinto, and K3 application processors, along with some older OMAP and DA8xx USB PHY support. These chips power industrial controllers, automotive infotainment and ADAS units, and embedded gateways shipping today.
recommendation
It should stay because TI is still actively shipping the Sitara AM64x and Jacinto TDA4VM/J721E processors that depend on these PHY blocks, and the directory is receiving real maintenance — including a phy-j721e-wiz bug fix in early 2026. TI continues to publish new Linux SDK releases for these SoCs, and there is no consolidated replacement since each PHY block is SoC-specific.
repository signals
sources
- git.kernel.org
Upstream path remains active in mainline rather than abandoned; recent history includes multiple 2024-2026 fixes and feature work in this directory.
- git.kernel.org
A real bug-fix landed on 2026-02-27 for phy-j721e-wiz, showing current maintenance attention.
- ti.com
AM6442 is listed by TI as ACTIVE and orderable; this family uses Ethernet/USB/PCIe PHY blocks covered by drivers in this directory and is a current Linux-capable deployment target.
- ti.com
TDA4VM is listed by TI as ACTIVE; Jacinto/K3 deployments continue to need j721e-wiz and related TI PHY support.
- ti.com
TI published current J721E Linux/QNX/RTOS SDK releases in 2026, indicating ongoing vendor enablement for SoCs served by this directory.
codex reasoning notes (technical)
Keep: this is an active TI PHY driver directory spanning current K3/Jacinto/Sitara SoCs plus some legacy OMAP/DA8xx USB PHY pieces, and local shell `git -c safe.directory=... log -- drivers/phy/ti` showed substantive 2024-2026 fixes/features with a latest non-merge fix on 2026-02-27. No removal signal was found: lore-http MCP was unavailable in this session, and web search against lore.kernel.org returned no removal/deprecation hits. Kernel.org log/commit URLs were added by canonical recall to anchor the local git evidence; TI product/SDK URLs were obtained via web search results (`turn2search0`, `turn2search1`, `turn0search0`). No single upstream replacement exists because these drivers are SoC-specific PHY/control blocks.