Lines Matching refs:access

28 - needs a mechanism to get access to the scatterlist that makes up this buffer
29    in memory, mapped into its own address space, so it can access the same area
41 4. When needed, buffer-user requests access to the buffer from exporter
115 4. When needed, buffer-user requests access to the buffer
118    access to the buffer using dma_buf_map_attachment API. At least one attach to
202    Bracketing of DMA access with {map,unmap}_dma_buf operations is essential
216     map_dma_buf until all outstanding access is completed (as signalled by
231 Kernel cpu access to a dma-buf buffer object
234 The motivation to allow cpu access from the kernel to a dma-buf object from the
246 1. Prepare access, which invalidate any necessary caches and make the object
247    available for cpu access.
249 3. Finish access, which will flush any necessary cpu caches and free reserved
252 1. Prepare access
254    Before an importer can access a dma_buf object with the cpu from the kernel
255    context, it needs to notify the exporter of the access that is about to
264    cpu access - the exporter might need to allocate or swap-in and pin the
265    backing storage. The exporter also needs to ensure that cpu access is
266    coherent for the given range and access direction. The range and access
268    access outside of the range or with a different direction (read instead of
276    To support dma_buf objects residing in highmem cpu access is page-based using
318    the dma-buf layer keeps a reference count for all vmap access and calls down
323 3. Finish access
345    In many processing pipelines it is sometimes required that the cpu can access
348    it's ideal if the dma_buf fd itself can be used to access the backing storage
360    Similar to the motivation for kernel cpu access it is again important that
434   access to buffers, via the leaked fd, to which it should otherwise
435   not be permitted access.