From: Philipp Zabel <p.zabel@pengutronix.de>
To: David Airlie <airlied@linux.ie>
Cc: kernel@pengutronix.de, dri-devel@lists.freedesktop.org
Subject: [GIT PULL] imx-drm fixes for i.MX5 regression and i.MX6QP PRE/PRG stability
Date: Thu, 12 Oct 2017 12:26:39 +0200 [thread overview]
Message-ID: <1507803999.5084.5.camel@pengutronix.de> (raw)
Hi Dave,
this tag contains a fix for a regression introduced in v4.14-rc1 with
commit 790cb4c7c954 ("drm/imx: lock scanout transfers for consecutive
bursts"), which breaks display output on i.MX53. Also there are two
patches to solve display output instability issues on i.MX6QP with the
prefetch/resolve feature.
regards
Philipp
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in the git repository at:
git://git.pengutronix.de/git/pza/linux.git tags/imx-drm-fixes-2017-10-12
for you to fetch changes up to 11aff4b4c7c4b7257660ef890920f2ac72911ed0:
gpu: ipu-v3: pre: implement workaround for ERR009624 (2017-10-11 12:04:24 +0200)
----------------------------------------------------------------
drm/imx: i.MX5 regression fix and i.MX6QP PRE/PRG stability fixes
- Disable channel burst locking on IPUv3EX (i.MX51) and IPUv3M (i.MX53).
This fixes a regression introduced by commit 790cb4c7c954 ("drm/imx: lock
scanout transfers for consecutive bursts").
- Give PRG a head start. Waiting for both double buffers to fill up before
enabling the IPU improves startup reliability.
- Avoid PRE control register updates during unsafe window, workaround for
ERR009624.
----------------------------------------------------------------
Lucas Stach (2):
gpu: ipu-v3: prg: wait for double buffers to be filled on channel startup
gpu: ipu-v3: pre: implement workaround for ERR009624
Philipp Zabel (1):
gpu: ipu-v3: Allow channel burst locking on i.MX6 only
drivers/gpu/ipu-v3/ipu-common.c | 8 ++++++++
drivers/gpu/ipu-v3/ipu-pre.c | 29 +++++++++++++++++++++++++++++
drivers/gpu/ipu-v3/ipu-prg.c | 7 +++++++
3 files changed, 44 insertions(+)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2017-10-12 10:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1507803999.5084.5.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@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).