talos-op-linux/drivers/base/dma-buf.c, branch v4.4.4

dma-buf: move to drivers/dma-buf

2014-07-08T17:51:06+00:00

Signed-off-by: Maarten Lankhorst Acked-by: Sumit Semwal Acked-by: Daniel Vetter Signed-off-by: Greg Kroah-Hartman

dma-buf: fix trivial typo error

2014-05-05T13:28:05+00:00

Signed-off-by: Javier Martinez Canillas Signed-off-by: Jiri Kosina

Merge 3.14-rc5 into driver-core-next

2014-03-03T04:09:08+00:00

We want the fixes in here.

dma-buf: update debugfs output

2014-02-13T04:38:52+00:00

Russell King observed 'wierd' looking output from debugfs, and also suggested better ways of getting device names (use KBUILD_MODNAME, dev_name()) This patch addresses these issues to make the debugfs output correct and better looking. While at it, replace seq_printf with seq_puts to remove the checkpatch.pl warnings. Reported-by: Russell King - ARM Linux Signed-off-by: Sumit Semwal

dma-buf: avoid using IS_ERR_OR_NULL

2014-02-07T22:21:09+00:00

dma_buf_map_attachment and dma_buf_vmap can return NULL or ERR_PTR on a error. This encourages a common buggy pattern in callers: sgt = dma_buf_map_attachment(attach, DMA_BIDIRECTIONAL); if (IS_ERR_OR_NULL(sgt)) return PTR_ERR(sgt); This causes the caller to return 0 on an error. IS_ERR_OR_NULL is almost always a sign of poorly-defined error handling. This patch converts dma_buf_map_attachment to always return ERR_PTR, and fixes the callers that incorrectly handled NULL. There are a few more callers that were not checking for NULL at all, which would have dereferenced a NULL pointer later. There are also a few more callers that correctly handled NULL and ERR_PTR differently, I left those alone but they could also be modified to delete the NULL check. This patch also converts dma_buf_vmap to always return NULL. All the callers to dma_buf_vmap only check for NULL, and would have dereferenced an ERR_PTR and panic'd if one was ever returned. This is not consistent with the rest of the dma buf APIs, but matches the expectations of all of the callers. Signed-off-by: Colin Cross Reviewed-by: Rob Clark Signed-off-by: Greg Kroah-Hartman

dma-buf: Expose buffer size to userspace (v2)

2013-09-10T06:06:45+00:00

Each dma-buf has an associated size and it's reasonable for userspace to want to know what it is. Since userspace already has an fd, expose the size using the size = lseek(fd, SEEK_END, 0); lseek(fd, SEEK_CUR, 0); idiom. v2: Added Daniel's sugeested documentation, with minor fixups Signed-off-by: Christopher James Halse Rogers Reviewed-by: Daniel Vetter Tested-by: Daniel Vetter Signed-off-by: Sumit Semwal

dma-buf: Check return value of anon_inode_getfile

2013-09-10T05:59:21+00:00

anon_inode_getfile might fail, so check its return value. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Sumit Semwal

dma-buf: Replace PTR_RET with PTR_ERR_OR_ZERO

2013-07-16T06:36:01+00:00

PTR_RET is now deprecated. Use PTR_ERR_OR_ZERO instead. Signed-off-by: Sachin Kamat Signed-off-by: Rusty Russell

[media] dma-buf: Cocci spatch "ptr_ret.spatch"

2013-06-08T23:00:29+00:00

Signed-off-by: Thomas Meyer Signed-off-by: Mauro Carvalho Chehab

dma-buf: Add debugfs support

2013-05-01T11:06:22+00:00

Add debugfs support to make it easier to print debug information about the dma-buf buffers. Cc: Dave Airlie [minor fixes on init and warning fix] Cc: Dan Carpenter [remove double unlock in fail case] Signed-off-by: Sumit Semwal