SoC reset controller framework and drivers
A generic kernel framework, plus around four dozen vendor-specific drivers, that lets system-on-chip platforms assert and release the reset lines feeding individual hardware blocks (USB controllers, Ethernet MACs, GPUs, and so on). It is used by virtually every modern ARM, RISC-V, and FPGA-SoC platform Linux runs on, from Renesas and Rockchip silicon to Microchip's PolarFire SoC.
recommendation
It should stay because this is an actively maintained framework that lets dozens of modern SoCs (including Microchip's PolarFire SoC and many ARM, Renesas, and other vendors' parts still shipping in 2025) bring individual hardware blocks in and out of reset. The core code was still receiving functional changes and API additions in 2026, and roughly 47 vendor-specific reset drivers live alongside it.
repository signals
sources
- lore.kernel.org
Core reset framework code was still receiving functional changes in April 2026 ('reset: use a shared SRCU domain for reset controls').
- lore.kernel.org
The subsystem was still seeing API expansion RFC work in April 2026 ('reset: Add reset_controller_get_provider()').
- docs.kernel.org
The kernel documents reset controllers as a generic framework used by reset-controller providers and consumers across the kernel.
- microchip.com
A current Linux-capable SoC family (PolarFire SoC / MPFS, which has a driver in this directory) is still marketed with current product and kit offerings.
codex reasoning notes (technical)
This is a real driver subsystem, not a helper library: local shell inspection showed 47 reset-controller driver .c files plus a maintained framework entry in MAINTAINERS. Both lore URLs came from `lore_file_timeline` on `drivers/reset/core.c`, which showed heavy 2024-2026 activity and recent functional work rather than retirement. The kernel docs URL was obtained by web search to confirm the directory is an active generic reset-controller framework, not legacy one-off code. The Microchip URL was obtained by web search as present-day deployment evidence for shipping hardware covered by this directory (e.g. MPFS/PolarFire SoC via `reset-mpfs.c`). Given active upstream development, many maintained vendor-specific drivers, and ongoing new SoC deployments, this should be kept.