drivers/media/platform/samsung/s5p-jpeg

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.

keep-annotate conf=0.81 last_sold=2016 deploy=low replacement=none subsystem=media category=media-other
81%

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

11 files
5,315 source lines
20 commits, 5y
+5,423 / −93 lines added / removed, 5y
17 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 20 total · active in 13/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 1 commit · +0 −2 2022-02: 0 commits · +0 −0 2022-03: 2 commits · +5,382 −1 2022-04: 1 commit · +0 −1 2022-05: 1 commit · +1 −1 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 2 commits · +3 −5 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +1 −11 2023-06: 0 commits · +0 −0 2023-07: 1 commit · +1 −3 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 1 commit · +1 −1 2024-10: 2 commits · +11 −8 2024-11: 1 commit · +0 −29 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 4 commits · +21 −22 2025-09: 0 commits · +0 −0 2025-10: 1 commit · +0 −7 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 2 commits · +2 −2 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. git.kernel.org

    The driver still received non-mechanical upstream maintenance in October 2025.

  2. git.kernel.org

    The driver still received non-mechanical upstream maintenance in August 2025.

  3. 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.