Socionext UniPhier SoC PHY controllers
On-chip PHY blocks (PCIe, USB, and AHCI/SATA serial-link transceivers) built into Socionext's UniPhier system-on-chip family, including the LD20, PXs2/PXs3, Pro4/Pro5, and NX1 parts used in Japanese set-top boxes and embedded gear from the mid-2010s onward.
recommendation
Worth keeping but documenting its niche, because the UniPhier SoC family it supports is still maintained in current kernels yet appears to no longer be a growth product line for Socionext, whose current marketing focuses on custom SoCs and radar sensors instead. There are no signs of an upstream removal effort, and because these PHY blocks are baked into specific UniPhier chips, no other driver could replace them for existing boards still in the field.
repository signals
sources
- cateee.net
The directory serves the Socionext UniPhier SoC family, which remains supported in current kernel releases.
- cateee.net
The PCIe PHY driver is still present through current kernels and covers UniPhier LD20/PXs3/Pro5/NX1-compatible PHYs.
- cateee.net
The AHCI PHY driver is still present through current kernels and covers UniPhier Pro4/PXs2/PXs3 PHYs.
- socionext.com
Socionext's current public product lineup highlights newer radar/ASSP products rather than UniPhier application SoCs, suggesting UniPhier is not a current growth family.
- socionext.com
Socionext's current business positioning emphasizes custom SoCs and newer markets rather than marketing UniPhier as a current flagship family.
codex reasoning notes (technical)
Real driver directory: local shell inspection of Kconfig and .c files showed module_platform_driver entries and UniPhier PHY compatibles. Chipset family derived from local source plus LKDDb pages. lore_file_timeline(path="drivers/phy/socionext/") via lore-http returned no events and a follow-up lore regex for diff headers also returned no hits, so I found no direct lore evidence of an active removal series; given the user-provided substantive touch date in 2026, I treated the driver as maintained but quiet. Web search produced LKDDb URLs confirming the configs remain in current kernels, and current Socionext product/about pages do not surface UniPhier products, which supports 'low' present-day deployment and likely-not-sold-new inference. No natural replacement driver exists because these are SoC-specific PHY blocks.