Imagination E5010 JPEG hardware encoder
A hardware JPEG encoder IP block from Imagination Technologies that offloads still-image compression from the CPU. It is integrated into recent Texas Instruments embedded application processors such as the AM62Ax and AM67A Jacinto family, which target camera, vision, and edge-AI products shipping in the mid-2020s.
recommendation
It should stay because this is a freshly upstreamed driver (first landed in mid-2024, with active maintenance into late 2025) for a JPEG encoder block that Texas Instruments currently ships on its AM62Ax and AM67A embedded SoCs. TI's own current Processor SDK documentation lists it as enabled by default, so the hardware is being sold and deployed new in 2025, even if the overall install base is small and embedded-specific.
repository signals
sources
- git.kernel.org
Upstream Linux directory is a dedicated Imagination E5010 JPEG encoder driver, not a helper library or test asset.
- software-dl.ti.com
TI's current AM62Ax Processor SDK documents the E5010 JPEG encoder driver as enabled by default and describes active supported features and validation flows.
- software-dl.ti.com
TI's AM67A SDK documents the same E5010 JPEG encoder IP and upstream driver support, indicating ongoing deployment on current TI SoCs.
codex reasoning notes (technical)
Keep: this is a very new upstream driver (first touch 2024-06-24 from provided metadata) with recent substantive maintenance through 2025-10-17, which is inconsistent with obsolescence. TI SDK docs obtained via web search show the block on current AM62Ax and AM67A platforms and describe default-enabled/support status, so hardware is still sold in 2025 but in a niche embedded-media segment, hence deployments_today=low. No natural in-tree replacement exists because this is a hardware-specific V4L2 M2M encoder driver. Source acquisition: 2 TI URLs via web search; kernel.org tree URL via canonical recall. Lore-first shell query was attempted with `lei`, but the tool was unavailable in this environment, so upstream-activity judgment relies on the provided commit-history metadata instead of direct lore results.