Lines Matching defs:dma_fence_signal
46 * dma_fence_signal(). Fences are associated with a context, allocated through
90 * drivers should annotate all code required to reach dma_fence_signal(),
226 * any deadlocks between dma_fence_wait() and dma_fence_signal() can't be caught
240 * dma_fence_signal(B);
249 * dma_fence_signal(B);
257 * dma_fence_signal() is called. Un-annotated code can contain deadlock issues,
266 * calls dma_fence_signal() purely as an optimization, but is not required to
268 * which calls dma_fence_signal(), while the mandatory completion path goes
280 * far as deadlocks with dma_fence_wait() against dma_fence_signal() are
292 * required to eventually complete &dma_fence by calling dma_fence_signal().
436 * Unlike dma_fence_signal(), this function must be called with &dma_fence.lock
449 * dma_fence_signal - signal completion of a fence
461 int dma_fence_signal(struct dma_fence *fence)
480 EXPORT_SYMBOL(dma_fence_signal);