StarFive JH7100 and JH7110 RISC-V SoC clock controllers
Clock controller support for StarFive's JH7100 and JH7110 RISC-V system-on-chip designs, which gate and dispatch clocks to the CPU cores and on-chip peripherals on RISC-V single-board computers such as the VisionFive and VisionFive 2 introduced from 2021 onward.
recommendation
It should stay in the kernel because it provides the clock tree for StarFive's JH7100 and JH7110 RISC-V SoCs, which power currently-shipping boards like the VisionFive 2 that StarFive was still selling and documenting into 2025. The code is actively maintained upstream, with functional fixes landing through January 2025 and no signs of a removal effort.
repository signals
sources
- git.kernel.org
Upstream kernel history for this directory shows regular non-removal activity, including functional StarFive clock changes in 2024-2025.
- git.kernel.org
The StarFive JH7100 clock generator driver was introduced by commit 4210be668a09 and is contained in v5.17, so this is a relatively recent, still-maturing SoC support line rather than legacy baggage.
- starfivetech.com
StarFive still markets VisionFive 2 around the JH-7110 SoC, with current product positioning and purchase flow, indicating hardware remained sold new in 2025.
- doc-en.rvspace.org
StarFive's VisionFive 2 Quick Start Guide dated 2025-01-06 documents the JH7110 board hardware, showing ongoing vendor documentation and deployment relevance.
codex reasoning notes (technical)
Local `rg` confirmed this is real kernel driver code for StarFive JH7100/JH7110 SoC clock blocks, not helper-only code. Local `git log` (with safe.directory override) showed substantive maintenance through 2025-01-14 plus multiple 2024 functional fixes; no local history suggested deprecation/removal. A `web.search_query` for lore removal/deprecation discussion returned no relevant results, so there is no visible active upstream removal push. Source URLs: the two kernel.org URLs are canonical recall of stable kernel git pages, while the StarFive/RVspace URLs were obtained via `web.search_query`. Since JH7110-based boards were still being marketed/documented in 2025 and the driver is seeing recent upkeep, the correct call is to keep it.