From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Nick Bowler <nbowler@draconx.ca>
Cc: Archit Taneja <architt@codeaurora.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Airlie <airlied@redhat.com>,
Andrzej Hajda <a.hajda@samsung.com>
Subject: Re: PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)
Date: Mon, 04 Dec 2017 21:34:36 +0200 [thread overview]
Message-ID: <2033574.q3E8txTlp8@avalon> (raw)
In-Reply-To: <20171204193001.dduxkafufgpeexk2@aura.draconx.ca>
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
next prev parent reply other threads:[~2017-12-04 19:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 5:16 PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression) Nick Bowler
2017-11-05 16:41 ` Nick Bowler
2017-11-16 6:28 ` Nick Bowler
2017-11-27 4:05 ` Archit Taneja
2017-11-27 9:00 ` Laurent Pinchart
2017-11-27 16:34 ` Nick Bowler
2017-11-28 3:30 ` Nick Bowler
2017-12-01 0:11 ` Nick Bowler
2017-12-02 17:11 ` Jose Abreu
2017-12-03 5:20 ` Nick Bowler
2017-12-04 10:04 ` Jose Abreu
2017-12-04 18:33 ` Nick Bowler
2017-12-05 6:18 ` Nick Bowler
2017-12-04 19:06 ` Laurent Pinchart
2017-12-04 19:30 ` Nick Bowler
2017-12-04 19:34 ` Laurent Pinchart [this message]
2017-12-05 3:22 ` Nick Bowler
2017-12-05 9:41 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2033574.q3E8txTlp8@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@redhat.com \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).