lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 05 Apr 2017 12:05:57 +0200
From:   Philipp Zabel <>
To:     Christian Gmeiner <>
Cc:     LKML <>,
        DRI mailing list <>
Subject: Re: imx-drm: vblank wait timed out

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?


Powered by blists - more mailing lists