From: Hyungwon Hwang <human.hwang@samsung.com>
To: dri-devel@lists.freedesktop.org, human.hwang@samsung.com
Subject: [PATCH 3/6] xf86drmMode: Make atomic request structures visible
Date: Wed, 19 Aug 2015 09:58:41 +0900 [thread overview]
Message-ID: <1439945924-22630-3-git-send-email-human.hwang@samsung.com> (raw)
In-Reply-To: <1439945924-22630-1-git-send-email-human.hwang@samsung.com>
This patch makes 'struct _drmModeAtomicReqItem' and 'struct
_drmModeAtomicReq' visible from outside. This is needed for userspace
applications to use those structures when calling drmModeAtomicCommit().
Signed-off-by: Hyungwon Hwang <human.hwang@samsung.com>
---
xf86drmMode.c | 14 --------------
xf86drmMode.h | 12 ++++++++++++
2 files changed, 12 insertions(+), 14 deletions(-)
diff --git a/xf86drmMode.c b/xf86drmMode.c
index 82c4c91..cf3fa21 100644
--- a/xf86drmMode.c
+++ b/xf86drmMode.c
@@ -1164,20 +1164,6 @@ int drmModeObjectSetProperty(int fd, uint32_t object_id, uint32_t object_type,
return DRM_IOCTL(fd, DRM_IOCTL_MODE_OBJ_SETPROPERTY, &prop);
}
-typedef struct _drmModeAtomicReqItem drmModeAtomicReqItem, *drmModeAtomicReqItemPtr;
-
-struct _drmModeAtomicReqItem {
- uint32_t object_id;
- uint32_t property_id;
- uint64_t value;
-};
-
-struct _drmModeAtomicReq {
- uint32_t cursor;
- uint32_t size_items;
- drmModeAtomicReqItemPtr items;
-};
-
drmModeAtomicReqPtr drmModeAtomicAlloc(void)
{
drmModeAtomicReqPtr req;
diff --git a/xf86drmMode.h b/xf86drmMode.h
index fe14078..ec05ed8 100644
--- a/xf86drmMode.h
+++ b/xf86drmMode.h
@@ -485,6 +485,18 @@ extern int drmModeObjectSetProperty(int fd, uint32_t object_id,
uint64_t value);
+struct _drmModeAtomicReqItem {
+ uint32_t object_id;
+ uint32_t property_id;
+ uint64_t value;
+};
+typedef struct _drmModeAtomicReqItem drmModeAtomicReqItem, *drmModeAtomicReqItemPtr;
+
+struct _drmModeAtomicReq {
+ uint32_t cursor;
+ uint32_t size_items;
+ drmModeAtomicReqItemPtr items;
+};
typedef struct _drmModeAtomicReq drmModeAtomicReq, *drmModeAtomicReqPtr;
extern drmModeAtomicReqPtr drmModeAtomicAlloc(void);
--
2.4.3
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-08-19 0:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 0:58 [PATCH 1/6] xf86drmMode: remove the trailing white spaces Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 2/6] xf86drmMode: separate drmModeAtomicCommit() and drmModeAtomicCleanup() Hyungwon Hwang
2015-08-20 16:17 ` Emil Velikov
2015-08-21 4:54 ` Hyungwon Hwang
2015-08-21 6:42 ` Pekka Paalanen
2015-08-21 7:18 ` Hyungwon Hwang
2015-08-21 10:08 ` Pekka Paalanen
2015-08-19 0:58 ` Hyungwon Hwang [this message]
2015-08-20 16:23 ` [PATCH 3/6] xf86drmMode: Make atomic request structures visible Emil Velikov
2015-08-21 6:06 ` Hyungwon Hwang
2015-08-21 6:44 ` Pekka Paalanen
2015-08-21 7:35 ` Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 4/6] modetest: remove the trailing white spaces Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 5/6] modetest: add atomic modeset support Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 6/6] modetest: add atomic page flip support Hyungwon Hwang
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=1439945924-22630-3-git-send-email-human.hwang@samsung.com \
--to=human.hwang@samsung.com \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox