Hi Piotr, 在 2025-03-05 21:56:12，"Piotr Oniszczuk" <piotr.oniszc...@gmail.com> 写道： > > >> Wiadomość napisana przez Andy Yan <andys...@163.com> w dniu 5 mar 2025, o >> godz. 03:30: >> >>> >> >> I only see the HDMI connector from your dri/state ; so it appears the DP >> driver hasn't been successfully >> initialized（I think kernel dmesg can tell that）. >> Have you enabled CONFIG_ROCKCHIP_DW_DP ? This is needed. >> > > >Andy, > >Do you mean CONFIG_ROCKCHIP_DW_DP or CONFIG_DRM_DW_DP ? > >If CONFIG_DRM_DW_DP - then yes - i have it: >https://github.com/warpme/minimyth2/blob/2e267842b1033bbc4c2c5d80c1756a142e347cc5/script/kernel/linux-6.14/files/linux-6.14-arm64-armv8.config#L5024 > >Kernel dmesg: https://termbin.com/uiup
Both of the two config options should be enabled. andy@Pro480:~/WorkSpace/linux-next$ rg DW_DP .config 4044:CONFIG_ROCKCHIP_DW_DP=y 4218:CONFIG_DRM_DW_DP=y And if dw dp driver boots success, you will see dmesg like bellow: [ 1.058634] arm-smmu-v3 fc900000.iommu: msi_domain absent - falling back to wired irqs [ 1.062458] rockchip-vop2 fdd90000.vop: Adding to iommu group 0 [ 1.067908] rockchip-drm display-subsystem: bound fdd90000.vop (ops vop2_component_ops) [ 1.068981] rockchip-drm display-subsystem: bound fde60000.dp (ops dw_dp_rockchip_component_ops) [ 1.070133] dwhdmiqp-rockchip fde80000.hdmi: registered DesignWare HDMI QP I2C bus driver [ 1.070859] rockchip-drm display-subsystem: bound fde80000.hdmi (ops dw_hdmi_qp_rockchip_ops) [ 1.072103] [drm] Initialized rockchip 1.0.0 for display-subsystem on minor 0 [ 1.080191] loop: module loaded But I just see hdmi driver boots from your dmesg. > > >
