Lines Matching refs:may

23 a dma_addr_t directly because there may be translation between its physical
35 without having to worry about caching effects.  (You may however need
44 It also returns a <dma_handle> which may be cast to an unsigned integer the
49 minimum allocation length may be as big as a page, so you should
55 implementation may choose to ignore flags that affect the location of
75 may only be called with IRQs enabled.
198 The direction for both APIs may be converted freely by casting.
208 Further, contiguous kernel virtual space may not be contiguous as
221 the driver may specify various platform-dependent flags to restrict
227 dma_mask may not apply if the platform has an IOMMU (a device which
229 portable, device driver writers may *not* assume that such an IOMMU
237 may not be known at compile time, the API will not enforce this
247 may write to it at any point, it should be DMA_BIDIRECTIONAL (see
251 accesses data that may be changed by the device.  This memory should
260 are flushed from the processor) and once before the data may be
262 cache lines are updated with data that the device may have changed).
299 Returns: the number of DMA address segments mapped (this may be shorter
485 Notes: This API may return a number *larger* than the actual cache
540 dma_alloc_coherent() may no longer be accessed directly, but instead
546 memory may be declared per device.
594 example warning message may look like this: