From: Philipp Zabel <p.zabel@pengutronix.de>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: kernel@pengutronix.de, dri-devel@lists.freedesktop.org
Subject: [GIT PULL] drm/imx: pending update handling, plane zpos property
Date: Wed, 13 Feb 2019 17:06:38 +0100 [thread overview]
Message-ID: <1550073998.3937.4.camel@pengutronix.de> (raw)
Hi Dave, Daniel,
please consider merging these imx-drm updates for v5.1.
The branch sits on top of yesterday's drm/imx fixes and adds support for
pending update handling, plane zpos property, builds under COMPILE_TEST
on all platforms.
regards
Philipp
The following changes since commit eb0200a4357da100064971689d3a0e9e3cf57f33:
gpu: ipu-v3: pre: don't trigger update if buffer address doesn't change (2019-01-23 11:56:44 +0100)
are available in the Git repository at:
git://git.pengutronix.de/pza/linux tags/imx-drm-next-2019-02-13
for you to fetch changes up to e4a2457f459bba3509bc8d9dd4b62f94a35f0fb7:
drm/imx: only send commit done event when all state has been applied (2019-01-30 11:01:13 +0100)
----------------------------------------------------------------
drm/imx: handle pending updates better, add plane zpos property support
- Add a mechanism to only send commit done events once all pending
updates have been applied. This closes a small race window where
already armed events could fire even though the double buffered
hardware update just missed the update window.
- Add plane zpos property support to allow placing the overlay plane
behind the primary plane.
- Allow building imx-drm on all platforms under COMPILE_TEST.
----------------------------------------------------------------
Lucas Stach (4):
gpu: ipu-v3: pre: add double buffer status readback
gpu: ipu-v3: prg: add function to get channel configure status
drm/imx: ipuv3-plane: add function to query atomic update status
drm/imx: only send commit done event when all state has been applied
Philipp Zabel (3):
drm/imx: ipuv3-plane: add zpos property
drm/imx: imx-tve: depend on COMMON_CLK
drm/imx: allow building under COMPILE_TEST
drivers/gpu/drm/imx/Kconfig | 3 +-
drivers/gpu/drm/imx/imx-drm-core.c | 7 +---
drivers/gpu/drm/imx/ipuv3-crtc.c | 30 ++++++++++++++-
drivers/gpu/drm/imx/ipuv3-plane.c | 76 +++++++++++++++++++++++++-------------
drivers/gpu/drm/imx/ipuv3-plane.h | 2 +
drivers/gpu/ipu-v3/ipu-pre.c | 6 +++
drivers/gpu/ipu-v3/ipu-prg.c | 16 ++++++++
drivers/gpu/ipu-v3/ipu-prv.h | 1 +
include/video/imx-ipu-v3.h | 1 +
9 files changed, 109 insertions(+), 33 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-02-13 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 16:06 Philipp Zabel [this message]
2019-02-14 13:06 ` [GIT PULL] drm/imx: pending update handling, plane zpos property Daniel Vetter
2019-02-14 14:19 ` Philipp Zabel
2019-02-14 14:50 ` Daniel Vetter
2019-02-14 20:20 ` Daniel Vetter
2019-02-15 10:17 ` Philipp Zabel
2019-02-15 16:41 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2019-02-22 11:23 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=1550073998.3937.4.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--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