diff options
Diffstat (limited to 'Documentation/dma-buf-sharing.txt')
-rw-r--r-- | Documentation/dma-buf-sharing.txt | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/Documentation/dma-buf-sharing.txt b/Documentation/dma-buf-sharing.txt index 0188903bc9e1..4966b1be42ac 100644 --- a/Documentation/dma-buf-sharing.txt +++ b/Documentation/dma-buf-sharing.txt | |||
@@ -302,7 +302,11 @@ Access to a dma_buf from the kernel context involves three steps: | |||
302 | void dma_buf_vunmap(struct dma_buf *dmabuf, void *vaddr) | 302 | void dma_buf_vunmap(struct dma_buf *dmabuf, void *vaddr) |
303 | 303 | ||
304 | The vmap call can fail if there is no vmap support in the exporter, or if it | 304 | The vmap call can fail if there is no vmap support in the exporter, or if it |
305 | runs out of vmalloc space. Fallback to kmap should be implemented. | 305 | runs out of vmalloc space. Fallback to kmap should be implemented. Note that |
306 | the dma-buf layer keeps a reference count for all vmap access and calls down | ||
307 | into the exporter's vmap function only when no vmapping exists, and only | ||
308 | unmaps it once. Protection against concurrent vmap/vunmap calls is provided | ||
309 | by taking the dma_buf->lock mutex. | ||
306 | 310 | ||
307 | 3. Finish access | 311 | 3. Finish access |
308 | 312 | ||