Re: [RFC PATCH 6/8] media: i2c: ov2312: add Omnivison OV2312 driver

[Sakari Ailus <sakari.ailus@linux.intel.com>]

Hi Mirela,

On Fri, Oct 02, 2026 at 07:16:11PM +0300, Mirela Rabulea wrote:
> Laurent, Hans, Sakari,
> 
> did you encounter similar situations? Any comments or proposals? The concern
> here, to summarize, is: v4l2 control cannot be committed to sensor registers
> right away (even when streaming) and we are also unsure when the right
> moment to perform the register access may come.

In practice there's little the kernel overall can do about this: the timing
of everything is handled by the userspace. Drivers that aren't directly in
control of the data path don't even have frame timing information and even
if we did pass that to drivers, I²C writes always have some uncertainty
(system scheduling, I²C access failures etc.), so one needs to be prepared
to failing to do the writes in time, which would further complicate the
UAPI.

Do you have libcamera in userspace or something else?

-- 
Kind regards,

Sakari Ailus