Re: [PATCH 0/4] media: Add the ST VD55G0 global shutter sensor

[Sergey Lebedev <lsa.uz@pm.me>]

Hi Fernando,

Thank you for the run, and for the detail.

On 25/10/2026 15:51, Fernando Rimoli wrote:
>  - renamed "dovdd" to "dvdd" in the ACPI supply names, because the
>    6.19-based int3472 here registers this sensor's two GPIO supplies as
>    avdd and dvdd, so dovdd got the dummy regulator.

The Surface Pro 9's ICL2 has the same two power GPIOs as the Surface
Pro 11, types 0x0b and 0x10. Mainline v6.19 has no name for 0x10, so
the dvdd comes from your tree; media next calls it dovdd, and the
driver as posted should find it there. If the int3472 names change, the
driver's ACPI names follow whatever lands.

> Since the driver needs a multiple of the clock it believes it has, a
> separate entry for this IPU (8086:465d) through the per-IPU match in
> ipu-bridge would let it run in specification without changing yours.

I would rather fix the clock. With 19.2 MHz reported as 24, the sensor
runs at four fifths of every rate the driver computes, so an
in-specification link frequency would still leave the controls off by
four fifths, as your 57.20 against 71.49 at 600 MHz shows. On Hao's
thread I have pointed at the Surface Pro 9's _DSM, which looks like it
takes 0 for 24 MHz. If it does, 396 MHz is in specification there too.

> 2. Nothing bounds the exposure while the strobe is on, and the
> illuminator has an overcurrent limit that a long exposure trips.

The same here: on the Surface Pro 11 the illuminator holds up to 68% of
an 1860-line frame, fades at 70-72% and goes out at 72-75%. It fades
rather than cutting off, which points at the board's LED driver rather
than the sensor, so the fraction belongs to the board, like st,leds. The
sensor has the means: MAX_EXPOSURE_LINES (UM2829, 13.8.1) bounds its own
auto exposure as well as manual exposure. I would do that as a
follow-up, with the bound supplied from the same place as st,leds,
rather than grow this series. Benjamin, say if you would rather have it
in the driver now.

> 3. On IPU6 the stream needs a CPU latency bound, or frames come out
> corrupted.

Thank you. I will mention it in the v2 cover letter, so that IPU6
testers do not take it for the sensor.

> I will add a Tested-by for the Surface Pro 9 on v2, if it has an entry
> for it.

It will; see my answer on 4/4.

Sergey