Lines Matching refs:memory
10 Part II describes extensions for supporting non-consistent memory
33 Consistent memory is memory for which a write by either the device or
37 devices to read that memory.)
39 This routine allocates a region of <size> bytes of consistent memory.
48 Note: consistent memory can be expensive on some platforms, and the
50 consolidate your requests for consistent memory as much as possible.
56 the returned memory, like GFP_DMA).
62 Wraps dma_alloc_coherent() and also zeroes the returned memory if the
69 Free a region of consistent memory you previously allocated. dev,
83 Many drivers need lots of small DMA-coherent memory regions for DMA
103 crossing restrictions, pass 0 for alloc; passing 4096 says memory allocated
110 This allocates memory from the pool; the returned memory will meet the
122 This puts memory back into the pool. The pool is what was passed to
124 were returned when that routine allocated the memory being freed.
131 memory back to the pool before you destroy it.
140 Checks to see if the device can support DMA to the memory described by
179 is the minimum required to cover all of memory. Examining the
195 Maps a piece of processor virtual memory so it can be accessed by the
196 device and returns the DMA address of the memory.
203 DMA_TO_DEVICE data is going from the memory to the device
204 DMA_FROM_DEVICE data is coming from the device to the memory
207 Notes: Not all memory regions in a machine can be mapped by this API.
209 physical memory. Since this API does not provide any scatter/gather
211 contiguous piece of memory. For this reason, memory to be mapped by
215 Further, the DMA address of the memory must be within the
218 the memory ANDed with the dma_mask is still equal to the DMA
219 address, then the device can perform DMA to the memory). To
220 ensure that the memory allocated by kmalloc is within the dma_mask,
228 maps an I/O DMA address to a physical memory address). However, to be
233 line width. In order for memory mapped by this API to operate
244 of the memory region by the software and before it is handed off to
245 the driver. Once this primitive is used, memory covered by this
251 accesses data that may be changed by the device. This memory should
256 isn't sure if the memory was modified before being handed off to the
258 you must always sync bidirectional memory twice: once before the
259 memory is handed off to the device (to make sure all memory changes
370 - before *and* after handing memory to the device if the memory is
411 you could pass an attribute DMA_ATTR_FOO when mapping memory
457 choose to return either consistent or non-consistent memory as it sees
459 have all the correct and necessary sync points for this memory in the
460 driver should it choose to return non-consistent memory.
462 Note: where the platform can return consistent memory, it will
465 Warning: Handling non-consistent memory is a real pain. You should
468 that simply cannot make consistent memory.
474 Free memory allocated by the nonconsistent API. All parameters must
483 memory or doing partial flushes.
494 Do a partial sync of memory that was allocated by
504 Declare region of memory to be handed out by dma_alloc_coherent() when
505 it's asked for coherent memory for this device.
507 phys_addr is the CPU physical address to which the memory is currently
511 with to actually address this memory (this will be handed out as the
518 DMA_MEMORY_MAP - request that the memory returned from
521 DMA_MEMORY_IO - request that the memory returned from
526 DMA_MEMORY_INCLUDES_CHILDREN - make the declared memory be allocated by
527 dma_alloc_coherent of any child devices of this one (for memory residing
530 DMA_MEMORY_EXCLUSIVE - only allocate memory from the declared regions.
531 Do not allow dma_alloc_coherent() to fall back to system memory when
532 it's out of memory in the declared region.
539 Note, for DMA_MEMORY_IO returns, all subsequent memory returned by
546 memory may be declared per device.
555 Remove the memory region previously declared from the system. This
558 driver's job to ensure that no parts of this memory region are
573 address of the memory, or an error (via PTR_ERR()) if any part of the
592 about what DMA memory was allocated for which device. If this code detects an
600 forcedeth 0000:00:08.0: DMA-API: device driver frees DMA memory with wrong
647 happen when it runs out of memory or if it was