From: Gustavo Padovan <gustavo@padovan.org>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org,
Daniel Stone <daniels@collabora.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Rob Clark <robdclark@gmail.com>,
Greg Hackmann <ghackmann@google.com>,
John Harrison <John.C.Harrison@Intel.com>,
laurent.pinchart@ideasonboard.com, seanpaul@google.com,
marcheu@google.com, m.chehab@samsung.com,
Sumit Semwal <sumit.semwal@linaro.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Brian Starkey <brian.starkey@arm.com>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: [PATCH v7 0/3] drm: add explict fencing
Date: Tue, 8 Nov 2016 15:54:47 +0900 [thread overview]
Message-ID: <1478588090-8664-1-git-send-email-gustavo@padovan.org> (raw)
From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Hi,
This is yet another version of the DRM fences patches. Please refer
to the cover letter[1] in a previous version to check for more details.
In v7 we now have split most of the out_fences code into
prepare_crtc_signaling() and unprepare_crtc_signaling() with improved error
handling. More details on the v7 changes are embedded in each commit's
message.
Robert Foss managed to port Android's drm_hwcomposer to the new HWC2 API and
added support to fences. Current patches can be seen here:
https://git.collabora.com/cgit/user/robertfoss/drm_hwcomposer.git/log/?h=hwc2_fence_v1
He managed to run AOSP on top of padovan/fences kernel branch with full fence
support on qemu/virgl and msm db410c. That means we already have a working
open source userspace using the explicit fencing implementation.
Also i-g-t testing are available at:
https://git.collabora.com/cgit/user/padovan/intel-gpu-tools.git/log/
Please review!
Gustavo
[1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1253822.html
---
Gustavo Padovan (3):
drm/fence: add in-fences support
drm/fence: add fence timeline to drm_crtc
drm/fence: add out-fences support
drivers/gpu/drm/Kconfig | 1 +
drivers/gpu/drm/drm_atomic.c | 247 ++++++++++++++++++++++++++++++------
drivers/gpu/drm/drm_atomic_helper.c | 3 +
drivers/gpu/drm/drm_crtc.c | 45 +++++++
drivers/gpu/drm/drm_plane.c | 1 +
include/drm/drm_atomic.h | 1 +
include/drm/drm_crtc.h | 55 ++++++++
7 files changed, 311 insertions(+), 42 deletions(-)
--
2.5.5
next reply other threads:[~2016-11-08 6:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 6:54 Gustavo Padovan [this message]
2016-11-08 6:54 ` [PATCH v7 1/3] drm/fence: add in-fences support Gustavo Padovan
2016-11-08 11:06 ` Daniel Vetter
2016-11-08 15:27 ` Brian Starkey
2016-11-08 16:11 ` Daniel Vetter
2016-11-08 6:54 ` [PATCH v7 2/3] drm/fence: add fence timeline to drm_crtc Gustavo Padovan
2016-11-08 6:54 ` [PATCH v7 3/3] drm/fence: add out-fences support Gustavo Padovan
2016-11-08 13:15 ` Daniel Vetter
2016-11-09 2:39 ` Gustavo Padovan
2016-11-09 10:18 ` Daniel Vetter
2016-11-08 15:36 ` Brian Starkey
2016-11-08 10:35 ` [PATCH v7 0/3] drm: add explict fencing Chris Wilson
2016-11-08 11:32 ` Daniel Vetter
2016-11-08 11:45 ` Chris Wilson
2016-11-08 12:43 ` Daniel Vetter
2016-11-08 12:52 ` Chris Wilson
2016-11-08 12:44 ` Christian König
2016-11-08 12:52 ` Daniel Vetter
2016-11-08 13:18 ` Daniel Vetter
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=1478588090-8664-1-git-send-email-gustavo@padovan.org \
--to=gustavo@padovan.org \
--cc=John.C.Harrison@Intel.com \
--cc=brian.starkey@arm.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ghackmann@google.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marcheu@google.com \
--cc=robdclark@gmail.com \
--cc=seanpaul@google.com \
--cc=sumit.semwal@linaro.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).