Renesas R-Mobile, R-Car, and RZ SoC system-controller power domains
Power-domain controllers built into Renesas system-on-chip processors — the R-Mobile and R-Car families used in cars and infotainment, and the RZ family used in industrial gear — that switch CPU cores, GPUs, and peripheral blocks on and off to save power. The code covers chips spanning roughly 2010 through current Gen4 R-Car and RZ parts shipping in 2025.
recommendation
It should stay in the kernel because Renesas still ships these SoCs for new automotive and industrial designs, with parts like the RZ/G2L promised in production through 2037 and the R-Car V4H recently selected for Toyota's RAV4 ADAS module. Upstream history shows steady 2024-2025 maintenance and new SoC additions, with no sign of a replacement subsystem.
repository signals
sources
- git.kernel.org
Upstream file history shows this directory is actively maintained rather than abandoned; recent work includes functional PM-domain behavior changes and new SoC support.
- git.kernel.org
Current upstream tree contains many Renesas SYSC implementations spanning older R-Mobile/R-Car parts through newer Gen4 devices, indicating ongoing platform coverage.
- renesas.com
Renesas lists RZ/G2L as Active with product longevity through 2037, showing hardware in this driver family is still sold for new designs.
- renesas.com
Renesas lists R-Car V4H as an active automotive SoC, supporting continued relevance of newer R-Car SYSC support.
- renesas.com
A February 24, 2026 Renesas newsroom post says R-Car V4H was selected for a Toyota RAV4 ADAS control unit, evidencing contemporary deployment of supported SoCs.
codex reasoning notes (technical)
Real driver directory, not helpers/docs: local code inspection via shell `rg` showed SYSC generic-pm-domain provider code and many SoC-specific implementations. Local `git -c safe.directory=... log` showed substantive 2024-2025 maintenance/add-support commits; local `git log --grep='remove|deprecat'` found no removal/deprecation trend. I could not access lore MCP here, so upstream-activity URLs are kernel.org canonical-recall log/tree pages, with commit evidence cross-checked by local shell git. Renesas product/deployment URLs were obtained by web search. Because supported SoCs are still active in industrial/automotive lines and there is no natural replacement for these SoC-specific PM-domain providers, the right call is keep.