BSP Tracker / BSP Status / Texas Instruments
Video encode and decode work upstream, which is unusual. But AM62A exists to do camera and AI, and both pillars — the VPAC3L ISP and the 2-TOPS C7x/MMA accelerator — have no upstream driver. On mainline a smart camera becomes raw Bayer capture with software 3A and CPU inference.
Can you ship mainline instead, and what exactly do you lose if you do?
Mainline, with named losses
| Block | IP | Upstream | Detail |
|---|---|---|---|
| VPU | Chips&Media Wave5 | upstream | CONFIG_VIDEO_WAVE_VPU — stateful H.264/HEVC encode and decode, depends on ARCH_K3. |
| NPU | C7x DSP + MMA (2 TOPS) | missing | No TI entry in drivers/accel. TIDL is proprietary and BSP-only. |
| ISP | VPAC3L | missing | No ISP driver in drivers/media/platform/ti. CSI-2 capture works; hardware 3A/HDR does not. |
| GPU | none | n/a | AM62A is the vision/AI variant and has no 3D GPU. |
Repository. https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel
Newest branch that actually exists. ti-linux-6.18.y, tracking Linux 6.18. Last commit 2026-07-09.
Cadence. Same K3 branch set as AM62x, with PREEMPT_RT variants.
The vendor publishes no commitment. TI life-cycle policy only. No dated per-part commitment.
Layer. meta-ti. A branch for the current LTS exists: wrynose.
The third-party SoM ecosystem for AM62A is much thinner than for AM62x. That is itself a sourcing signal.
TI AM62A (AM62A7): upstream fixes stop December 2028. That leaves 29 months. After that date the kernel this BSP is based on receives no further security fixes from upstream, and maintaining it becomes your team’s responsibility.
There are three options:
All three are engineering work, and all three are work we do: reading vendor kernel trees, checking what mainline actually supports, and moving products from one to the other. This page is built from the same work.
An email when a kernel series reaches end of life, a board row changes, or a layer picks up a release branch. Nothing else.
RSS