From: Sean Paul <sean@poorly.run>
To: dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org
Cc: dcastagna@chromium.org, matthias.bgg@gmail.com,
mcasas@chromium.org, Sean Paul <seanpaul@chromium.org>,
p.zabel@pengutronix.de, frkoenig@chromium.org,
ck.hu@mediatek.com, linux-arm-kernel@lists.infradead.org,
markyacoub@google.com
Subject: [PATCH v2 0/7] drm/mediatek: Refactor plane init/check and support rotation
Date: Tue, 5 Nov 2019 16:10:17 -0500 [thread overview]
Message-ID: <20191105211034.123937-1-sean@poorly.run> (raw)
From: Sean Paul <seanpaul@chromium.org>
Hello,
This is a follow-on to [1], which supports the original Y-flip. I've
added X-flip and 180 degree rotate. Additionally, the rotation property
is only exposed for ovl planes, not rdma planes since rdma doesn't
support it. In order to differentiate between the two types, I had to
do some plumbing in order to surface the supported rotations of a
component as well as allowing a component to implement plane checks.
I've tested this on a 4.19 kernel on mt8183. The set was then forward
ported to mainline and build tested. The forward port was relatively
collision free, but there were a few.
Sean
[1]- https://lists.freedesktop.org/archives/dri-devel/2019-November/242312.html
Sean Paul (7):
drm/mediatek: Refactor plane init
drm/mediatek: Add helper to get component for a plane
drm/mediatek: Add plumbing for layer_check hook
drm/mediatek: Plumb supported rotation values from components to plane
init
drm/mediatek: Support reflect-y plane rotation
drm/mediatek: Support reflect-x plane rotation
drm/mediatek: Support 180 degree rotation
drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 50 +++++++
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 145 ++++++++++++++------
drivers/gpu/drm/mediatek/mtk_drm_crtc.h | 2 +
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 22 +++
drivers/gpu/drm/mediatek/mtk_drm_plane.c | 18 ++-
drivers/gpu/drm/mediatek/mtk_drm_plane.h | 4 +-
6 files changed, 199 insertions(+), 42 deletions(-)
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next reply other threads:[~2019-11-05 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 21:10 Sean Paul [this message]
2019-11-05 21:10 ` [PATCH v2 1/7] drm/mediatek: Refactor plane init Sean Paul
2019-11-05 21:10 ` [PATCH v2 2/7] drm/mediatek: Add helper to get component for a plane Sean Paul
2019-11-05 21:10 ` [PATCH v2 3/7] drm/mediatek: Add plumbing for layer_check hook Sean Paul
2019-11-05 21:10 ` [PATCH v2 4/7] drm/mediatek: Plumb supported rotation values from components to plane init Sean Paul
2019-11-05 21:10 ` [PATCH v2 5/7] drm/mediatek: Support reflect-y plane rotation Sean Paul
2019-11-05 21:10 ` [PATCH v2 6/7] drm/mediatek: Support reflect-x " Sean Paul
2019-11-05 21:10 ` [PATCH v2 7/7] drm/mediatek: Support 180 degree rotation Sean Paul
2019-11-06 9:07 ` CK Hu
2019-11-06 14:42 ` Sean Paul
2019-11-07 1:38 ` CK Hu
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=20191105211034.123937-1-sean@poorly.run \
--to=sean@poorly.run \
--cc=ck.hu@mediatek.com \
--cc=dcastagna@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frkoenig@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=markyacoub@google.com \
--cc=matthias.bgg@gmail.com \
--cc=mcasas@chromium.org \
--cc=p.zabel@pengutronix.de \
--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