Re: [PATCH v2 3/3] media: ipu-bridge: Add OmniVision OV32C4

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

Hi Robert,

Thanks for the update.

On Fri, Aug 28, 2026 at 03:21:04PM +0200, Robert Bozik wrote:
> Add the sensor configuration for the OV32C4, matching the _HID the
> sensor enumerates with. Without this entry the bridge does not build a
> software node graph for the sensor, so its driver defers probing on the
> missing fwnode endpoint forever and the camera never binds.
> 
> Assisted-by: Claude:claude-opus-5 sparse
> Assisted-by: Claude:claude-fable-5 sparse
> Signed-off-by: Robert Bozik <robertbozik@gmail.com>
> ---
> Changes in v2:
> - Signed-off-by placed last in the trailer block (Krzysztof Kozlowski).
> - No other changes.
> 
>  drivers/media/pci/intel/ipu-bridge.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
> index 1bb3a3e98..7d3c7e09f 100644
> --- a/drivers/media/pci/intel/ipu-bridge.c
> +++ b/drivers/media/pci/intel/ipu-bridge.c
> @@ -93,6 +93,16 @@ static const struct ipu_sensor_config ipu_supported_sensors[] = {
>  	IPU_SENSOR_CONFIG("OVTIDB10", 1, 560000000),
>  	/* Omnivision OV2680 */
>  	IPU_SENSOR_CONFIG("OVTI2680", 1, 331200000),
> +	/*
> +	 * OmniVision OV32C4.
> +	 *
> +	 * 400 MHz link frequency, i.e. 800 Mbps per lane. There is no public
> +	 * datasheet; the value comes from the vendor Windows driver, which
> +	 * carries it as MipiBps, and it is confirmed on hardware: the IPU7
> +	 * D-PHY locks and the sensor streams 3264x1840 at a measured
> +	 * 30.00 fps, matching pixel_rate / (ppl * vts) exactly.

This bit could go to the driver but the IPU bridge isn't the right place to
document this.

> +	 */
> +	IPU_SENSOR_CONFIG("OVTI32C4", 1, 400000000),
>  	/* Omnivision OV5675 */
>  	IPU_SENSOR_CONFIG("OVTI5675", 1, 450000000),
>  	/* Omnivision OV8856 */

-- 
Regards,

Sakari Ailus