Lines Matching full:dma
4 The dma-buf subsystem provides the framework for sharing buffers for
5 hardware (DMA) access across multiple device drivers and subsystems, and
11 The three main components of this are: (1) dma-buf, representing a
17 Shared DMA Buffers
20 This document serves as a guide to device-driver writers on what is the dma-buf
23 Any device driver which wishes to be a part of DMA buffer sharing, can do so as
49 Any exporters or users of the dma-buf buffer sharing framework must have a
55 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
59 - Since kernel 3.12 the dma-buf FD supports the llseek system call, but only
64 If llseek on dma-buf FDs isn't support the kernel will report -ESPIPE for all
65 cases. Userspace can use this to detect support for discovering the dma-buf
81 flag be set when the dma-buf fd is created. So any API provided by
85 - Memory mapping the contents of the DMA buffer is also supported. See the
86 discussion below on `CPU Access to DMA Buffer Objects`_ for the full details.
88 - The DMA buffer FD is also pollable, see `Implicit Fence Poll Support`_ below for
91 Basic Operation and Device DMA Access
94 .. kernel-doc:: drivers/dma-buf/dma-buf.c
95 :doc: dma buf device access
97 CPU Access to DMA Buffer Objects
100 .. kernel-doc:: drivers/dma-buf/dma-buf.c
106 .. kernel-doc:: drivers/dma-buf/dma-buf.c
112 .. kernel-doc:: drivers/dma-buf/dma-buf.c
115 .. kernel-doc:: include/linux/dma-buf.h
121 .. kernel-doc:: drivers/dma-buf/dma-resv.c
124 .. kernel-doc:: drivers/dma-buf/dma-resv.c
127 .. kernel-doc:: include/linux/dma-resv.h
130 DMA Fences
133 .. kernel-doc:: drivers/dma-buf/dma-fence.c
134 :doc: DMA fences overview
136 DMA Fence Cross-Driver Contract
139 .. kernel-doc:: drivers/dma-buf/dma-fence.c
142 DMA Fence Signalling Annotations
145 .. kernel-doc:: drivers/dma-buf/dma-fence.c
148 DMA Fences Functions Reference
151 .. kernel-doc:: drivers/dma-buf/dma-fence.c
154 .. kernel-doc:: include/linux/dma-fence.h
163 DMA Fence Array
166 .. kernel-doc:: drivers/dma-buf/dma-fence-array.c
169 .. kernel-doc:: include/linux/dma-fence-array.h
172 DMA Fence uABI/Sync File
175 .. kernel-doc:: drivers/dma-buf/sync_file.c
181 Indefinite DMA Fences
196 are then imported as a DMA fence for integration into existing winsys
200 batch DMA fences for memory management instead of context preemption DMA
205 in-kernel DMA fences does not work, even when a fallback timeout is included to
208 * Only the kernel knows about all DMA fence dependencies, userspace is not aware
216 dependent upon DMA fences. If the kernel also support indefinite fences in the
217 kernel like a DMA fence, like any of the above proposal would, there is the
226 kernel [label="Kernel DMA Fences"]
244 * No future fences, proxy fences or userspace fences imported as DMA fences,
247 * No DMA fences that signal end of batchbuffer for command submission where