to maintain a separate api for synchronization. I've left the android
trace events in place, but the core fence events should already be
sufficient for debugging.
v2:
- Call fence_remove_callback in sync_fence_free if not all fences have
fired.
v3:
- Merge Colin Cross' bugfixes
On Thu, Jun 19, 2014 at 5:28 AM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
thierry.red...@gmail.com wrote:
With these changes, can we pull the android sync logic out of
drivers/staging/ now?
Afaik the google guys never really looked at this and
On Fri, Feb 7, 2014 at 8:43 AM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Sat, Dec 21, 2013 at 07:42:17AM -0500, Rob Clark wrote:
On Fri, Dec 20, 2013 at 7:43 PM, Colin Cross ccr...@android.com wrote:
dma_buf_map_attachment and dma_buf_vmap can return NULL or
ERR_PTR on a error
On Mon, Jan 13, 2014 at 4:31 AM, Maarten Lankhorst
maarten.lankho...@canonical.com wrote:
The kernel fence implementation doesn't use event queues, but needs
to perform the same wake up. The symbol is not exported, since the
fence implementation is not built as a module.
Signed-off-by:
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 ccr...@android.com
---
drivers/base/dma-buf.c
On Thu, Jul 19, 2012 at 2:15 PM, Tejun Heo t...@kernel.org wrote:
Hello,
kthread_worker was introduced together with concurrency managed
workqueue to serve workqueue users which need a special dedicated
worker - e.g. RT scheduling. This is minimal queue / flush / flush
all iterface on top