Lines Matching refs:DMA

5 hardware (DMA) access across multiple device drivers and subsystems, and
17 Shared DMA Buffers
23 Any device driver which wishes to be a part of DMA buffer sharing, can do so as
55 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
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
97 CPU Access to DMA Buffer Objects
130 DMA Fences
134    :doc: DMA fences overview
136 DMA Fence Cross-Driver Contract
142 DMA Fence Signalling Annotations
148 DMA Fences Functions Reference
163 DMA Fence Array
172 DMA Fence uABI/Sync File
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