TI DaVinci VPIF video capture and display
The Video Port Interface (VPIF) block found on Texas Instruments DaVinci-family system-on-chips such as the TMS320DM6467, DA850, and OMAP-L138, used to capture and output standard-definition and HD video on embedded boards, digital signage, industrial vision systems, and video infrastructure gear from the late 2000s onward.
recommendation
Worth keeping but documenting its niche, because it serves a narrow set of older Texas Instruments DaVinci-era SoCs (DM6467, DA850, OMAP-L138) that TI still lists as active but mostly ship into long-lived industrial and embedded video designs. Recent upstream commits, including a 2025 display fix and a probe-path memory leak fix, show the code is still being maintained, and there is no replacement driver because VPIF is a SoC-specific block.
repository signals
sources
- git.kernel.org
The in-tree Kconfig says these drivers cover TI DM6467, DA850, and OMAPL138 SoCs.
- git.kernel.org
VPIF display received a substantive upstream fix in late 2025, showing the driver is still maintained rather than abandoned.
- git.kernel.org
VPIF core code received a real bug fix for a probe-path memory leak in the last few years.
- ti.com
TI still listed OMAP-L138 as ACTIVE, and the product page includes Linux support and VPIF-capable SoC details.
- ti.com
TI still listed TMS320DM6467 as ACTIVE, and its product page explicitly includes the Video Port Interface (VPIF).
codex reasoning notes (technical)
Real driver confirmed from source inspection (`vpif.c`, `vpif_capture.c`, `vpif_display.c`) and Kconfig via shell `sed`. Upstream attention came from local shell `git log`; git.kernel.org commit URLs are canonical-recall URLs built from the observed hashes. A local `git log --grep` found no actual vpif deprecation/removal series, only remove-callback API churn, so there is no clear removal push. Product availability came from `web.search_query` on ti.com: OMAP-L138 and DM6467 were still ACTIVE, but both are old DaVinci-era embedded/video SoCs, so current deployments are likely niche legacy/industrial rather than broad new designs. No natural replacement driver exists because VPIF is a SoC-specific capture/display block.