Samsung Exynos 5 G-Scaler video scaler and color-space converter
A hardware video scaler and color-space conversion block built into Samsung's Exynos 5250, 5420, and 5433 mobile processors, used in Galaxy-era tablets and phones such as the Galaxy Note 10.1 (2014) and Galaxy Note 4. It offloads image resizing and pixel-format conversion from the CPU for camera and video pipelines.
recommendation
Worth keeping but documenting its niche: the silicon ships only in early-to-mid 2010s Samsung mobile devices that are long out of production, yet the code is still being actively maintained upstream, with a substantive fix landing as recently as August 2025. There is no removal effort in flight, and only one legacy device-tree compatible string is marked deprecated, not the driver itself, so it should remain available for the hobbyist and postmarketOS users keeping these handsets and tablets running.
repository signals
sources
- git.kernel.org
The driver received a substantive upstream fix on 2025-08-13 ('media: exynos-gsc: Access v4l2_fh from file'), so it is not abandoned.
- git.kernel.org
The driver matches Samsung Exynos 5250/5420/5433 G-Scaler blocks, and only the legacy fallback DT compatible 'samsung,exynos5-gsc' is marked deprecated, not the driver itself.
- cateee.net
LKDDb shows CONFIG_VIDEO_SAMSUNG_EXYNOS_GSC is still present in current kernels and binds samsung,exynos5250-gsc, samsung,exynos5420-gsc, samsung,exynos5433-gsc, and samsung,exynos5-gsc.
- en.wikipedia.org
Exynos 5420 deployments were in products launched in 2013, indicating this driver serves older mobile/tablet hardware rather than current products.
- en.wikipedia.org
Exynos 5433 deployments were in products launched in 2014 and later discontinued, reinforcing that present-day use is legacy.
codex reasoning notes (technical)
Local shell inspection identified the block as Samsung EXYNOS5 SoC G-Scaler and exposed supported DT compatibles plus the in-code message that only 'exynos5-gsc' is deprecated. MCP lore tooling was unavailable here and `lei` was not installed, so upstream activity was checked via local `git log`; the cited kernel.org commit URL was constructed from that local hash using canonical kernel.org commit URL form. Web search obtained the LKDDb page and device-market pages. Conclusion: legacy hardware with low current deployment, but still seeing upstream maintenance and no concrete removal evidence, so keep the driver with annotation rather than deprecate/remove.