From: Philipp Zabel <p.zabel@pengutronix.de>
To: Martyn Welch <martyn.welch@collabora.co.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [CRTC:24] vblank wait timed out
Date: Fri, 24 Mar 2017 11:42:53 +0100 [thread overview]
Message-ID: <1490352173.3068.8.camel@pengutronix.de> (raw)
In-Reply-To: <20170324102428.GE25206@hermes.home>
On Fri, 2017-03-24 at 10:24 +0000, Martyn Welch wrote:
[...]
> > Could you move to v4.9 or v4.10 and check if the four patches in
> > https://git.pengutronix.de/cgit/pza/linux/tag/?id=v4.9-ipu-dp-plane-fix
> > or
> > https://git.pengutronix.de/cgit/pza/linux/tag/?id=v4.10-ipu-dp-plane-fix-2
> > help?
> >
>
> I've updated to v4.10, the patches from v4.10-ipu-dp-plane-fix-2 resolve
> the error, though we are unfortunately still experiencing the loss of
> output on LVDS display. Time to look elsewhere for the cause of that I
> guess. :-)
Is the LVDS serial clock derived from the video PLL on that board?
(What is the output of /sys/kernel/debug/clk/clk_summary?)
If you are driving high resolution displays from the same IPU, this
could also be a bandwidth issue. Maybe try severing the ipu1->hdmi and
ipu2->ldb links in the device tree as done in imx6q-utilite-pro.dts.
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-24 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:50 [CRTC:24] vblank wait timed out Martyn Welch
2017-03-21 17:18 ` Philipp Zabel
2017-03-24 10:24 ` Martyn Welch
2017-03-24 10:42 ` Philipp Zabel [this message]
2017-03-27 11:11 ` Martyn Welch
2017-03-28 10:49 ` Martyn Welch
2017-03-28 16:44 ` Philipp Zabel
2017-03-28 17:52 ` Martyn Welch
2017-03-29 8:07 ` Philipp Zabel
2017-03-29 8:21 ` Martyn Welch
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=1490352173.3068.8.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=martyn.welch@collabora.co.uk \
/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).