[PATCH v2 07/16] drm: omapdrm: gem: Remove omap_drm_private has_dmm field

The field is set to true iff the usergart field is not NULL. Test usergart instead. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_drv.c | 2 +- drivers/gpu/drm/omapdrm/omap_drv.h | 1 - drivers/gpu/drm/omapdrm/omap_fbdev.c | 2 +- drivers/gpu/drm/omapdrm/omap_gem.c | 5 +

[PATCH v2 05/16] drm: omapdrm: gem: Group functions by purpose

Divide the GEM implementation in groups of functions to improve readability. No code change is performed by this commit. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_gem.c | 140 +++-- 1 file changed, 87 insertions(+), 53 deletions(-) diff --

[PATCH v2 08/16] drm: omapdrm: gem: Mask out private flags passed from userspace

The 8 high order bits of the buffer flags are reserved for internal use. Mask them out from the flags passed by userspace. Signed-off-by: Laurent Pinchart --- Changes since v1: - Make the OMAP_BO_USER_MASK definition private --- drivers/gpu/drm/omapdrm/omap_drv.c | 11 --- 1 file chang

[PATCH v2 09/16] drm: omapdrm: gem: Clean up GEM objects memory flags

The driver assumes that only objects backed by shmem need to be mapped through DMM. While this is true with the current code, the assumption won't hold with dma_buf import support. Condition the mapping based on whether the buffer has been allocated using the DMA mapping API instead and clean up t

[PATCH v2 10/16] drm: omapdrm: gem: Free the correct memory object

The GEM object free handler frees memory allocated by the driver using the pointer to the drm_gem_object instead of the pointer to the omap_gem_object that embeds it. This doesn't cause any issue in practice as the drm_gem_object is the first field of omap_gem_object, but would cause memory corrupt

[PATCH v2 11/16] drm: omapdrm: gem: Fix GEM object destroy in error path

Use the omap_gem_free_object() function to destroy the GEM object in the omap_gem_new_handle() error path instead of doing it manually (and incorrectly). Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_gem.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/d

[PATCH v2 12/16] drm: omapdrm: gem: Don't free mmap offset twice

The drm_gem_free_mmap_offset() call in omap_gem_free_object() is redundant as the same function is called from drm_gem_object_release(). Remove it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_gem.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/gpu/drm/omapdrm/

[PATCH v2 13/16] drm: omapdrm: gem: Simplify error handling when creating GEM object

The goto error statement end up just returning NULL without performing any cleanup, replace it with a direct return. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_gem.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/omapdrm/omap_gem

[PATCH v2 15/16] drm: omapdrm: gem: Refactor GEM object allocation

Split the individual steps of GEM object allocation and initialization clearly. This improves readability and prepares for dma_buf import support. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_gem.c | 75 ++ 1 file changed, 43 insertions(+),

[PATCH v2 14/16] drm: omapdrm: gem: Remove check for impossible condition

The GEM object can't be tiled without a usergart as that condition is checked and considered as an error when creating the GEM object. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_gem.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/gpu/drm/omapdrm/omap_gem.c

[PATCH v2 16/16] drm: omapdrm: gem: Implement dma_buf import

OMAP GEM objects backed by dma_buf reuse the current OMAP GEM object support as much as possible. If the imported buffer is physically contiguous its physical address will be used directly, reusing the OMAP_BO_MEM_DMA_API code paths. Otherwise it will be mapped through the TILER using a pages list

drm/msm: msm-next for 4.5

Hi Dave, Main thing this time around is DSI support for msm8960/apq8064, which should be helpful for getting an upstream kernel working on nexus7/nexus4/etc. The following changes since commit 663a233eef643b38f36c05535cb5c9a4972edcc1: Merge branch 'drm-header-fixes' of https://github.com/Gabri

[Bug 93217] [tonga] [powerplay] Radon M395X isn't initialised with the powerplay branch

ssignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151214/46fd5472/attachment.html>

[Bug 93217] [tonga] [powerplay] Radon M395X isn't initialised with the powerplay branch

crubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151214/6e6e4de7/attachment.html>

[Bug 93217] [tonga] [powerplay] Radon M395X isn't initialised with the powerplay branch

attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151214/bacd0797/attachment.html>

[PATCH] drm: Use the driver's gem_object_free function from CMA helpers.

VC4 wraps the CMA objects in its own structures, so it needs to do its own teardown (waiting for GPU to finish, updating bo_stats tracking). The other CMA drivers are using drm_gem_cma_free_object as their gem_free_object, so this should be a no-op for them. Signed-off-by: Eric Anholt --- driver

[PATCH] android: fix warning when releasing active sync point

Userspace can close the sync device while there are still active fence points, in which case kernel produces the following warning: [ 43.853176] [ cut here ] [ 43.857834] WARNING: CPU: 0 PID: 892 at /mnt/host/source/src/third_party/kernel/v3.18/drivers/staging/android/

[PATCH v2 13/14] ARM: dts: dove: add DT GPU support

Hi Lucas, On lun., déc. 14 2015, Lucas Stach wrote: > Dove maintainers, > > can you please tell me if you prefer the DT changes to go along with the > rest of the etnaviv series through the DRM tree, or plan on picking this > separate? I prefer to take the DT change in the mvebu tree. I was w

<    1   2