Camera/ISP Drivers Using V4L2 Media Controller Framework
summary
Explains how the media-controller layer augments V4L2 to model complex ISP pipelines as a graph of entities and pads, using media controller APIs to register entities, create links, and walk/start/stop pipelines; shows use of V4L2 async for dynamic subdevice binding and media-ctl for topology inspection; demonstrates building drivers that expose subdevices/video nodes (example: Rockchip ISP) and coordinating stream-on/stream-off sequencing so the pipeline brings up and tears down reliably.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:47Evolution of Cameras
- 2:16External ISP
- 3:31V4L2 Camera Stack
- 4:20V4L2 Internal ISP
- 4:50Evolution of V4L2
- 5:57Example ISP
- 10:11Media Controller
- 11:29Media Device Model
- 13:13Generic ISP
- 14:46Media Controller vs V4L2
- 16:17Media Controller API
- 16:32Media Device Register
- 17:57Media Entity Operations
- 20:36Other APIs
- 23:15Pipeline APIs
- 24:54V4L2 Async Framework
- 28:50MediaCTL Tool
- 31:28Media Request API
- 31:58References
related talks
36mCamera/ISP Drivers Using V4L2 Media Controller Framework
41mHow V4L2 Transformed To Support Embedded Cameras
27mBoF: Cameras on Linux
20mV4L2 Media Controller Request API
46mV4L2 Video Decoder/Encoder Development Journey
33mBring Your Camera into 2018: Forward Porting Image Sensor Drivers
55mTowards Mainline Video Capture and Camera Support for Recent Rockchip SoCs
42mCameras in Embedded Systems: Device Tree and ACPI View