Repository navigation
drivers/video: Add the ST VL53L5CX multizone ToF driver - #22026
Open
raiden00pl wants to merge 4 commits into
Open
raiden00pl wants to merge 4 commits into
raiden00pl wants to merge 4 commits into
Conversation
V4L2_PIX_FMT_Z16 carries a 16-bit little endian distance per pixel, as used by time-of-flight depth sensors. Add the imgdata and imgsensor values and pass it through the V4L2 capture format handling. Assisted-by: Claude:claude-fable-5-1 Signed-off-by: raiden00pl <raiden00@railab.me>
VIDIOC_ENUM_FRAMEINTERVALS returned every sensor entry whatever the requested size and format. Entries that set a width, height or pixel format now only match a request for it. This also filters the per-size entries of the UVC host driver; tables without them work as before. Assisted-by: Claude:claude-fable-5-1 Signed-off-by: raiden00pl <raiden00@railab.me>
The VL53L5CX is a V4L2 depth capture device with its own image sensor and image data interfaces: V4L2_PIX_FMT_Z16 in millimetres, 8x8 at 1-15 Hz or 4x4 at 1-60 Hz. The sensor INT output starts each frame read on the low priority work queue. The sensor keeps its firmware in RAM: the build downloads it from ST's VL53L5CX ULD (X-CUBE-TOF1), which is under the BSD-3-Clause license, so the driver depends on ALLOW_BSD_COMPONENTS. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: raiden00pl <raiden00@railab.me>
The camera module carries a VL53L5CX on I2C1, with INT on PQ0 and LPn on PQ5. The board powers the module with the IMX335 held in reset and registers the sensor as /dev/video1. INT takes EXTI0, so the TAMP button has no interrupt when the sensor is enabled. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: raiden00pl <raiden00@railab.me>
raiden00pl
requested review from
Ouss4,
jerpelea,
pkarashchenko and
xiaoxiang781216
as code owners
November 18, 2026 18:55
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Entries that set a size or format now only match a request for it
(this also filters the UVC host driver's per-size entries).
V4L2 depth capture device (V4L2_PIX_FMT_Z16, mm): 8x8 at 1-15 Hz or
4x4 at 1-60 Hz. The sensor INT output starts each frame read on the LP
work queue. The sensor keeps its firmware in RAM; the build downloads
it from ST's VL53L5CX ULD (X-CUBE-TOF1 v3.4.3, BSD-3-Clause), so the
driver depends on ALLOW_BSD_COMPONENTS.
INT on PQ0, LPn on PQ5, /dev/video1. INT takes EXTI0, so the TAMP
button has no interrupt when the sensor is enabled.
Impact
New driver, a new pixel format (Z16) and a fix in frame interval
enumeration. No change for existing boards.
Testing
STM32N6570-DK, nsh + VIDEO_VL53L5CX (10 ms tick), V4L2 capture of
/dev/video1: