Hey Fabio,

On 4/10/19 2:00 PM, Fabio Estevam wrote:
> On Wed, Apr 10, 2019 at 8:55 AM Fabio Estevam <festevam@gmail.com> wrote:
> 
>> Please check if this patch fixes the problem on your case:
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20190410&id=728e096dd70889c2e80dd4153feee91afb1daf72
> 
> Also, just confirmed that this commit reached 5.1-rc3.
> 
> Robert, please run 5.1-rc3 (or rc4) and let us know if you still see
> the problem.

That does seem to work, but I'm seeing another crash.
So I can't 100% confirm it.

[    2.019601] imx-drm display-subsystem: bound disp0 (ops imx_pd_ops)
[    2.027062] dwhdmi-imx 120000.hdmi: Detected HDMI TX controller v1.30a with 
HDCP (DWC HDMI 3D TX PHY)
[    2.041765] imx-drm display-subsystem: bound 120000.hdmi (ops dw_hdmi_imx_ops)
[    2.049608] [drm] forcing LVDS-1 connector off
[    2.054482] imx-drm display-subsystem: bound ldb (ops imx_ldb_ops)
[    2.064153] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on 
minor 1

^^ Looks good to me.
However, the kernel crashes right after this, let me attach the full bootlog below.

Just to be clear, this is when using:
Kernel version: v5.1-rc4
Commit: 15ade5d2e7775667cf191cf2f94327a4889f8b9d
Devboard: Nitrogen6-Max
SOC: i.MX6QP