From: Stanislav Meduna <stano@meduna.org>
To: Philipp Zabel <p.zabel@pengutronix.de>,
linux-kernel@vger.kernel.org, Dennis Gilmore <dennis@ausil.us>
Subject: Problem with gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading
Date: Wed, 22 Jun 2016 19:43:38 +0200 [thread overview]
Message-ID: <164dd12f-cce7-911d-abaa-bf5daab40e6f@meduna.org> (raw)
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.
The DTS fragment is
disp1: display@disp1 {
compatible = "fsl,imx-parallel-display";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_disp1_1>;
interface-pix-fmt = "rgb24";
/*
* enable this to support parallel display or DVI
* disable LVDS bridge and TVE in this case
*/
status = "okay";
/*
* uncomment and adapt to your display to support parallel
* LCD display using video mode settings
*/
display-timings {
tx14d11vm1cpd {
clock-frequency = <5847953>;
hactive = <320>;
vactive = <240>;
hfront-porch = <30>;
hback-porch = <30>;
hsync-len = <5>;
vback-porch = <5>;
vfront-porch = <6>;
vsync-len = <2>;
pixelclk-active = <1>;
hsync-active = <0>;
vsync-active = <0>;
de-active = <1>;
};
};
port {
display1_in: endpoint {
remote-endpoint = <&ipu_di1_disp1>;
};
};
};
Thanks
--
Stano
next reply other threads:[~2016-06-22 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 17:43 Stanislav Meduna [this message]
2016-06-23 8:12 ` Problem with gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading Philipp Zabel
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=164dd12f-cce7-911d-abaa-bf5daab40e6f@meduna.org \
--to=stano@meduna.org \
--cc=dennis@ausil.us \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).