Mods: This really should be a continuation of my previous topic on this.
The new OV9282 driver can (in theory) be configured to use continuous or non-continuous MIPI clocks, and defaults to non-continuous.
The old OV9281 driver always used continuous clocks.
Non-continuous clocks restrict the framerate/exposure time (minimum HTS is higher), so there is benefits to running the MIPI clocks continuously.
However, it seems the OV9282 driver cannot be properly configured to use continuous clocks as seems to be intended.
I know the goal is to configure V4L2 to unset the V4L2_MBUS_CSI2_NONCONTINUOUS_CLOCK flag. I have verified this by modifying the 6.12 OV9282 driver and forcing ov9282::noncontinuous_clock to false, ignoring that flag. That resulted in a working driver that allowed for lower a HTS.
But I struggle to find any documentation on how this is supposed to be configured.
There is a override named "clk-continuous", but specifying clk-continuous=1 results in a broken driver, the camera does not send any frames at all, even with the patched drivers that definitely configures the camera to use continuous clocks.
If I'm misinterpreting the device tree config, please tell me how to configure it. I can't find any documentation on how these overrides are supposed to work.
Thanks!
The new OV9282 driver can (in theory) be configured to use continuous or non-continuous MIPI clocks, and defaults to non-continuous.
The old OV9281 driver always used continuous clocks.
Non-continuous clocks restrict the framerate/exposure time (minimum HTS is higher), so there is benefits to running the MIPI clocks continuously.
However, it seems the OV9282 driver cannot be properly configured to use continuous clocks as seems to be intended.
I know the goal is to configure V4L2 to unset the V4L2_MBUS_CSI2_NONCONTINUOUS_CLOCK flag. I have verified this by modifying the 6.12 OV9282 driver and forcing ov9282::noncontinuous_clock to false, ignoring that flag. That resulted in a working driver that allowed for lower a HTS.
But I struggle to find any documentation on how this is supposed to be configured.
There is a override named "clk-continuous", but specifying clk-continuous=1 results in a broken driver, the camera does not send any frames at all, even with the patched drivers that definitely configures the camera to use continuous clocks.
If I'm misinterpreting the device tree config, please tell me how to configure it. I can't find any documentation on how these overrides are supposed to work.
Thanks!
Statistics: Posted by Seneral — Mon Dec 22, 2025 10:08 am — Replies 0 — Views 27