Samsung S5P and Exynos hardware JPEG codec
A hardware JPEG encoder/decoder block built into Samsung's S5P and early Exynos mobile application processors from roughly 2010 to 2014, including the Exynos 3250, 4210/4212, 5420, and 5433 found in phones like the Galaxy Note 4 and Gear-series wearables. It offloads JPEG compression and decompression from the CPU for camera and image-viewer workloads on those SoCs.
recommendation
Worth keeping but flagging as legacy: the SoCs it supports stopped shipping in new devices a decade ago and remaining users are owners of old Samsung phones and wearables, yet the code still received genuine bug-fix work as recently as August and October 2025. That ongoing upstream attention means removal would be premature, but a note marking it as a driver for obsolete 2010–2014 Samsung mobile silicon would help future maintainers gauge how much effort it deserves.
repository signals
sources
- git.kernel.org
The driver still received non-mechanical upstream maintenance in October 2025.
- git.kernel.org
The driver still received non-mechanical upstream maintenance in August 2025.
- en.wikipedia.org
Supported SoCs tied to this driver are old Samsung S5P/Exynos parts: Exynos 5420 released Q3 2013, Exynos 5433 Q4 2014, and Exynos 3250 Q2 2014, used in legacy devices such as Galaxy Note 4 and Gear-class wearables.
codex reasoning notes (technical)
Real driver: local shell inspection of Kconfig and jpeg-core.c shows a V4L2 mem2mem platform driver with DT compatibles for samsung,s5pv210-jpeg, exynos3250-jpeg, exynos4210/4212-jpeg, exynos5420-jpeg, and exynos5433-jpeg. Local shell git log showed substantive touches in 2025-2026 and no obvious removal subject lines, so this does not look abandoned upstream; cited commit URLs are canonical recall for the public git.kernel.org commit pages corresponding to those local-shell commits. Web open on Wikipedia Exynos (via web search/open) showed all supported SoCs are 2010-2014 era mobile/wearable parts, implying no meaningful new-hardware sales by 2025 and only low legacy deployments today. Because hardware is obsolete but upstream bug-fix traffic still exists, keep the driver but annotate it as legacy rather than deprecate/remove.