drivers/clk/sprd

Spreadtrum/UNISOC SC9860, SC9863A, and UMS512 SoC clock controllers

Clock tree controllers for Spreadtrum/UNISOC mobile SoCs, specifically the SC9860, SC9863A, and UMS512 chips that power budget Android phones and tablets from the late 2010s through products still sold in 2025. They gate and divide the reference clocks every other on-chip block depends on.

keep conf=0.86 deploy=low replacement=none subsystem=clk category=infrastructure
86%

recommendation

It should stay in the kernel because UNISOC still actively sells these mobile SoCs in 2025 and the directory continues to receive upstream maintenance. The clocks are also a hard prerequisite for community projects like postmarketOS to bring up phones built on UMS512 and SC9863A, and there is no generic replacement since clock trees are SoC-specific.

repository signals

17 files
7,380 source lines
18 commits, 5y
+2,304 / −84 lines added / removed, 5y
13 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 18 total · active in 15/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: 0 commits · +0 −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: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 1 commit · +5 −4 2022-08: 0 commits · +0 −0 2022-09: 1 commit · +2,209 −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: 1 commit · +2 −0 2023-03: 2 commits · +7 −4 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +11 −5 2023-06: 1 commit · +3 −25 2023-07: 1 commit · +3 −3 2023-08: 1 commit · +1 −1 2023-09: 1 commit · +42 −17 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: 1 commit · +1 −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: 1 commit · +3 −3 2025-08: 2 commits · +12 −9 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 1 commit · +2 −6 2025-12: 0 commits · +0 −0 2026-01: 1 commit · +1 −5 2026-02: 2 commits · +2 −2 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. git.kernel.org

    Upstream Linux contains dedicated Spreadtrum/UNISOC clock driver code here, including SoC-specific drivers for SC9860, SC9863A, and UMS512.

  2. git.kernel.org

    The directory has continued upstream maintenance in recent kernel history rather than being abandoned or staged for removal.

  3. unisoc.com

    UNISOC still markets SC9863A on its current product site, indicating the supported hardware family remained commercially relevant into 2025.

  4. unisoc.com

    UNISOC still markets S512/UMS512 on its current product site, covering another SoC family handled by this driver directory.

  5. wiki.postmarketos.org

    A 2025 postmarketOS device page reports UMS512-based hardware with basic/mainline support, showing at least niche present-day Linux deployments.

codex reasoning notes (technical)

Real driver directory: local shell inspection found `module_platform_driver()` in `sc9860-clk.c`, `sc9863a-clk.c`, and `ums512-clk.c`. Kernel tree/log URLs are canonical recall of stable kernel.org pages. UNISOC product URLs were obtained via web search and show the hardware family is still sold/marketed. The postmarketOS URL was obtained via web search and supports `deployments_today=low` rather than none. `replacement_driver` is null because these are SoC-specific clock controllers with no generic successor driver. Lore file-timeline on the directory prefix returned no indexed events, so I relied on the provided recent-touch stats plus kernel.org history rather than treating that as evidence of obsolescence.