Hi,

On Thu, Sep 11, 2025 at 08:34:48PM +0300, Marius Vlad wrote:
> > > diff --git a/drivers/gpu/drm/msm/dsi/dsi_manager.c 
> > > b/drivers/gpu/drm/msm/dsi/dsi_manager.c
> > > index ca400924d4ee..4b87f4f78d38 100644
> > > --- a/drivers/gpu/drm/msm/dsi/dsi_manager.c
> > > +++ b/drivers/gpu/drm/msm/dsi/dsi_manager.c
> > > @@ -479,7 +479,7 @@ int msm_dsi_manager_connector_init(struct msm_dsi 
> > > *msm_dsi,
> > >   if (ret)
> > >           return ret;
> > >  
> > > - connector = drm_bridge_connector_init(dev, encoder);
> > > + connector = drm_bridge_connector_init(dev, encoder, 
> > > BIT(HDMI_COLORSPACE_RGB));
> > 
> > And this totally depends on the bridge chain. If we have a DSI-to-HDMI
> > bridge somewhere in the middle, we are able to output YUV data to the
> > HDMI connector.
> That's actually the usecase for this patch: to allow passing other color
> formats, but this patch is a transitory patch to further expose the fact
> drm_bridge_connector_init was embedding BIT(HDMI_COLORSPACE_RGB) for the
> format. See rockchip implementation for this bit, the last patch in this
> series.

I think Dmitry's point is that it needs to be integrated with the
atomic_get_input_bus_fmt / atomic_get_output_bus_fmt, because not only
we need to make sure the monitor supports it, and the userspace demands
it, we also need to make sure every bridge in the chain (and possibly
the encoder) can implement it.

Maxime

Attachment: signature.asc
Description: PGP signature

Reply via email to