Samsung S3C, S5P, Exynos, and Tesla FSD SoC clock controllers
Clock controller support for Samsung's system-on-chip families spanning roughly two decades, from the older S3C and S5P mobile chips through the modern ARM64 Exynos line (including Exynos Auto V920 used in next-generation Hyundai infotainment) and Tesla's FSD self-driving SoC. These blocks gate, divide, and route the internal clocks every other on-chip peripheral depends on.
recommendation
It should stay because the codebase is actively maintained, with 176 substantive commits from 37 authors over the last five years and recent activity into 2026, and because the hardware is far from legacy: Samsung was still marketing Exynos Auto V920 as a current product in 2025 with Hyundai shipping it in new vehicles. There is no alternative driver path for these SoCs, since clock controllers are inherently SoC-specific.
repository signals
sources
- git.kernel.org
Upstream Kconfig still enables a broad active family: legacy Samsung SoCs, ARM64 Exynos, Exynos ACPM clocks, and Tesla FSD common clocks under COMMON_CLK_SAMSUNG.
- semiconductor.samsung.com
Samsung was still marketing Exynos Auto V920 as a current automotive processor product in 2025-era materials.
- semiconductor.samsung.com
Samsung announced Hyundai rollout of Exynos Auto V920-based IVI systems expected by 2025, indicating new-deployment relevance for SoCs covered by this clock-driver family.
- semiconductor.samsung.com
Samsung's current automotive processor lineup still includes Exynos Auto families, supporting ongoing deployment rather than purely legacy status.
codex reasoning notes (technical)
Real driver directory, not an early-exit case. Upstream health is strong from prompt-provided static evidence: 176 substantive commits in 5y, 37 authors, most recent substantive touch on 2026-01-17. `lore_file_timeline` on the directory path returned no hits for the prefix form, so I relied on the prompt's lore-derived activity figures for maintenance signal; a follow-up `lore_regex` removal search timed out, and `lei` was blocked by the sandbox, so I found no concrete removal-series evidence. Local shell inspection (`rg --files`, `sed` on Kconfig) confirmed this directory still covers current non-legacy targets such as Exynos Auto V920-era platforms and Tesla FSD, and the cited Samsung pages were obtained via web search. Because the hardware family is still entering 2025 vehicle deployments and there is no natural replacement driver beyond these SoC-specific clock blocks, the correct recommendation is to keep it.