From: Paolo Sabatino <paolo.sabatino@gmail.com>
To: "Alex Bee" <knaerzche@gmail.com>,
"Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/5] drm: rockchip: use overlay windows as such
Date: Sat, 25 Jul 2020 11:08:43 +0200 [thread overview]
Message-ID: <3a420557-8f49-02bf-e5d8-94c69534b2ca@gmail.com> (raw)
In-Reply-To: <20200718200323.3559-6-knaerzche@gmail.com>
On 18/07/20 22:03, Alex Bee wrote:
> static const int rk3188_vop_intrs[] = {
> @@ -980,7 +980,7 @@ static const struct vop_win_data rk3228_vop_win_data[] = {
> { .base = 0x00, .phy = &rk3288_win01_data,
> .type = DRM_PLANE_TYPE_PRIMARY },
> { .base = 0x40, .phy = &rk3288_win01_data,
> - .type = DRM_PLANE_TYPE_CURSOR },
> + .type = DRM_PLANE_TYPE_OVERLAY },
> };
>
> static const struct vop_data rk3228_vop = {
Tried on several rk322x boards, it worked fine.
Tested-by: Paolo Sabatino <paolo.sabatino@gmail.com>
prev parent reply other threads:[~2020-07-25 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 20:03 [PATCH 0/5] drm: rockchip: various ports for older VOPs Alex Bee
2020-07-18 20:03 ` [PATCH 1/5] drm: rockchip: add scaling for RK3036 win1 Alex Bee
2020-07-18 20:03 ` [PATCH 2/5] drm: rockchip: add missing registers for RK3188 Alex Bee
2020-07-20 8:22 ` [PATCH 2/5] drm: rockchip: add missing registers for RK3188【请注意，邮件由linux-rockchip-bounces+andy.yan=rock-chips.com@lists.infradead.org代发】 Andy Yan
2020-07-20 14:46 ` Alex Bee
2020-07-21 1:17 ` Andy Yan
2020-07-21 2:46 ` Alex Bee
2020-07-18 20:03 ` [PATCH 3/5] drm: rockchip: add alpha support for RK3036, RK3066, RK3126 and RK3188 Alex Bee
2020-07-18 20:03 ` [PATCH 4/5] drm: rockchip: set alpha_en to 0 if it is not used Alex Bee
2020-07-18 20:03 ` [PATCH 5/5] drm: rockchip: use overlay windows as such Alex Bee
2020-07-25 9:08 ` Paolo Sabatino [this message]
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=3a420557-8f49-02bf-e5d8-94c69534b2ca@gmail.com \
--to=paolo.sabatino@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).