Hello Morimoto-san, For some reason this mail hadn't made it to the list, nor to my inbox. On Thu, Nov 04, 2021 at 08:23:15AM +0900, Kuninori Morimoto wrote: > > Hi Kieran > > > > > => [ 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. > > > > Was something changed to make this happen between this and the above > > test? > > Only reverting the issue patch. > > > > Note that in both cases feb00000.display failed to probe first > > > Is this an fw_devlink issue, due to HDMI linking to DU in DT? > > > Does it work with fw_devlink=permissive of fw_devlink=off? > > > > The DT is all connected up with the ports as I would expect them on > > ulcb+kf, but I saw the unanswered question from Geert above. Could you > > check that please? > > In my understanding, Laurent answered it at private meeting. > He said it is not related, if my memory was correct. > > > Is there anything else specific to replicating this issue? Is it only on > > the ULCB+KF? Or does it occur on Salvator-XS too? (And does it need a > > specific kernel config to reproduce?) > > I could reproduce the same issue on Salvator-XS. > I attached my .config on this mail. [snip] > # CONFIG_DRM_DISPLAY_CONNECTOR is not set Enabling this option should help. -- Regards, Laurent Pinchart
