Searched hist:f76c83b580043d55b2899719da61fe000839812d (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/gpu/drm/rockchip/ |
| H A D | rockchip_drm_gem.h | diff f76c83b580043d55b2899719da61fe000839812d Mon Jan 12 00:58:23 CST 2015 Daniel Kurtz <djkurtz@chromium.org> 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>
|
| H A D | rockchip_drm_gem.c | diff f76c83b580043d55b2899719da61fe000839812d Mon Jan 12 00:58:23 CST 2015 Daniel Kurtz <djkurtz@chromium.org> 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>
|