From: Philipp Zabel <p.zabel@pengutronix.de>
To: devel@driverdev.osuosl.org, Russell King <rmk+kernel@arm.linux.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, Philipp Zabel <p.zabel@pengutronix.de>
Subject: [PATCH 0/7] Reorder i.MX IPU display enable/disable sequence
Date: Mon, 14 Apr 2014 17:21:28 +0200 [thread overview]
Message-ID: <1397488895-17930-1-git-send-email-p.zabel@pengutronix.de> (raw)
Repeatedly enabling and disabling the display currently can lead to a state
in which the IPU doesn't produce a valid signal anymore because we disable
IPU submodules before they can finish their interaction.
This series reorders the enable/disable sequence so that we first wait for the
DC/DP to finish processing the current frame, then stop the DI and IDMAC, and
only then disable clocks to the submodules. Also from now on we disable the DC
when it is not in use.
regards
Philipp
Philipp Zabel (7):
imx-drm: ipu-common: add ipu_map_irq to request non-IDMAC interrupts
imx-drm: ipu-common: Add helpers to check for a busy IDMAC channel and
to busywait for an interrupt
imx-drm: ipu-dmfc: Wait for FIFOs to run empty before disabling
imx-drm: ipu-dc: Wait for DC_FC_1 / DP_SF_END interrupt
imx-drm: ipu-dp: Split disabling the DP foreground channel from
disabling the DP module
imx-drm: imx-dp: When disabling the DP foreground channel, wait until
the DP background channel is finished before disabling the IDMAC
channel
imx-drm: ipuv3-crtc: Change display enable/disable order
drivers/staging/imx-drm/ipu-v3/imx-ipu-v3.h | 3 ++
drivers/staging/imx-drm/ipu-v3/ipu-common.c | 41 ++++++++++++++---
drivers/staging/imx-drm/ipu-v3/ipu-dc.c | 71 ++++++++++++++++++++---------
drivers/staging/imx-drm/ipu-v3/ipu-dmfc.c | 25 +++++++++-
drivers/staging/imx-drm/ipu-v3/ipu-dp.c | 71 +++++++++++++++++++----------
drivers/staging/imx-drm/ipu-v3/ipu-prv.h | 3 ++
drivers/staging/imx-drm/ipuv3-crtc.c | 10 ++--
drivers/staging/imx-drm/ipuv3-plane.c | 4 ++
8 files changed, 173 insertions(+), 55 deletions(-)
--
1.9.1
next reply other threads:[~2014-04-14 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 15:21 Philipp Zabel [this message]
2014-04-14 15:21 ` [PATCH 1/7] imx-drm: ipu-common: add ipu_map_irq to request non-IDMAC interrupts Philipp Zabel
2014-04-14 15:21 ` [PATCH 2/7] imx-drm: ipu-common: Add helpers to check for a busy IDMAC channel and to busywait for an interrupt Philipp Zabel
2014-04-14 15:21 ` [PATCH 3/7] imx-drm: ipu-dmfc: Wait for FIFOs to run empty before disabling Philipp Zabel
2014-04-14 15:21 ` [PATCH 4/7] imx-drm: ipu-dc: Wait for DC_FC_1 / DP_SF_END interrupt Philipp Zabel
2014-04-14 21:45 ` Russell King - ARM Linux
2014-04-14 15:21 ` [PATCH 5/7] imx-drm: ipu-dp: Split disabling the DP foreground channel from disabling the DP module Philipp Zabel
2014-04-14 15:21 ` [PATCH 6/7] imx-drm: imx-dp: When disabling the DP foreground channel, wait until the DP background channel is finished before disabling the IDMAC channel Philipp Zabel
2014-04-14 15:21 ` [PATCH 7/7] imx-drm: ipuv3-crtc: Change display enable/disable order Philipp Zabel
2014-04-14 19:57 ` [PATCH 0/7] Reorder i.MX IPU display enable/disable sequence Russell King - ARM Linux
2014-04-14 21:31 ` Russell King - ARM Linux
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=1397488895-17930-1-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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®