Lines Matching refs:any
22 - takes care of any migration of scatterlist - for all (shared) users of this
117 Whenever a buffer-user wants to use the buffer for any DMA, it asks for
142 accessing at the same time (for reading, maybe), or any other kind of sharing
182 dma_buf->ops->detach(), if provided by exporter, for any housekeeping bits.
220 and then allow further {map,unmap}_dma_buf operations from any buffer-user
246 1. Prepare access, which invalidate any necessary caches and make the object
249 3. Finish access, which will flush any necessary cpu caches and free reserved
298 atomic dma_buf kmaps at the same time (in any given process context).
306 any preparations that might fail in begin_cpu_access.
327 unpinning of any pinned resources). The result of any dma_buf kmap calls
369 subsystems shows that no driver seems to do any nefarious thing like syncing
404 Exporters that shoot down mappings (for any reasons) shall not do any
444 flag be set when the dma-buf fd is created. So any API provided by