summaryrefslogtreecommitdiff
path: root/Documentation/DMA-API.txt
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2019-08-30 09:46:57 +0300
committerChristoph Hellwig <hch@lst.de>2019-09-04 12:13:19 +0300
commit1fa0682448acd5198f79c1d28ee1292a27ae406d (patch)
tree36d9a2d25bfb2cec04f7479580fe0db8e69448bc /Documentation/DMA-API.txt
parent212836a9929f0c91214a8a1879e6e41be0e26a6f (diff)
downloadlinux-1fa0682448acd5198f79c1d28ee1292a27ae406d.tar.xz
dma-mapping: remove dma_release_declared_memory
This function is entirely unused given that declared memory is generally provided by platform setup code. Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'Documentation/DMA-API.txt')
-rw-r--r--Documentation/DMA-API.txt11
1 files changed, 0 insertions, 11 deletions
diff --git a/Documentation/DMA-API.txt b/Documentation/DMA-API.txt
index 9c4dd3d779ed..2d8d2fed7317 100644
--- a/Documentation/DMA-API.txt
+++ b/Documentation/DMA-API.txt
@@ -603,17 +603,6 @@ For reasons of efficiency, most platforms choose to track the declared
region only at the granularity of a page. For smaller allocations,
you should use the dma_pool() API.
-::
-
- void
- dma_release_declared_memory(struct device *dev)
-
-Remove the memory region previously declared from the system. This
-API performs *no* in-use checking for this region and will return
-unconditionally having removed all the required structures. It is the
-driver's job to ensure that no parts of this memory region are
-currently in use.
-
Part III - Debug drivers use of the DMA-API
-------------------------------------------