Lines Matching defs:buffer
3 * Framework for buffer objects that can be shared across devices/subsystems.
67 static char *dmabuffs_dname(struct dentry *dentry, char *buffer, int buflen)
80 return dynamic_dname(dentry, buffer, buflen, "/%s:%s", dentry->d_name.name, ret > 0 ? name : "");
100 * dma-buf while still having pending operation to the buffer.
195 /* override open() and close() to provide buffer mmap count */
220 /* check if buffer supports mmap */
225 /* check for overflowing the buffer's size */
244 /* only support discovering the end of the buffer,
265 * To support cross-device and cross-driver synchronization of buffer access
423 * The name of the dma-buf buffer can only be set when the dma-buf is not
428 * @dmabuf: [in] dmabuf buffer that will be renamed.
432 * Returns 0 on success. If the dma-buf buffer is already attached to
575 * For device DMA access to a shared DMA buffer the usual sequence of operations
580 * buffer object into a &dma_buf. It then exports that &dma_buf to userspace
583 * 2. Userspace passes this file-descriptors to all drivers it wants this buffer
585 * dma_buf_get(). Then the buffer is attached to the device using
591 * 3. Once the buffer is attached to all devices userspace can initiate DMA
592 * access to the shared buffer. In the kernel this is done by calling
595 * 4. Once a driver is done with a shared buffer it needs to call
605 * with this buffer, so it can be exported.
606 * Also connect the allocator specific data and ops to the buffer.
767 * dma_buf_put - decreases refcount of the buffer
768 * @dmabuf: [in] buffer to reduce refcount of
812 * @dmabuf: [in] buffer to attach device to.
919 * @dmabuf: [in] buffer to attach device to.
934 * @dmabuf: [in] buffer to detach from.
1057 * dma_buf_unmap_attachment - unmaps and decreases usecount of the buffer;might
1060 * @attach: [in] attachment to unmap buffer from
1061 * @sg_table: [in] scatterlist info of the buffer to unmap
1098 * @dmabuf: [in] buffer which is moving
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
1144 * framework already supported this and for DMA buffer file descriptors to
1165 * - munmap once you don't need the buffer any more
1176 * interfaces with a imported dma-buf buffer object as with a native buffer
1179 * use a different way to mmap a buffer rather invasive.
1218 * @dmabuf: [in] buffer to prepare cpu access for.
1281 * @dmabuf: [in] buffer to complete cpu access for.
1319 * @dmabuf: [in] buffer that should back the vma
1322 * dma-buf buffer.
1340 /* check if buffer supports mmap */
1350 /* check for overflowing the buffer's size */
1376 * dma_buf_vmap - Create virtual mapping for the buffer object into kernel
1378 * @dmabuf: [in] buffer to vmap
1428 * @dmabuf: [in] buffer to vunmap