All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schake <stschake@gmail.com>
To: eric@anholt.net
Cc: airlied@linux.ie, linux-rpi-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org,
	Stefan Schake <stschake@gmail.com>
Subject: [PATCH v2 0/3] drm/vc4: Syncobj import export
Date: Wed, 25 Apr 2018 00:03:44 +0200	[thread overview]
Message-ID: <1524607427-12876-1-git-send-email-stschake@gmail.com> (raw)

v2 drops the extra syncobj parameter and gets rid of the submit flags
since 0 is never a valid syncobj handle.

This series allows userspace to submit syncobj handles for importing
a fence to wait on or exporting the job fence as part of submission.

The primary use of this is to enable native fence fd support in Mesa.
Userspace implementation is under review and available here:

https://patchwork.freedesktop.org/series/42081/

Stefan Schake (3):
  drm/vc4: Syncobj import support
  drm/vc4: Export fence through syncobj
  drm/vc4: Enable syncobj support

 drivers/gpu/drm/vc4/vc4_drv.c |  3 ++-
 drivers/gpu/drm/vc4/vc4_drv.h |  1 +
 drivers/gpu/drm/vc4/vc4_gem.c | 60 ++++++++++++++++++++++++++++++++++++++-----
 include/uapi/drm/vc4_drm.h    | 13 +++++++---
 4 files changed, 65 insertions(+), 12 deletions(-)

-- 
2.7.4

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-04-24 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 22:03 Stefan Schake [this message]
2018-04-24 22:03 ` [PATCH v2 1/3] drm/vc4: Syncobj import support Stefan Schake
2018-04-24 22:03 ` [PATCH v2 2/3] drm/vc4: Export fence through syncobj Stefan Schake
2018-04-24 22:03 ` [PATCH v2 3/3] drm/vc4: Enable syncobj support Stefan Schake
2018-04-30 23:05 ` [PATCH v2 0/3] drm/vc4: Syncobj import export Eric Anholt

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=1524607427-12876-1-git-send-email-stschake@gmail.com \
    --to=stschake@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=linux-rpi-kernel@lists.infradead.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 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.