From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Simon Ser <contact@emersion.fr>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915: add immutable zpos plane properties
Date: Tue, 16 Apr 2019 16:42:42 +0300 [thread overview]
Message-ID: <20190416134242.GG24299@intel.com> (raw)
In-Reply-To: <fb960571-5ab6-01a3-41fc-e34d4439680b@linux.intel.com>
On Tue, Apr 16, 2019 at 03:28:15PM +0200, Maarten Lankhorst wrote:
> Op 16-04-2019 om 15:20 schreef Ville Syrjälä:
> > On Sat, Apr 13, 2019 at 11:13:27AM +0000, Simon Ser wrote:
> >> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>
> >> This adds basic immutable support for the zpos property. The zpos increases
> >> from bottom to top: primary, sprites, cursor.
> > I was thinking a bit about how we might go about testing this.
> >
> > We probably want a basic test that just checks that if any
> > plane has a zpos prop then all planes should have it.
> This would be a good test for BAT.
> > A functional test would stack the planes up in some way and
> > compare against a software rendered reference. IIRC there was
> > a zpos test case floating around but that depended on alpha
> > blending which we don't necessarily have.
>
> But with semi-overlapping planes you would accomplish the same, without alpha dependency.
>
> Something like this?
>
> [BG] [Sprite 1] [Cursor]
> [Primary] [Sprite 2]
Should probably be good enough. Though I was pondering is there a
way to position an arbitraty number of planes such that the
resulting picture has a visible region for every possible
combination of planes?
>
> Perhaps primary fullscreen to prevent issues with hw that doesn't support partial planes?
I guess. And maybe a second test that disables the primary
so that we can also get the bg color into the picture?
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-16 13:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 22:19 [PATCH] drm/i915: add immutable zpos plane properties Simon Ser
2019-03-30 0:11 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-03-30 0:37 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-04-02 7:49 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-02 11:34 ` ✓ Fi.CI.IGT: " Patchwork
2019-04-02 12:35 ` [PATCH] " Joonas Lahtinen
2019-04-02 14:36 ` Simon Ser
2019-04-03 8:28 ` Joonas Lahtinen
2019-04-03 16:21 ` [PATCH v2] " Simon Ser
2019-04-09 18:49 ` Simon Ser
2019-04-13 11:13 ` [PATCH v3] " Simon Ser
2019-04-15 20:33 ` Maarten Lankhorst
2019-04-16 13:20 ` Ville Syrjälä
2019-04-16 13:28 ` Maarten Lankhorst
2019-04-16 13:42 ` Ville Syrjälä [this message]
2019-04-16 18:13 ` Maarten Lankhorst
2019-04-16 19:04 ` Ville Syrjälä
2019-04-17 20:35 ` Simon Ser
2019-04-18 5:20 ` Simon Ser
2019-04-19 17:10 ` Simon Ser
2019-04-03 18:08 ` ✓ Fi.CI.BAT: success for drm/i915: add immutable zpos plane properties (rev2) Patchwork
2019-04-04 12:39 ` ✓ Fi.CI.IGT: " Patchwork
2019-04-04 12:44 ` Patchwork
2019-04-13 11:57 ` ✓ Fi.CI.BAT: success for drm/i915: add immutable zpos plane properties (rev3) Patchwork
2019-04-13 13:52 ` ✓ Fi.CI.IGT: " Patchwork
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=20190416134242.GG24299@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=contact@emersion.fr \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
/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