summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/rockchip/rockchip_drm_gem.h
diff options
context:
space:
mode:
authorDaniel Kurtz <djkurtz@chromium.org>2015-01-12 09:58:23 +0300
committerMark Yao <mark.yao@rock-chips.com>2015-03-16 05:07:12 +0300
commitf76c83b580043d55b2899719da61fe000839812d (patch)
treeade110f4c117f8c16d952640073e1f2984ccceb8 /drivers/gpu/drm/rockchip/rockchip_drm_gem.h
parent03be70050c85768e9ce7c0d0887110d1b629e127 (diff)
downloadlinux-f76c83b580043d55b2899719da61fe000839812d.tar.xz
drm/rockchip: Only alloc a kmap for fbdev gem object
In general, the data in drm/rockchip GEM objects is never accessed by the kernel. The objects are either accessed by a GPU, by display controller DMA, or by mmap'ing them to user space. Thus, these buffers need not be mapped into kernel address space. The only exception is the fbdev framebuffer(s), which may be written in-kernel by fbcon. Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
Diffstat (limited to 'drivers/gpu/drm/rockchip/rockchip_drm_gem.h')
-rw-r--r--drivers/gpu/drm/rockchip/rockchip_drm_gem.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_gem.h b/drivers/gpu/drm/rockchip/rockchip_drm_gem.h
index 67bcebe90003..ad22618473a4 100644
--- a/drivers/gpu/drm/rockchip/rockchip_drm_gem.h
+++ b/drivers/gpu/drm/rockchip/rockchip_drm_gem.h
@@ -41,7 +41,8 @@ int rockchip_gem_mmap_buf(struct drm_gem_object *obj,
struct vm_area_struct *vma);
struct rockchip_gem_object *
- rockchip_gem_create_object(struct drm_device *drm, unsigned int size);
+ rockchip_gem_create_object(struct drm_device *drm, unsigned int size,
+ bool alloc_kmap);
void rockchip_gem_free_object(struct drm_gem_object *obj);