public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH] kms_cursor_legacy: Keep primary plane enabled for XRGB overlay fallback
Date: Tue, 9 Jun 2020 19:49:22 +0300	[thread overview]
Message-ID: <20200609164922.GT6112@intel.com> (raw)
In-Reply-To: <4d5f6d18-0f17-3dcb-aabe-1f0dc585c894@daenzer.net>

On Tue, Jun 09, 2020 at 06:40:57PM +0200, Michel Dänzer wrote:
> On 2020-06-09 4:50 p.m., Ville Syrjälä wrote:
> > On Fri, Jun 05, 2020 at 04:37:20PM +0200, Michel Dänzer wrote:
> >> From: Michel Dänzer <mdaenzer@redhat.com>
> >>
> >> This allows the test to work on setups where the primary plane cannot
> >> be disabled while the CRTC is enabled.
> >>
> >> It should make no difference for the output.
> >>
> >> Signed-off-by: Michel Dänzer <mdaenzer@redhat.com>
> >> ---
> >>  tests/kms_cursor_legacy.c | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/tests/kms_cursor_legacy.c b/tests/kms_cursor_legacy.c
> >> index 9306e54b..344442e8 100644
> >> --- a/tests/kms_cursor_legacy.c
> >> +++ b/tests/kms_cursor_legacy.c
> >> @@ -326,6 +326,7 @@ static void transition_nonblocking(igt_display_t *display, enum pipe pipe_id,
> >>  
> >>  		igt_assert(ret == -EINVAL);
> >>  
> >> +		igt_plane_set_fb(primary, prim_fb);
> >>  		igt_plane_set_fb(sprite, prim_fb);
> >>  	}
> >>  	igt_display_commit_atomic(display, DRM_MODE_ATOMIC_NONBLOCK | DRM_MODE_PAGE_FLIP_EVENT, display);
> > 
> > Mixes up the argb vs. xrgb with the primary vs. no primary thing a bit.
> > No idea why the test even wants an argb fb for the sprite tbh. Also not
> > sure there's an actual reason for toggling the primary on/off.
> > 
> > But meh. Patch seems OK to me.
> > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Thanks!
> 
> Are you going to apply the patch?

Pushed. Thanks for the patch.

> 
> 
> > PS.
> > I am wondering a bit how a driver that can't turn off the primary
> > will fare with some of the ther tests. IIRC quite a few might assume
> > you don't need an fb for the primary when using the atomic uapi...
> 
> Maybe I'm not yet running some tests I should be, but the only kms_*
> tests that seem to fail specifically because of this (with amdgpu DC)
> are the plane-use-after-nonblocking-unbind(-fencing) sub-tests of
> kms_atomic_transition.
> 
> 
> -- 
> Earthling Michel Dänzer               |               https://redhat.com
> Libre software enthusiast             |             Mesa and X developer

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-06-09 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 14:37 [igt-dev] [PATCH] kms_cursor_legacy: Keep primary plane enabled for XRGB overlay fallback Michel Dänzer
2020-06-05 15:13 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-05 16:28 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-06-08 16:29   ` Michel Dänzer
2020-06-09 14:50 ` [igt-dev] [PATCH] " Ville Syrjälä
2020-06-09 16:40   ` Michel Dänzer
2020-06-09 16:49     ` Ville Syrjälä [this message]
2020-06-11  8:25 ` [igt-dev] ✗ GitLab.Pipeline: failure for " Patchwork
2020-06-11  8:39   ` Michel Dänzer

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=20200609164922.GT6112@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    /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