All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chunming Zhou <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: Christian.Koenig-5C7GfCeVMHo@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: Chunming Zhou <david1.zhou-5C7GfCeVMHo@public.gmane.org>
Subject: [PATCH libdrm 2/8] addr cs chunk for syncobj timeline
Date: Tue, 11 Dec 2018 18:36:21 +0800	[thread overview]
Message-ID: <20181211103627.25985-2-david1.zhou@amd.com> (raw)
In-Reply-To: <20181211103627.25985-1-david1.zhou-5C7GfCeVMHo@public.gmane.org>

Signed-off-by: Chunming Zhou <david1.zhou@amd.com>
---
 include/drm/amdgpu_drm.h | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/include/drm/amdgpu_drm.h b/include/drm/amdgpu_drm.h
index 1ceec56d..a3c067dd 100644
--- a/include/drm/amdgpu_drm.h
+++ b/include/drm/amdgpu_drm.h
@@ -517,6 +517,8 @@ struct drm_amdgpu_gem_va {
 #define AMDGPU_CHUNK_ID_SYNCOBJ_IN      0x04
 #define AMDGPU_CHUNK_ID_SYNCOBJ_OUT     0x05
 #define AMDGPU_CHUNK_ID_BO_HANDLES      0x06
+#define AMDGPU_CHUNK_ID_SYNCOBJ_TIMELINE_WAIT    0x07
+#define AMDGPU_CHUNK_ID_SYNCOBJ_TIMELINE_SIGNAL  0x08
 
 struct drm_amdgpu_cs_chunk {
 	__u32		chunk_id;
@@ -592,6 +594,13 @@ struct drm_amdgpu_cs_chunk_sem {
 	__u32 handle;
 };
 
+struct drm_amdgpu_cs_chunk_syncobj {
+	__u32 handle;
+	__u32 flags;
+	__u64 point;
+};
+
+
 #define AMDGPU_FENCE_TO_HANDLE_GET_SYNCOBJ	0
 #define AMDGPU_FENCE_TO_HANDLE_GET_SYNCOBJ_FD	1
 #define AMDGPU_FENCE_TO_HANDLE_GET_SYNC_FILE_FD	2
-- 
2.17.1

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2018-12-11 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 10:36 [PATCH libdrm 1/8] new syncobj extension v3 Chunming Zhou
2018-12-11 10:36 ` [PATCH libdrm 3/8] add timeline wait/query ioctl v2 Chunming Zhou
     [not found] ` <20181211103627.25985-1-david1.zhou-5C7GfCeVMHo@public.gmane.org>
2018-12-11 10:36   ` Chunming Zhou [this message]
2018-12-11 10:36   ` [PATCH libdrm 4/8] wrap syncobj timeline query/wait APIs for amdgpu v3 Chunming Zhou
2018-12-11 10:36   ` [PATCH libdrm 5/8] add timeline signal/transfer ioctls v2 Chunming Zhou
2018-12-11 10:36   ` [PATCH libdrm 6/8] expose timeline signal/export/import interfaces v2 Chunming Zhou
2018-12-11 10:36   ` [PATCH libdrm 8/8] add syncobj timeline tests v3 Chunming Zhou
2018-12-11 10:36 ` [PATCH libdrm 7/8] wrap transfer interfaces Chunming Zhou
2019-04-01  9:58 [PATCH libdrm 1/8] new syncobj extension v3 Chunming Zhou
     [not found] ` <20190401095838.10165-1-david1.zhou-5C7GfCeVMHo@public.gmane.org>
2019-04-01  9:58   ` [PATCH libdrm 2/8] addr cs chunk for syncobj timeline Chunming Zhou
2019-04-09  9:04 [PATCH libdrm 1/8] new syncobj extension v3 Chunming Zhou
2019-04-09  9:04 ` [PATCH libdrm 2/8] addr cs chunk for syncobj timeline Chunming Zhou

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=20181211103627.25985-2-david1.zhou@amd.com \
    --to=david1.zhou-5c7gfcevmho@public.gmane.org \
    --cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.