Hi Nick, On Monday, 4 December 2017 21:30:01 EET Nick Bowler wrote: > On 2017-12-04 21:06 +0200, Laurent Pinchart wrote: > > As you reported that the PLL lock failure message is not printed, the > > failure can only come from either the extra delay introduced by the > > above loop, or from reading the HDMI_PHY_STAT0 register. > > > > How many iterations of the for loop execute before the condition > > becomes true? > > Judging from the log posted elsethread (where I added extra printouts), > it seems to consistently become true on the second iteration. > > I will try to rule out read side effects by replacing the polling loop > with an unconditional delay. You're reading my mind :-) -- Regards, Laurent Pinchart _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
