From: CK Hu <ck.hu@mediatek.com>
To: Dave Airlie <airlied@gmail.com>,
Daniel Vetter <daniel.vetter@intel.com>,
<dri-devel@lists.freedesktop.org>,
<linux-mediatek@lists.infradead.org>
Cc: Phong LE <ple@baylibre.com>, Sean Paul <seanpaul@chromium.org>,
Evan Benn <evanbenn@chromium.org>,
Bibby Hsieh <bibby.hsieh@mediatek.com>
Subject: [GIT PULL] mediatek drm fixes for 5.6
Date: Thu, 5 Mar 2020 09:51:09 +0800 [thread overview]
Message-ID: <1583373069.364.4.camel@mtksdaap41> (raw)
Hi, Dave & Daniel:
This include OVL, cursor, and gce fixup.
Regards,
CK
The following changes since commit
bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
are available in the Git repository at:
https://github.com/ckhu-mediatek/linux.git-tags.git
tags/mediatek-drm-fixes-5.6
for you to fetch changes up to 3d2ed431b8f39483477bc3c3a2aefbc9778ffe12:
drm/mediatek: Handle component type MTK_DISP_OVL_2L correctly
(2020-02-25 13:02:22 +0800)
----------------------------------------------------------------
Mediatek DRM Fixes for Linux 5.6
----------------------------------------------------------------
Bibby Hsieh (4):
drm/mediatek: Add plane check in async_check function
drm/mediatek: Add fb swap in async_update
drm/mediatek: Move gce event property to mutex device node
drm/mediatek: Make sure previous message done or be aborted before
send
Evan Benn (1):
drm/mediatek: Find the cursor plane instead of hard coding it
Phong LE (1):
drm/mediatek: Handle component type MTK_DISP_OVL_2L correctly
Sean Paul (1):
drm/mediatek: Ensure the cursor plane is on top of other overlays
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 30
+++++++++++++++++++----------
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 1 +
drivers/gpu/drm/mediatek/mtk_drm_plane.c | 7 +++++++
3 files changed, 28 insertions(+), 10 deletions(-)
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
reply other threads:[~2020-03-05 1:51 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=1583373069.364.4.camel@mtksdaap41 \
--to=ck.hu@mediatek.com \
--cc=airlied@gmail.com \
--cc=bibby.hsieh@mediatek.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=evanbenn@chromium.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=ple@baylibre.com \
--cc=seanpaul@chromium.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;
as well as URLs for NNTP newsgroup(s).