From: Philipp Zabel <p.zabel@pengutronix.de>
To: Stanislav Meduna <stano@meduna.org>
Cc: linux-kernel@vger.kernel.org, Dennis Gilmore <dennis@ausil.us>
Subject: Re: Problem with gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading
Date: Thu, 23 Jun 2016 10:12:39 +0200 [thread overview]
Message-ID: <1466669559.2278.4.camel@pengutronix.de> (raw)
In-Reply-To: <164dd12f-cce7-911d-abaa-bf5daab40e6f@meduna.org>
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
prev parent reply other threads:[~2016-06-23 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 17:43 Stanislav Meduna
2016-06-23 8:12 ` Philipp Zabel [this message]
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=1466669559.2278.4.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dennis@ausil.us \
--cc=linux-kernel@vger.kernel.org \
--cc=stano@meduna.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®