From: Mikko Perttunen <mperttunen@nvidia.com>
To: thierry.reding@gmail.com
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: [PATCH 2/3] drm/tegra: Add sync file support to submit interface
Date: Thu, 9 Mar 2017 19:57:17 +0200 [thread overview]
Message-ID: <20170309175718.14843-3-mperttunen@nvidia.com> (raw)
In-Reply-To: <20170309175718.14843-1-mperttunen@nvidia.com>
Adds ability to pass sync file based prefences and get back
sync file based postfences during job submission. Both
fence fd's are passed in the `fence` field. A new `flags`
field is used to specify if the prefence should be waited
or a postfence created.
Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
---
include/uapi/drm/tegra_drm.h | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/include/uapi/drm/tegra_drm.h b/include/uapi/drm/tegra_drm.h
index d954f8c33321..b85689c15d8f 100644
--- a/include/uapi/drm/tegra_drm.h
+++ b/include/uapi/drm/tegra_drm.h
@@ -117,6 +117,9 @@ struct drm_tegra_waitchk {
__u32 thresh;
};
+#define DRM_TEGRA_SUBMIT_WAIT_FENCE_FD (1 << 0)
+#define DRM_TEGRA_SUBMIT_CREATE_FENCE_FD (1 << 1)
+
struct drm_tegra_submit {
__u64 context;
__u32 num_syncpts;
@@ -129,9 +132,10 @@ struct drm_tegra_submit {
__u64 cmdbufs;
__u64 relocs;
__u64 waitchks;
- __u32 fence; /* Return value */
+ __u32 fence;
+ __u32 flags;
- __u32 reserved[5]; /* future expansion */
+ __u32 reserved[4]; /* future expansion */
};
#define DRM_TEGRA_GEM_TILING_MODE_PITCH 0
--
2.11.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-09 18:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 17:57 [PATCH 0/3] Tegra Host1x dma_fence/sync_file support Mikko Perttunen
[not found] ` <20170309175718.14843-1-mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-09 17:57 ` [PATCH 1/3] gpu: host1x: Add support for DMA fences Mikko Perttunen
2017-03-09 17:57 ` Mikko Perttunen [this message]
2017-03-09 17:57 ` [PATCH 3/3] drm/tegra: Support for sync file-based fences in submit Mikko Perttunen
[not found] ` <20170309175718.14843-4-mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-03-13 7:15 ` Thierry Reding
[not found] ` <20170313071500.GB15513-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2017-03-13 9:07 ` Mikko Perttunen
2017-03-13 17:46 ` Thierry Reding
2017-03-09 18:58 ` [PATCH 0/3] Tegra Host1x dma_fence/sync_file support Daniel Vetter
[not found] ` <CAKMK7uH=_9wXDS+yN4e60878j7kDSo+isrePOeDBP5HnHu-tjw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-09 19:09 ` Mikko Perttunen
2017-03-10 12:43 ` Daniel Vetter
[not found] ` <20170310124334.6v4tmmn5vxqvhs2w-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-03-13 8:55 ` Mikko Perttunen
[not found] ` <fcca70a0-8bfe-d1b6-329f-ded53fd98a72-/1wQRMveznE@public.gmane.org>
2017-03-13 10:22 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2018-01-11 22:22 [PATCH 0/3] drm/tegra: Add support for fence FDs Thierry Reding
[not found] ` <20180111222249.29105-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-11 22:22 ` [PATCH 2/3] drm/tegra: Add sync file support to submit interface Thierry Reding
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=20170309175718.14843-3-mperttunen@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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