On 11/30/24 1:13 AM, Cristian Ciocaltea wrote: > Bridges having the DRM_BRIDGE_OP_HDMI flag set in drm_bridge->ops are > supposed to rely on drm_bridge->supported_formats bitmask to advertise > the supported colorspaces, including HDMI_COLORSPACE_YUV420. Therefore, > the newly introduced drm_bridge->ycbcr_420_allowed flag becomes > redundant in this particular context. > > Moreover, when drm_bridge_connector gets initialised, only > drm_bridge->ycbcr_420_allowed is considered in the process of adjusting > the equivalent property of the base drm_connector, which effectively > discards the formats advertised by the HDMI bridge. > > Handle the inconsistency by ignoring ycbcr_420_allowed for HDMI bridges > and, instead, make use of the supported_formats bitmask when setting up > the bridge connector. > > Fixes: 3ced1c687512 ("drm/display: bridge_connector: handle ycbcr_420_allowed") Please ignore this and check v2 instead: https://lore.kernel.org/all/20241206-bridge-conn-fmt-prio-v2-1-85c817529b88@xxxxxxxxxxxxx/