linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: dri-devel@lists.freedesktop.org, 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,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Brian Starkey <brian.starkey@arm.com>,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH v8 0/3] drm: add explict fencing
Date: Fri, 11 Nov 2016 23:17:57 +0900	[thread overview]
Message-ID: <20161111141757.GM26677@joana> (raw)
In-Reply-To: <1478873759-6580-1-git-send-email-gustavo@padovan.org>

Subject was supposed to be v9! sorry about that.

2016-11-11 Gustavo Padovan <gustavo@padovan.org>:

> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> 
> Hi,
> 
> Another iteration after Brian comments. Please refer to the cover letter[1] in
> a previous version to check for more details.
> 
> The changes since the last version can be seen in commit message on each patch.
> 
> 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        | 257 +++++++++++++++++++++++++++++-------
>  drivers/gpu/drm/drm_atomic_helper.c |   5 +
>  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              |  56 ++++++++
>  7 files changed, 321 insertions(+), 45 deletions(-)
> 
> -- 
> 2.5.5
> 

  parent reply	other threads:[~2016-11-11 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 14:15 [PATCH v8 0/3] drm: add explict fencing Gustavo Padovan
2016-11-11 14:15 ` [PATCH v8 1/3] drm/fence: add in-fences support Gustavo Padovan
2016-11-11 15:42   ` Sean Paul
2016-11-11 14:15 ` [PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc Gustavo Padovan
2016-11-11 14:15 ` [PATCH v8 3/3] drm/fence: add out-fences support Gustavo Padovan
2016-11-11 16:48   ` Sean Paul
2016-11-11 17:11     ` Daniel Vetter
2016-11-11 17:21       ` Sean Paul
2016-11-11 17:38   ` Brian Starkey
2016-11-11 14:17 ` Gustavo Padovan [this message]
2016-11-11 14:50 ` [PATCH v8 0/3] drm: add explict fencing Robert Foss
  -- strict thread matches above, loose matches on Subject: below --
2016-11-11  5:16 Gustavo Padovan

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=20161111141757.GM26677@joana \
    --to=gustavo.padovan@collabora.com \
    --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=gustavo@padovan.org \
    --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 \
    /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).