Lines Matching refs:dma_fence_signal
45 * dma_fence_signal(). Fences are associated with a context, allocated through
89 * drivers should annotate all code required to reach dma_fence_signal(),
191 * any deadlocks between dma_fence_wait() and dma_fence_signal() can't be caught
205 * dma_fence_signal(B);
214 * dma_fence_signal(B);
222 * dma_fence_signal() is called. Un-annotated code can contain deadlock issues,
231 * calls dma_fence_signal() purely as an optimization, but is not required to
233 * which calls dma_fence_signal(), while the mandatory completion path goes
245 * far as deadlocks with dma_fence_wait() against dma_fence_signal() are
257 * required to eventually complete &dma_fence by calling dma_fence_signal().
324 * Unlike dma_fence_signal(), this function must be called with &dma_fence.lock
358 * dma_fence_signal - signal completion of a fence
370 int dma_fence_signal(struct dma_fence *fence)
389 EXPORT_SYMBOL(dma_fence_signal);
550 * the fence alive until after it signals with dma_fence_signal(). The callback