Lines Matching full:apis

18 the normal DMA map, unmap, and sync APIs when programming a device to do DMA.
19 These APIs use the device DMA attributes and kernel-wide settings to determine
61 The primary swiotlb APIs are swiotlb_tbl_map_single() and
77 swiotlb also provides "sync" APIs that correspond to the dma_sync_*() APIs that
79 device. The swiotlb "sync" APIs cause a CPU copy of the data between the
80 original buffer and the bounce buffer. Like the dma_sync_*() APIs, the swiotlb
81 "sync" APIs support doing a partial sync, where only a subset of the bounce
86 The swiotlb map/unmap/sync APIs must operate without blocking, as they are
87 called by the corresponding DMA APIs which may run in contexts that cannot
262 APIs and the corresponding swiotlb APIs use the bounce buffer address as the
267 swiotlb_tbl_map_single(), but it is not passed to the other APIs. Consequently,
318 Restricted pools add swiotlb_alloc() and swiotlb_free() APIs, which are called
319 from the dma_alloc_*() and dma_free_*() APIs. The swiotlb_alloc/free() APIs