linux-kernel - Re: Problem with gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 23 Jun 2016 10:12:39 +0200
From:	Philipp Zabel <p.zabel@...gutronix.de>
To:	Stanislav Meduna <stano@...una.org>
Cc:	linux-kernel@...r.kernel.org, Dennis Gilmore <dennis@...il.us>
Subject: Re: Problem with gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading

Hi Stanislav,

Am Mittwoch, den 22.06.2016, 19:43 +0200 schrieb Stanislav Meduna:
> Hi,
> 
> the c04e6e9 patch
> 
> gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading
> 
> broke display connected to a TQMa53 i.MX53 board. The lines
> 
> imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops ipu_crtc_ops)
> imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops ipu_crtc_ops)
> 
> are not present anymore and the display shows random lines.
> 
> I am using the 4.4.12-rt19+ kernel with some local changes, but
>
> the area of this patch is not touched by either.
> 
> I am not sure whether my device tree is at fault (I am not
> an expert here nor did I created the file from scratch) or the patch
> does not take some special case into account. In any case
> reverting the patch solves the problem for me.

It's not your fault. Please update to 4.4.13 or apply commit
310944d148e3 ("drm/imx: Match imx-ipuv3-crtc components using device
node in platform data"). That should fix this issue. See the patch
description for more details.

regards
Philipp