Hi Chaoyi, On 9/10/26 10:16, Chaoyi Chen wrote: > Maybe we should consider adding a new "DRM_BRIDGE_OP_DP" :)
Works for me - it keeps the HDMI-only wording of max_bpc and makes the check explicit. So that Maxime and Cristian have something concrete to object to, this is all I would give the flag: - DRM_BRIDGE_OP_DP: the bridge drives a DisplayPort connector and fills in max_bpc. Nothing else is read from it for now. - drm_bridge_connector_init() treats it like DRM_BRIDGE_OP_HDMI: at most one such bridge in the chain (-EBUSY), max_bpc must be set (-EINVAL), and the connector gets "max bpc" with range 6..max_bpc. - dw-dp sets the flag and max_bpc = 10. The connector itself stays a plain drmm_connector_init() one - no DP counterpart of drmm_connector_hdmi_init() - so bridges without the flag see no change at all. > Perhaps @Cristian and @Maxime have better ideas? That is point 3, and I will wait for it before writing v3: whether the create-state block gets duplicated into the non-HDMI path or factored out of drmm_connector_hdmi_init(), and whether keeping the restore value in struct drm_bridge_connector is acceptable once 71/74 lands. Thanks, Igor
