All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Foss <robert.foss@collabora.com>
To: dri-devel@lists.freedesktop.org, robh@kernel.org,
	salidoa@google.com, seanpaul@chromium.org, zachr@google.com
Subject: Re: [PATCH hwc v3 0/6] Implement fencing
Date: Mon, 02 Oct 2017 10:42:51 +0200	[thread overview]
Message-ID: <1506933771.32304.0.camel@collabora.com> (raw)
In-Reply-To: <20170928164031.29720-1-robert.foss@collabora.com>

Series pushed.

On Thu, 2017-09-28 at 18:40 +0200, Robert Foss wrote:
> This series removes the old thread-based synchronization utilities
> and
> replaces them with fences.
> 
> It has been tested on various platforms, including
> etnaviv/freedreno/virgl.
> 
> Robert Foss (5):
>   drm_hwcomposer: Add support for IN_FENCE_FD property to DrmPlane
>   drm_hwcomposer: Submit in-fence to DRM
>   drm_hwcomposer: Add FENCE_OUT_PTR property to DrmCrtc
>   drm_hwcomposer: Add crtc() fetcher to DrmResources
>   drm_hwcomposer: Add out-fence support
> 
> Sean Paul (1):
>   drm_hwcomposer: Remove threading
> 
>  Android.mk                |   3 -
>  drmcomposition.cpp        | 166 --------------------------------
>  drmcomposition.h          |  79 ---------------
>  drmcompositor.cpp         | 106 --------------------
>  drmcompositor.h           |  56 -----------
>  drmcompositorworker.h     |  41 --------
>  drmcrtc.cpp               |  10 ++
>  drmcrtc.h                 |   2 +
>  drmdisplaycomposition.cpp |   1 +
>  drmdisplaycomposition.h   |  19 ++++
>  drmdisplaycompositor.cpp  | 239 +++++++++---------------------------
> ----------
>  drmdisplaycompositor.h    |  36 +------
>  drmeventlistener.cpp      |   3 +
>  drmhwctwo.cpp             |  15 +--
>  drmplane.cpp              |   8 ++
>  drmplane.h                |   2 +
>  drmresources.cpp          |  58 +----------
>  drmresources.h            |   6 +-
>  glworker.cpp              |  52 +++++++++-
>  glworker.h                |  10 ++
>  20 files changed, 162 insertions(+), 750 deletions(-)
>  delete mode 100644 drmcomposition.cpp
>  delete mode 100644 drmcomposition.h
>  delete mode 100644 drmcompositor.cpp
>  delete mode 100644 drmcompositor.h
>  delete mode 100644 drmcompositorworker.h
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2017-10-02  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 16:40 [PATCH hwc v3 0/6] Implement fencing Robert Foss
2017-09-28 16:40 ` [PATCH hwc v3 1/6] drm_hwcomposer: Add support for IN_FENCE_FD property to DrmPlane Robert Foss
2017-09-28 16:40 ` [PATCH hwc v3 2/6] drm_hwcomposer: Submit in-fence to DRM Robert Foss
2017-09-28 16:40 ` [PATCH hwc v3 3/6] drm_hwcomposer: Add FENCE_OUT_PTR property to DrmCrtc Robert Foss
2017-09-28 16:40 ` [PATCH hwc v3 4/6] drm_hwcomposer: Add crtc() fetcher to DrmResources Robert Foss
2017-09-28 16:40 ` [PATCH hwc v3 5/6] drm_hwcomposer: Add out-fence support Robert Foss
2017-09-28 16:40 ` [PATCH hwc v3 6/6] drm_hwcomposer: Remove threading Robert Foss
2017-10-02  8:42 ` Robert Foss [this message]

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=1506933771.32304.0.camel@collabora.com \
    --to=robert.foss@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh@kernel.org \
    --cc=salidoa@google.com \
    --cc=seanpaul@chromium.org \
    --cc=zachr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.