A kernel-wide framework and collection of vendor drivers for PHYs, the analog/mixed-signal transceivers that sit between a digital controller and the physical wires for USB, PCIe, SATA, UFS, eMMC, MIPI and similar high-speed links. It is used by virtually every modern ARM SoC and many x86 platforms to bring up Type-C ports, NVMe and SATA storage, display and camera links, and other serial buses.
It should stay because this is a core, actively maintained subsystem rather than a legacy chip driver. New PHY drivers were still landing upstream in 2026 (for example EcoNet EN751221/EN7528 PCIe and Axiado AX3000 eMMC), and current shipping silicon like Rockchip's RK3588 depends on it for USB, PCIe, SATA and Type-C support.
repository signals
359files
146,435source lines
1,606commits, 5y
+120,918 / −54,325lines added / removed, 5y
330authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 1,606 total · active in 59/61 months
As of April 4, 2026, the subsystem was still gaining new upstream PHY driver support (EcoNet EN751221/EN7528 PCIe PHY), indicating active development rather than retirement.
Rockchip still markets RK3588 with Linux support and high-speed interfaces including PCIe, SATA, Type-C, USB3.1 and USB2.0, all of which rely on PHY drivers from this subsystem.
Axiado's current products page still lists active TCU SoCs in 2025/2026-era offerings, supporting the conclusion that related PHY-backed hardware remains in new deployments.
codex reasoning notes (technical)
`drivers/phy` is an active subsystem directory, not a single obsolete chip driver: local `rg`/tree inspection showed many vendor PHY drivers plus the generic PHY framework. Upstream activity was checked with `mcp__lore_http__.lore_file_timeline` on `drivers/phy/Kconfig`, which showed heavy 2025-2026 traffic and recent new-driver additions; no removal evidence was found in the sampled lore results. Deployment evidence came from `web.search_query` hits for Rockchip RK3588 and Axiado current product pages, both showing currently marketed Linux-capable hardware using PHY-managed links. Because this directory covers current SoCs across multiple vendors and is still receiving enablement work, the correct disposition is keep.