Lines Matching defs:buffer
3 * Framework for buffer objects that can be shared across devices/subsystems.
44 static char *dmabuffs_dname(struct dentry *dentry, char *buffer, int buflen)
56 return dynamic_dname(dentry, buffer, buflen, "/%s:%s",
76 * dma-buf while still having pending operation to the buffer.
141 /* check if buffer supports mmap */
145 /* check for overflowing the buffer's size */
163 /* only support discovering the end of the buffer,
182 * To support cross-device and cross-driver synchronization of buffer access
333 * The name of the dma-buf buffer can only be set when the dma-buf is not
338 * @dmabuf: [in] dmabuf buffer that will be renamed.
342 * Returns 0 on success. If the dma-buf buffer is already attached to
479 * For device DMA access to a shared DMA buffer the usual sequence of operations
484 * buffer object into a &dma_buf. It then exports that &dma_buf to userspace
487 * 2. Userspace passes this file-descriptors to all drivers it wants this buffer
489 * dma_buf_get(). Then the buffer is attached to the device using
495 * 3. Once the buffer is attached to all devices userspace can initiate DMA
496 * access to the shared buffer. In the kernel this is done by calling
499 * 4. Once a driver is done with a shared buffer it needs to call
509 * with this buffer, so it can be exported.
510 * Also connect the allocator specific data and ops to the buffer.
668 * dma_buf_put - decreases refcount of the buffer
669 * @dmabuf: [in] buffer to reduce refcount of
689 * @dmabuf: [in] buffer to attach device to.
789 * @dmabuf: [in] buffer to attach device to.
805 * @dmabuf: [in] buffer to detach from.
943 * dma_buf_unmap_attachment - unmaps and decreases usecount of the buffer;might
946 * @attach: [in] attachment to unmap buffer from
947 * @sg_table: [in] scatterlist info of the buffer to unmap
981 * @dmabuf: [in] buffer which is moving
1001 * There are mutliple reasons for supporting CPU access to a dma buffer object:
1009 * Since for most kernel internal dma-buf accesses need the entire buffer, a
1028 * framework already supported this and for DMA buffer file descriptors to
1049 * - munmap once you don't need the buffer any more
1060 * interfaces with a imported dma-buf buffer object as with a native buffer
1063 * use a different way to mmap a buffer rather invasive.
1104 * @dmabuf: [in] buffer to prepare cpu access for.
1140 * @dmabuf: [in] buffer to complete cpu access for.
1164 * @dmabuf: [in] buffer that should back the vma
1167 * dma-buf buffer.
1185 /* check if buffer supports mmap */
1193 /* check for overflowing the buffer's size */
1219 * dma_buf_vmap - Create virtual mapping for the buffer object into kernel
1221 * @dmabuf: [in] buffer to vmap
1267 * @dmabuf: [in] buffer to vunmap