Samsung Exynos 4210 and 5433 power-domain controllers
On-chip power-domain controllers built into Samsung's Exynos 4210 (2011) and Exynos 5433 (2014) mobile application processors, used to gate power to GPU, multimedia, and other SoC blocks in phones and tablets like the Galaxy S II era and the Galaxy Note 4 generation.
recommendation
Worth keeping but documenting as legacy-specific, because the supported Exynos 4210 and 5433 chips are roughly a decade old and no longer shipping in new products, yet upstream maintainers were still landing fixes as recently as July and October 2025. The hardware lives on in postmarketOS and other mainline-mobile community ports, so removing it would hurt those niche users without much cleanup benefit.
repository signals
sources
- cateee.net
CONFIG_EXYNOS_PM_DOMAINS is a current upstream kernel option for this directory and LKDDb associates it with samsung,exynos5433-pd and drivers/pmdomain/samsung/exynos-pm-domains.c.
- wiki.postmarketos.org
Exynos5433 remains at least somewhat supported in current mainline-oriented mobile Linux communities, indicating niche ongoing deployments rather than zero use.
- en.wikichip.org
Exynos4210 is a mobile SoC introduced in 2011, placing one supported hardware target firmly in legacy-era products.
- en.wikichip.org
Exynos5433 is a mobile SoC introduced in 2014, placing the other supported hardware target in older phone/tablet generations.
codex reasoning notes (technical)
Local shell inspection of exynos-pm-domains.c shows only two DT compatibles (samsung,exynos4210-pd and samsung,exynos5433-pd) and a real platform-driver/core_initcall implementation. Local shell git log on this path shows substantive maintenance in 2025 (July, October twice) plus a 2023 subsystem move, with no evident removal-oriented history; that backs off any deprecation despite old hardware. URLs were obtained via web search tool for LKDDb, postmarketOS, and WikiChip pages. Net: hardware is legacy and not new in 2025, but upstream still fixes it for niche/mainline-mobile use, so keep the driver and annotate it as legacy-specific rather than deprecate or remove.