All of lore.kernel.org
 help / color / mirror / Atom feed
From: sourab.gupta@intel.com
To: intel-gfx@lists.freedesktop.org
Cc: "Cc: Daniel Vetter" <daniel.vetter@intel.com>,
	Sourab Gupta <sourab.gupta@intel.com>,
	"Cc: Jesse Barnes" <jesse.barnes@intel.com>,
	Akash Goel <akash.goel@intel.com>,
	"Cc: Chris Wilson" <chris.wilson@intel.com>
Subject: [RFC 1/2] include/drm: Rename the 'pad' field to 'flags' of gem_create ioctl
Date: Wed,  5 Mar 2014 17:03:18 +0530	[thread overview]
Message-ID: <1394019199-8723-2-git-send-email-sourab.gupta@intel.com> (raw)
In-Reply-To: <1394019199-8723-1-git-send-email-sourab.gupta@intel.com>

From: Sourab Gupta <sourab.gupta@intel.com>

Renamed the 'pad' field to 'flags' of gem_create ioctl.
Also, added a new flag I915_CPU_MAP_NOT_NEEDED which can be passed with
gem_create ioctl.

Signed-off-by: Sourab Gupta <sourab.gupta@intel.com>

Signed-off-by: Akash Goel <akash.goel@intel.com>
---
 include/drm/i915_drm.h |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/include/drm/i915_drm.h b/include/drm/i915_drm.h
index 2f4eb8c..39ff300 100644
--- a/include/drm/i915_drm.h
+++ b/include/drm/i915_drm.h
@@ -431,7 +431,8 @@ struct drm_i915_gem_create {
 	 * Object handles are nonzero.
 	 */
 	__u32 handle;
-	__u32 pad;
+	__u32 flags;
+#define I915_CPU_MAP_NOT_NEEDED 0x1
 };
 
 struct drm_i915_gem_pread {
-- 
1.7.9.5

  reply	other threads:[~2014-03-05 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 11:33 [RFC 0/2] New flag to indicate no cpu mapping requirement for buffer object sourab.gupta
2014-03-05 11:33 ` sourab.gupta [this message]
2014-03-05 11:33 ` [RFC 2/2] intel: Added a new flag 'BO_ALLOC_CPU_MAP_NOT_NEEDED' flag in bo_alloc sourab.gupta

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=1394019199-8723-2-git-send-email-sourab.gupta@intel.com \
    --to=sourab.gupta@intel.com \
    --cc=akash.goel@intel.com \
    --cc=chris.wilson@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jesse.barnes@intel.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.