While testing the dw-dp v11 series I noticed that ROCKCHIP_DW_DP does not select DRM_BRIDGE_CONNECTOR although dw_dp-rockchip.c calls drm_bridge_connector_init(), and Sebastian suggested handling this independently of that series [1].
The ROCKCHIP_DW_DP gap was in fact found before: Marius Dinu posted the same one-liner in March [2] and dropped it when the failure stopped reproducing in his build. The failure is configuration-dependent - any other enabled option that selects DRM_BRIDGE_CONNECTOR masks it - so it can come and go with unrelated config changes. It still reproduces on current drm-misc-next. A sweep over drivers/gpu/drm/rockchip found eight callers of drm_bridge_connector_init(). Five options already select it, ROCKCHIP_INNO_HDMI gets it through its DRM_INNO_HDMI core option, and two are left with a latent link failure: ROCKCHIP_DW_DP and ROCKCHIP_RK3066_HDMI. The rk3066 case additionally needs DRM_DISPLAY_HELPER, whose module carries the bridge-connector code. Both failures were reproduced on drm-misc-next (d85a5e9dfb42) with an arm64 allnoconfig-based configuration enabling only DRM_ROCKCHIP plus the option in question; with the fixes applied both configurations link cleanly, and an arm64 defconfig re-run shows no new Kconfig warnings. Both issues are present in released kernels: the rk3066 one since v6.16, the dw_dp one since v6.18. [1] https://lore.kernel.org/r/aneNCDU12OzG99UX@venus [2] https://lore.kernel.org/r/[email protected] Igor Paunovic (2): drm/rockchip: dw_dp: Select DRM_BRIDGE_CONNECTOR drm/rockchip: rk3066_hdmi: Add missing Kconfig selects drivers/gpu/drm/rockchip/Kconfig | 3 +++ 1 file changed, 3 insertions(+) -- 2.43.0
