On 7/8/26 9:46 AM, Maxime Ripard wrote: > On Fri, Jul 03, 2026 at 10:55:09PM +0300, Cristian Ciocaltea wrote: >> On 7/3/26 5:19 PM, Dmitry Baryshkov wrote: >>> On Thu, Jul 02, 2026 at 05:46:16PM +0300, Cristian Ciocaltea wrote: >>>> Switch drm_bridge_connector_init() to >>>> drmm_connector_hdmi_init_with_caps(), collecting the bridge's HDMI >>>> properties into a stack drm_connector_hdmi_caps so future HDMI 2.x >>>> capabilities can be plumbed without growing the argument list. >>>> >>>> Introduce struct drm_bridge::supported_hdmi_ver to let bridges declare >>>> the HDMI specification version they are conformant with, and forward it >>>> to the connector layer through the new caps struct so HDMI 2.x features >>>> can be gated on real source capability rather than guesswork. >>> >>> And it's left uninitialized by the bridges, which doesn't mean anything. >>> If you don't want to touch all bridge drivers in one commit, please >>> provide some migration path and hopefully get rid of it by the end of >>> the series. >> >> Sure, one question though: at the end of the migration, would it be fine to >> stick with drmm_connector_hdmi_init_with_caps() and just drop >> drmm_connector_hdmi_init()? Otherwise I'll rename it back. > > Absolutely, it doesn't make any sense to keep both variants.
I was referring to whether option 3 might be the preferred choice in the context of the earlier patch discussion. Cristian
