dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/5] drm/amdgpu: Page flip improvement and related cleanups
Date: Fri, 10 Jun 2016 17:57:08 +0900	[thread overview]
Message-ID: <1465549033-16561-1-git-send-email-michel@daenzer.net> (raw)

The main purpose of this series is patch 5, which can avoid delaying
flips for a frame in some cases. It depends on patch 4 to prevent flips
from taking effect too early, which in turn depends on the core DRM
patch 2.

Patches 1 & 3 are cleanups I noticed while working on the other patches.

Mario, it would be great if you could run these through your rigorous
vblank testing.

[PATCH 1/5] drm: Only handle _DRM_VBLANK_NEXTONMISS once
[PATCH 2/5] drm: Keep track of last vblank sequence waited for
[PATCH 3/5] drm/amdgpu: Unpin BO if we can't get fences in
[PATCH 4/5] drm/amdgpu: Wait for end of last waited-for vblank before
[PATCH 5/5] drm/amdgpu: Set MASTER_UPDATE_MODE to 0 again
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-06-10  8:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10  8:57 Michel Dänzer [this message]
2016-06-10  8:57 ` [PATCH 1/5] drm: Only handle _DRM_VBLANK_NEXTONMISS once Michel Dänzer
2016-06-10  8:57 ` [PATCH 2/5] drm: Keep track of last vblank sequence waited for per-file-descriptor Michel Dänzer
2016-06-10  8:57 ` [PATCH 3/5] drm/amdgpu: Unpin BO if we can't get fences in amdgpu_crtc_page_flip Michel Dänzer
2016-06-10  8:57 ` [PATCH 4/5] drm/amdgpu: Wait for end of last waited-for vblank before programming flip Michel Dänzer
2016-06-10 14:43   ` Daniel Vetter
2016-06-13  1:54     ` Michel Dänzer
2016-06-13  8:06       ` Daniel Vetter
2016-06-13  8:58         ` Michel Dänzer
2016-06-13 14:06           ` Daniel Vetter
2016-06-14  2:09             ` Michel Dänzer
2016-06-14  5:53               ` Daniel Vetter
2016-06-14  7:25                 ` Michel Dänzer
2016-06-14  8:06                   ` Daniel Vetter
2016-06-15  8:03                     ` Michel Dänzer
2016-06-15  9:23                       ` Daniel Vetter
2016-06-16  2:15                         ` Michel Dänzer
2016-06-16  8:14                           ` Daniel Vetter
2016-06-14  8:12                 ` Chris Wilson
2016-06-10  8:57 ` [PATCH 5/5] drm/amdgpu: Set MASTER_UPDATE_MODE to 0 again Michel Dänzer
2016-06-10  9:01 ` [PATCH 0/5] drm/amdgpu: Page flip improvement and related cleanups Christian König

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=1465549033-16561-1-git-send-email-michel@daenzer.net \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.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