On Tue, 24 Dec 2024 20:22:40 +0200, Cristian Ciocaltea wrote:
> Bridges with DRM_BRIDGE_OP_HDMI set in drm_bridge->ops are expected to
> rely on drm_bridge->supported_formats to advertise the supported
> colorspaces, including HDMI_COLORSPACE_YUV420.
>
> However, when drm_bridge_connector gets ini
On Tue, Jan 07, 2025 at 01:36:59PM +0200, Dmitry Baryshkov wrote:
> On Mon, Jan 06, 2025 at 02:55:52PM +, Maxime Ripard wrote:
> > On Tue, 24 Dec 2024 20:22:40 +0200, Cristian Ciocaltea wrote:
> > > Bridges with DRM_BRIDGE_OP_HDMI set in drm_bridge->ops are expected to
> > > rely on drm_bridge-
On Mon, Jan 06, 2025 at 02:55:52PM +, Maxime Ripard wrote:
> On Tue, 24 Dec 2024 20:22:40 +0200, Cristian Ciocaltea wrote:
> > Bridges with DRM_BRIDGE_OP_HDMI set in drm_bridge->ops are expected to
> > rely on drm_bridge->supported_formats to advertise the supported
> > colorspaces, including H
On Tue, 24 Dec 2024 20:22:40 +0200, Cristian Ciocaltea wrote:
> Bridges with DRM_BRIDGE_OP_HDMI set in drm_bridge->ops are expected to
> rely on drm_bridge->supported_formats to advertise the supported
> colorspaces, including HDMI_COLORSPACE_YUV420.
>
> However, when drm_bridge_connector gets ini
Bridges with DRM_BRIDGE_OP_HDMI set in drm_bridge->ops are expected to
rely on drm_bridge->supported_formats to advertise the supported
colorspaces, including HDMI_COLORSPACE_YUV420.
However, when drm_bridge_connector gets initialised, only
drm_bridge->ycbcr_420_allowed is considered in the proces
