HiSilicon Hi3xxx SoC clock and reset controllers
Clock and reset controller support for a range of HiSilicon system-on-chip designs from the 2010s, including the Hi3660/Hi3670 used in HiKey960/970 developer boards, the Hi6220 in the original HiKey, and various Hi35xx/Hi37xx parts shipped in set-top boxes and IP cameras. These controllers gate and configure the clocks every other on-chip peripheral depends on.
recommendation
Worth keeping but its niche should be documented: the supported SoCs are older HiSilicon phone, STB, and CCTV generations no longer being designed into new products, but the directory still receives modest maintenance (around 17 commits in the last five years, with touches into 2026) and underpins community boards like HiKey960 that remain in developer hands. There is no upstream removal effort visible, so removal would be premature, but a note clarifying that these are legacy-platform clock drivers would help future readers.
repository signals
sources
- git.kernel.org
Upstream Kconfig shows this directory covers multiple HiSilicon SoC-specific clock drivers including HI3516CV300, HI3519, HI3559A, HI3660, HI3670, HI3798CV200, and HI6220, plus reset support.
- 96boards.org
HiKey960 documentation remains published, indicating at least residual developer-board deployment for a Hi3660/Hi3670-era platform.
- hisilicon.com
HiSilicon still markets newer STB chipsets in the same broad product area, implying the use-case persists even though the exact older CV200-era parts in this driver are not the current focus.
codex reasoning notes (technical)
Real driver directory: local shell inspection of Kconfig/Makefile showed platform clock/reset drivers, not helpers. lore_subsystem_churn(path:drivers/clk/hisilicon/) produced no lore-visible patch-mail churn or removal signal, and the prompt's own stats show 17 substantive commits in the last 5 years with a 2026-01-22 latest touch, so this does not look abandoned. The supported SoCs are older HiSilicon phone/STB/CCTV generations; current public evidence points to residual field use and dev-board presence rather than strong new-design momentum. Recommendation is keep-annotate, not deprecate/remove. URL provenance: git.kernel.org URL by canonical recall; 96Boards and HiSilicon URLs obtained via web search.