From: Gustavo Padovan <gustavo@padovan.org>
To: dri-devel@lists.freedesktop.org
Cc: marcheu@google.com, Daniel Stone <daniels@collabora.com>,
seanpaul@google.com, Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
John Harrison <John.C.Harrison@Intel.com>,
m.chehab@samsung.com
Subject: [PATCH v12 0/3] drm: add explicit fencing
Date: Tue, 15 Nov 2016 22:06:38 +0900 [thread overview]
Message-ID: <1479215201-2672-1-git-send-email-gustavo@padovan.org> (raw)
From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Hi,
Yet another iteration, v12 now after working on the changes proposed by Chris
Wilson.
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 ran 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 with all tests suggested in v7 included:
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 | 255 +++++++++++++++++++++++++++++-------
drivers/gpu/drm/drm_atomic_helper.c | 5 +
drivers/gpu/drm/drm_crtc.c | 52 ++++++++
drivers/gpu/drm/drm_crtc_internal.h | 10 ++
drivers/gpu/drm/drm_plane.c | 1 +
include/drm/drm_atomic.h | 1 +
include/drm/drm_crtc.h | 40 ++++++
8 files changed, 320 insertions(+), 45 deletions(-)
--
2.5.5
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-11-15 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 13:06 Gustavo Padovan [this message]
2016-11-15 13:06 ` [PATCH v12 1/3] drm/fence: add in-fences support Gustavo Padovan
2016-11-15 13:06 ` [PATCH v12 2/3] drm/fence: add fence timeline to drm_crtc Gustavo Padovan
2016-11-15 14:37 ` [PATCH] " Gustavo Padovan
2016-11-16 8:11 ` Daniel Vetter
2016-11-16 9:02 ` Gustavo Padovan
2016-11-16 9:43 ` Daniel Vetter
2016-11-15 13:06 ` [PATCH v12 3/3] drm/fence: add out-fences support Gustavo Padovan
2016-11-16 9:10 ` Chris Wilson
2016-11-15 14:26 ` [PATCH v12 0/3] drm: add explicit fencing Sean Paul
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=1479215201-2672-1-git-send-email-gustavo@padovan.org \
--to=gustavo@padovan.org \
--cc=John.C.Harrison@Intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=marcheu@google.com \
--cc=seanpaul@google.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;
as well as URLs for NNTP newsgroup(s).