Camera Sensor Drivers Compliance
summary
V4L2 has a compliance tool but it misses functional expectations, so libcamera becomes the common consumer and adds concrete fixes: libcamera helpers translate generic analog-gain and exposure values into sensor register values, exposure is normalized to lines, and blanking/exposure ordering is codified. Practical testing shows surprising gaps — only six drivers advertise the control flag that signals buffer layout changes — and device-tree rotation blobs often embed flips. The helper work unifies many drivers but gaps remain and expanded compliance tests are needed.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:34Camera sensor drivers compliance
- 6:12Exposure/gain handling
- 9:58Vertical and horizontal flips
- 12:22Camera sensor rotation
- 17:06Selection targets: analog crop
- 19:15Blankings controls
related talks
33mBring Your Camera into 2018: Forward Porting Image Sensor Drivers
30mComplex Cameras on Linux
46mWhy Embedded Cameras are Difficult, and How to Make Them Easy
42mCameras in Embedded Systems: Device Tree and ACPI View
39mCameras, Devicetree and ACPI: A Device Driver Perspective
48mGiving Linux a Camera Stack: libcamera's 3 Years Journey and Exciting Future
45mV4L2 & CEC Status Report
46mV4L2 Video Decoder/Encoder Development Journey
