Hi Laurent Thank you for your reply > > I noticed that ULCB+KF board on v5.15-rc1 doesn't probe HDMI. > > Is that the M3 or H3 ULCB ? I'm using H3 ULCB + Kingfihser > > commit d0f44e0dac29aca3f85d238dfbcd2e52450b38dc > > Author: Laurent Pinchart <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx> > > Date: Mon May 25 07:05:26 2020 +0300 > > > > drm: rcar-du: dw-hdmi: Set output port number > > > > Report the DT output port number in dw_hdmi_plat_data to connect to the > > next bridge in the dw-hdmi driver. > > > > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx> > > Tested-by: Kieran Bingham <kieran.bingham@xxxxxxxxxxxxxxxx> # On V3U > > Reviewed-by: Kieran Bingham <kieran.bingham+renesas@xxxxxxxxxxxxxxxx> > > I've tested v5.15-rc1 on a M3-N Salvator-XS, and can't reproduce the > issue. If your kernel log doesn't show anything useful, I'll test it on > my ULCB. I'm not sure what is related, but I noticed something. This is OK case. DRM failed ? rcar-dw-hdmi was probed ... [ 0.499485] gpio_rcar e6055800.gpio: driving 4 GPIOs [ 0.511240] SuperH (H)SCI(F) driver initialized [ 0.512316] e6e88000.serial: ttySC0 at MMIO 0xe6e88000 (irq = 123, base_baud = 0) is a scif [ 1.465894] printk: console [ttySC0] enabled => [ 1.476935] rcar-du feb00000.display: failed to initialize DRM/KMS (-6) => [ 1.485684] rcar-dw-hdmi fead0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (DWC HDMI 2.0 TX PHY) => [ 1.496248] rcar-dw-hdmi fead0000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.535173] loop: module loaded ... This is NG case. DAM failed. rcar-dw-hdmi is not probed. ... [ 0.490286] gpio_rcar e6055800.gpio: driving 4 GPIOs [ 0.501956] SuperH (H)SCI(F) driver initialized [ 0.503027] e6e88000.serial: ttySC0 at MMIO 0xe6e88000 (irq = 123, base_baud = 0) is a scif [ 1.432046] printk: console [ttySC0] enabled => [ 1.443177] rcar-du feb00000.display: failed to initialize DRM/KMS (-6) [ 1.481426] loop: module loaded ... Thank you for your help !! Best regards --- Kuninori Morimoto
