diff options
author | Vinod Koul <vinod.koul@intel.com> | 2016-10-03 05:48:06 +0200 |
---|---|---|
committer | Vinod Koul <vinod.koul@intel.com> | 2016-10-03 05:48:06 +0200 |
commit | ed58a112b0f57f2673cd483d45d82de1ad890e9a (patch) | |
tree | 36e92dd23787c646bd5c8a40b9d9e7e39dbd476e /Documentation | |
parent | Merge branch 'topic/ioatdma' into for-linus (diff) | |
parent | dma-debug: fix ia64 build, use PHYS_PFN (diff) | |
download | linux-ed58a112b0f57f2673cd483d45d82de1ad890e9a.tar.xz linux-ed58a112b0f57f2673cd483d45d82de1ad890e9a.zip |
Merge branch 'topic/iommu' into for-linus
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/DMA-API.txt | 22 |
1 files changed, 17 insertions, 5 deletions
diff --git a/Documentation/DMA-API.txt b/Documentation/DMA-API.txt index 1d26eeb6b5f6..6b20128fab8a 100644 --- a/Documentation/DMA-API.txt +++ b/Documentation/DMA-API.txt @@ -277,14 +277,26 @@ and <size> parameters are provided to do partial page mapping, it is recommended that you never use these unless you really know what the cache width is. +dma_addr_t +dma_map_resource(struct device *dev, phys_addr_t phys_addr, size_t size, + enum dma_data_direction dir, unsigned long attrs) + +void +dma_unmap_resource(struct device *dev, dma_addr_t addr, size_t size, + enum dma_data_direction dir, unsigned long attrs) + +API for mapping and unmapping for MMIO resources. All the notes and +warnings for the other mapping APIs apply here. The API should only be +used to map device MMIO resources, mapping of RAM is not permitted. + int dma_mapping_error(struct device *dev, dma_addr_t dma_addr) -In some circumstances dma_map_single() and dma_map_page() will fail to create -a mapping. A driver can check for these errors by testing the returned -DMA address with dma_mapping_error(). A non-zero return value means the mapping -could not be created and the driver should take appropriate action (e.g. -reduce current DMA mapping usage or delay and try again later). +In some circumstances dma_map_single(), dma_map_page() and dma_map_resource() +will fail to create a mapping. A driver can check for these errors by testing +the returned DMA address with dma_mapping_error(). A non-zero return value +means the mapping could not be created and the driver should take appropriate +action (e.g. reduce current DMA mapping usage or delay and try again later). int dma_map_sg(struct device *dev, struct scatterlist *sg, |