drivers/cache

SoC last-level cache controllers for RISC-V and Arm platforms

A small collection of cache-maintenance controllers found on modern systems-on-chip, including SiFive's L2/L3 composable cache, StarFive's StarLink cache, Andes' AX45MP, and HiSilicon's HHA. They handle flushing, invalidation, and error reporting for the shared last-level cache on boards like the HiFive Premier P550, StarFive VisionFive 2, and Renesas RZ/Five.

keep conf=0.84 deploy=low replacement=none subsystem=cache category=infrastructure
84%

recommendation

It should stay because the code is young, actively maintained, and tied to RISC-V and Arm SoCs that vendors are still selling new in 2025 — SiFive's HiFive Premier P550, StarFive's JH7110 boards, and Renesas RZ/Five parts with longevity guaranteed through 2033. Recent commits and new hardware enablement keep landing, and there is no sign upstream of any move to retire it.

repository signals

6 files
893 source lines
15 commits, 5y
+1,001 / −45 lines added / removed, 5y
11 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 15 total · active in 11/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: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 1 commit · +227 −0 2023-09: 0 commits · +0 −0 2023-10: 3 commits · +341 −4 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 1 commit · +4 −0 2024-03: 1 commit · +46 −26 2024-04: 1 commit · +1 −1 2024-05: 1 commit · +142 −2 2024-06: 0 commits · +0 −0 2024-07: 1 commit · +1 −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: 1 commit · +2 −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: 1 commit · +4 −4 2025-10: 0 commits · +0 −0 2025-11: 2 commits · +229 −4 2025-12: 0 commits · +0 −0 2026-01: 2 commits · +4 −4 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. sifive.com

    SiFive lists the HiFive Premier P550 as 'Available Now' and sells a current board based on an ESWIN EIC7700X SoC with SiFive P550 cores, indicating current hardware using this driver family remains on the market.

  2. renesas.com

    Renesas marks RZ/Five as Active with product longevity to 2033 and identifies it as using an Andes AX45MP core, supporting that AX45MP-based deployments are still current.

  3. doc-en.rvspace.org

    StarFive documentation presents JH7110 as a current SoC and ties it to VisionFive 2, supporting ongoing StarFive platform relevance for the cache driver family.

  4. cateee.net

    LKDDb shows CONFIG_SIFIVE_CCACHE in current kernels and maps it to active compatible strings including ESWIN EIC7700 and StarFive JH7100-related hardware.

  5. cateee.net

    LKDDb shows CONFIG_STARFIVE_STARLINK_CACHE present in current kernels (6.11-6.19 and 7.0-rc+HEAD), indicating ongoing upstream support rather than retirement.

codex reasoning notes (technical)

Real driver directory: local `exec_command` inspection found four driver objects and platform-driver/module registrations in `drivers/cache/*.c`. Local `git -c safe.directory=... log -- drivers/cache` showed substantive commits through 2026-02-06 across multiple files/authors, with recent fixes and new hardware enablement, so upstream activity is current. Lore-specific tools were unavailable here (`lei` missing; web lore queries returned no indexed removal/deprecation thread), so I treated the absence of removal evidence plus recent git activity as a strong signal against deprecation. URLs were obtained via `web.search_query`/`web.open`; kernel support URLs show configs still present in current kernels, and vendor pages show relevant SiFive/StarFive/Andes-based hardware still shipping. Recommendation is `keep` because the code is young, recently maintained, and still tied to new-niche embedded/RISC-V/server deployments rather than abandoned legacy hardware.