drivers/clk/uniphier

Socionext UniPhier SoC clock controllers

Clock controllers built into Socionext's UniPhier family of system-on-chip processors, used in smart TVs, set-top boxes, and other consumer media devices from the mid-2010s. The driver covers a range of UniPhier generations including LD4, Pro4, sLD8, Pro5, PXs2, LD11, LD20, PXs3, and NX1.

keep-annotate conf=0.68 deploy=low replacement=none subsystem=clk category=platform-vendor
68%

recommendation

Worth keeping but documenting its niche, because UniPhier was a legacy Socionext consumer-SoC line (heavily marketed for smart TVs around 2015) that is no longer pushed as a current product family, yet there is no replacement driver and no removal discussion upstream. Trusted Firmware-A still carries UniPhier platform support, suggesting some lingering deployments, so the driver should remain available for those users while its legacy status is noted.

repository signals

12 files
1,235 source lines
7 commits, 5y
+75 / −13 lines added / removed, 5y
4 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 7 total · active in 5/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: 3 commits · +70 −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: 1 commit · +1 −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: 1 commit · +2 −4 2023-04: 1 commit · +2 −8 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 1 commit · +0 −1 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 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: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 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. git.kernel.org

    Mainline Linux has a dedicated built-in platform clock driver for multiple Socionext UniPhier SoCs, with DT compatibles covering LD4/PRO4/SLD8/PRO5/PXS2/LD11/LD20/PXS3/NX1.

  2. trustedfirmware-a.readthedocs.io

    Trusted Firmware-A documents Socionext UniPhier Armv8-A SoCs and their boot flow, indicating the platform still has adjacent upstream firmware support.

  3. edn.com

    UniPhier was marketed into smart-TV/media SoCs in 2015, which points to a legacy consumer-SoC family rather than a currently promoted 2025 product line.

  4. socionext.com

    Socionext's current corporate/product messaging emphasizes custom SoCs and newer offerings; UniPhier is not presented as a current product family.

codex reasoning notes (technical)

Inspected local files with exec_command/rg: this is real driver code, not helpers, and it binds many UniPhier clock compatibles. lore_file_timeline on the directory path returned no events; a representative-file lore timeline was dominated by U-Boot, and no Linux-kernel removal discussion was found from the lore checks, so I treated upstream removal evidence as absent. The kernel.org URL is canonical recall corresponding to the locally inspected file. TF-A and vendor/product URLs were obtained via web search. Recommendation is keep-annotate: low recent Linux churn and likely legacy deployments, but no natural replacement driver and no concrete removal push.