drivers/reset/starfive

StarFive JH7100 and JH7110 RISC-V SoC reset controllers

Handles the on-chip reset controllers inside StarFive's JH7100 and JH7110 RISC-V system-on-chip designs, which power affordable RISC-V single-board computers such as the VisionFive 2 and PINE64 STAR64 introduced from 2022 onward. The reset blocks are what bring individual SoC peripherals (USB, PCIe, networking, etc.) out of reset during boot and runtime power management.

keep conf=0.89 deploy=low replacement=none subsystem=reset category=platform-vendor
89%

recommendation

It should stay in the kernel because the StarFive JH7110 still ships in 2025 in popular RISC-V single-board computers like the VisionFive 2 and PINE64 STAR64, the driver is young (added in 2023), and it received a substantive bug fix as recently as September 2024 with no sign of any replacement or deprecation effort upstream.

repository signals

6 files
325 source lines
10 commits, 5y
+609 / −258 lines added / removed, 5y
6 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 10 total · active in 4/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: 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: 0 commits · +0 −0 2023-04: 7 commits · +574 −257 2023-05: 1 commit · +2 −1 2023-06: 0 commits · +0 −0 2023-07: 1 commit · +30 −0 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: 1 commit · +3 −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

    Canonical kernel log location for this directory; local `git log` on the same path shows the driver was added in 2023 and still received a substantive fix on 2024-09-25, with no local sign of deprecation/removal activity.

  2. cateee.net

    LKDDb shows CONFIG_RESET_STARFIVE_JH7110 exists in mainline kernels 6.4 through 6.19, indicating current upstream presence rather than retirement.

  3. starfivetech.com

    StarFive still markets VisionFive 2 hardware built on the JH7110 SoC, supporting the view that this driver targets hardware still sold new in 2025.

  4. pine64.com

    PINE64 lists the JH7110-based STAR64 SBC as in stock, giving current retail evidence of ongoing low-volume deployments.

codex reasoning notes (technical)

Local `sed` inspection confirmed this is real reset-controller driver code for StarFive JH7100/JH7110 SoCs, not helper-only code. Local `git -c safe.directory=... log -- drivers/reset/starfive` showed a young driver (introduced 2023) with a recent bug-fix on 2024-09-25; a local grep over git log found no remove/deprecate matches for this path. `web.search_query` obtained the cateee LKDDb page plus StarFive and PINE64 product pages. The kernel.org log URL was added by canonical recall as the stable upstream path anchor. Conclusion: hardware is still on sale, upstream support is current, deployments are niche rather than broad, and there is no natural replacement driver for the same reset blocks.