How V4L2 Transformed To Support Embedded Cameras
summary
V4L2 now exposes device topology with the media controller and implements subdev states (kernel helpers since ~v6.2) to store per-pad and per-stream formats, plus a routable routing table and stream IDs to model CSI‑2 virtual channels/data types; sensors use internal pads and frame descriptors; ISPs work inline or memory‑to‑memory, with examples on Renesas RZV2H and a Mali C‑55 ISP and Sony IMX500 (NPU output modeled as streams); multicontext and media jobs are emerging, V11 patch series and compliance tests are in flight.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 6:02V4L2 is only a webcam API?
- 11:22V4L2 handles complex hardware
- 13:30Media streams and routing tables
- 20:35CSI2 virtual channels handling
- 25:07Embedded data in CSI2 sensors
- 26:57Internal pads and configuration models
- 30:04HDR sensors and NPU integration
- 32:32V4L2 cannot handle ISPs?
- 36:02Multicontext support for ISPs
- 38:51Media jobs framework
- 40:13Future of V4L2
related talks
36mCamera/ISP Drivers Using V4L2 Media Controller Framework- 36mCamera/ISP Drivers Using V4L2 Media Controller Framework
36mV4L2 Controls - From Perspective of Video Capture Devices
27mBoF: Cameras on Linux
25mLibcamera: Making Complex Cameras Easy
41mLearn How to Support Your SoC and ISP in Libcamera
46mV4L2 Video Decoder/Encoder Development Journey
42mV4L2: A Status Update