Lines Matching refs:must

18 To get the dma_ API, you must #include <linux/dma-mapping.h>.  This
70 size and dma_handle must all be the same as those passed into
71 dma_alloc_coherent().  cpu_addr must be the virtual address returned by
81 To get this part of the dma_ API, you must #include <linux/dmapool.h>
96 for use with a given device.  It must be called in a context which
102 in bytes, and must be a power of two).  If your device has no boundary
104 from this pool must not cross 4KByte boundaries.
129 dma_pool_destroy() frees the resources of the pool.  It must be
215 Further, the DMA address of the memory must be within the
234 correctly, the mapped region must begin exactly on a cache line
243 DMA_TO_DEVICE synchronisation must be done after the last modification
250 DMA_FROM_DEVICE synchronisation must be done before the driver
258 you must always sync bidirectional memory twice: once before the
269 must be identical to those passed in (and returned) by the mapping
308 does, 0 is returned and a driver must take appropriate action. It is
339 must be the same as those and passed in to the scatter/gather mapping
342 Note: <nents> must be the number you passed in, *not* the number of
359 and device. With the sync_sg API, all the parameters must be the same
364 Notes:  You must do this:
474 Free memory allocated by the nonconsistent API.  All parameters must
482 alignment *and* width that you must observe when either mapping
496 continuing on for size.  Again, you *must* observe the cache line
514 size is the size of the area (must be multiples of PAGE_SIZE).
524 One or both of these flags must be present.
535 must correspond to a passed in flag (i.e. no returning DMA_MEMORY_IO
541 must be accessed using the correct bus functions.  If your driver
579 The DMA-API as described above has some constraints. DMA addresses must be