From: Pekka Paalanen <ppaalanen@gmail.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Simon Ser <contact@emersion.fr>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, od@zcrc.me,
dri-devel@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm: DON'T require each CRTC to have a unique primary plane
Date: Mon, 29 Mar 2021 17:35:41 +0300 [thread overview]
Message-ID: <20210329173541.00b301ea@eldfell> (raw)
In-Reply-To: <C4BQQQ.FDNJ4NAK9OAD3@crapouillou.net>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
On Mon, 29 Mar 2021 12:41:00 +0100
Paul Cercueil <paul@crapouillou.net> wrote:
> Hi,
>
> Le lun. 29 mars 2021 à 11:15, Pekka Paalanen <ppaalanen@gmail.com> a
> écrit :
> > On Sat, 27 Mar 2021 11:26:26 +0000
> > Paul Cercueil <paul@crapouillou.net> wrote:
> >
> >> It has two mutually exclusive background planes (same Z level) + one
> >> overlay plane.
> >
> > What's the difference between the two background planes?
> >
> > How will generic userspace know to pick the "right" one?
>
> First primary plane cannot scale, supports RGB and C8. Second primary
> plane goes through the IPU, and as such can scale and convert pixel
> formats; it supports RGB, non-planar YUV, and multi-planar YUV.
>
> Right now the userspace apps we have will simply pick the first one
> that fits the bill.
What would be the downside of exposing just one "virtual" primary
plane, and then have the driver pick one of the two hardware planes as
appropriate per modeset?
Thanks,
pq
> >> Le sam. 27 mars 2021 à 11:24, Simon Ser <contact@emersion.fr> a
> >> écrit
> >> :
> >> > On Saturday, March 27th, 2021 at 12:22 PM, Paul Cercueil
> >> > <paul@crapouillou.net> wrote:
> >> >
> >> >> The ingenic-drm driver has two mutually exclusive primary planes
> >> >> already; so the fact that a CRTC must have one and only one
> >> primary
> >> >> plane is an invalid assumption.
> >> >
> >> > Why does this driver expose two primary planes, if it only has a
> >> > single
> >> > CRTC?
> >>
> >>
> >> _______________________________________________
> >> dri-devel mailing list
> >> dri-devel@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-29 14:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 11:22 [PATCH] drm: DON'T require each CRTC to have a unique primary plane Paul Cercueil
2021-03-27 11:24 ` Simon Ser
2021-03-27 11:26 ` Paul Cercueil
2021-03-29 8:15 ` Pekka Paalanen
2021-03-29 11:41 ` Paul Cercueil
2021-03-29 14:35 ` Pekka Paalanen [this message]
2021-03-29 15:21 ` Paul Cercueil
2021-03-29 14:07 ` Maxime Ripard
2021-03-29 14:11 ` Simon Ser
2021-03-29 15:32 ` Paul Cercueil
2021-03-29 15:36 ` Simon Ser
2021-03-30 6:55 ` Pekka Paalanen
2021-03-29 15:15 ` Paul Cercueil
2021-03-29 15:35 ` Maxime Ripard
2021-03-29 15:39 ` Paul Cercueil
2021-03-29 15:42 ` Simon Ser
2021-03-29 16:15 ` Paul Cercueil
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=20210329173541.00b301ea@eldfell \
--to=ppaalanen@gmail.com \
--cc=airlied@linux.ie \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=od@zcrc.me \
--cc=paul@crapouillou.net \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.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