From: Philipp Zabel <p.zabel@pengutronix.de>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: imx-drm: vblank wait timed out
Date: Wed, 05 Apr 2017 12:05:57 +0200 [thread overview]
Message-ID: <1491386757.2381.62.camel@pengutronix.de> (raw)
In-Reply-To: <CAH9NwWc8fdP9ikyuK_1O8zdpaQ5L6C-D8x7q1pe7bMZjD52vUw@mail.gmail.com>
On Tue, 2017-04-04 at 14:50 +0200, Christian Gmeiner wrote:
[...]
> > Is this on a non-plus i.MX6? Maybe are missing the LDB DI clock glitch
> > fixes (commits 5d283b083800, 03d576f202e8, and f13abeff2cde)?
>
> Yes it is a non-plus i.MX6D and all those three patches are included in
> 4.9.20 (which I am using right now), But maybe my dts is not that good as I
> used it for a longer time without any changes to it. It is really time to get
> those upstream.
Which device tree is this? Can I see it?
> At the moment I have this artifact in it:
>
> &clks {
> assigned-clocks = <&clks IMX6QDL_CLK_LDB_DI0_SEL>,
> <&clks IMX6QDL_CLK_LDB_DI1_SEL>;
> assigned-clock-parents = <&clks IMX6QDL_CLK_PLL5_VIDEO_DIV>,
> <&clks IMX6QDL_CLK_PLL5_VIDEO_DIV>;
> };
>
> I am not to 100% sure if PLL5 is what I want - need.
I'd use PLL5 for LVDS only if there is no other clock that can provide
the required rate, or if thee is no other display. Is LVDS the only user
of PLL5 or does this maybe conflict with HDMI?
regards
Philipp
next prev parent reply other threads:[~2017-04-05 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 10:44 Christian Gmeiner
2017-03-31 12:57 ` Philipp Zabel
2017-04-03 15:16 ` Christian Gmeiner
2017-04-04 8:14 ` Philipp Zabel
2017-04-04 12:50 ` Christian Gmeiner
2017-04-05 10:05 ` Philipp Zabel [this message]
2017-04-05 16:07 ` Christian Gmeiner
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=1491386757.2381.62.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®