Lines Matching refs:dma
16 #include <linux/dma-buf.h>
17 #include <linux/dma-fence.h>
24 #include <linux/dma-resv.h>
29 #include <uapi/linux/dma-buf.h>
32 #include "dma-buf-sysfs-stats.h"
33 #include "dma-buf-process-info.h"
95 * Any fences that a dma-buf poll can wait on should be signaled
96 * before releasing dma-buf. This is the responsibility of each
100 * dma-buf while still having pending operation to the buffer.
423 * The name of the dma-buf buffer can only be set when the dma-buf is not
425 * name of the dma-buf if the same piece of memory is used for multiple
430 * the dma-buf.
432 * Returns 0 on success. If the dma-buf buffer is already attached to
573 * DOC: dma buf device access
1117 * There are mutliple reasons for supporting CPU access to a dma buffer object:
1125 * Since for most kernel internal dma-buf accesses need the entire buffer, a
1135 * that the dma-buf layer keeps a reference count for all vmap access and
1147 * There is no special interfaces, userspace simply calls mmap on the dma-buf
1154 * CPU and GPU domains are being accessed through dma-buf at the same time.
1156 * forward directly to existing dma-buf device drivers vfunc hooks. Userspace
1160 * - mmap dma-buf fd
1176 * interfaces with a imported dma-buf buffer object as with a native buffer
1181 * The assumption in the current dma-buf interfaces is that redirecting the
1195 * equally achieve that for a dma-buf object.
1322 * dma-buf buffer.