aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorMatthew Wilcox <matthew@wil.cx>2007-10-17 02:31:27 -0400
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-10-17 11:43:06 -0400
commitd1482f40c975e883f209aab659ec75a0afd84075 (patch)
treeb5104116cd40cdd2d06bd1ae555c9558efed6829 /Documentation
parent814073620a2eb520c8bb38e0038fd1c78011fe21 (diff)
Update DMA-mapping documentation
A couple of updates haven't considered whether the documentation makes sense as a whole any more. Three changes here: - Remove the reference to the "DAC Addressing for Address Space Hungry Devices" section which was deleted by Jan Beulich. - Remove the comment about DMA_24BIT_MASK which became obsolete when Tobias Klauser changed the code to actually use DMA_24BIT_MASK. - Remove the section "64-bit DMA and DAC cycle support" since it's fully covered above, and contains a reference to the section deleted by Jan. Signed-off-by: Matthew Wilcox <willy@linux.intel.com> Cc: "David S. Miller" <davem@davemloft.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/DMA-mapping.txt20
1 files changed, 0 insertions, 20 deletions
diff --git a/Documentation/DMA-mapping.txt b/Documentation/DMA-mapping.txt
index 3c8ae020b6a7..d84f89dbf921 100644
--- a/Documentation/DMA-mapping.txt
+++ b/Documentation/DMA-mapping.txt
@@ -189,12 +189,6 @@ smaller mask as pci_set_dma_mask(). However for the rare case that a
189device driver only uses consistent allocations, one would have to 189device driver only uses consistent allocations, one would have to
190check the return value from pci_set_consistent_dma_mask(). 190check the return value from pci_set_consistent_dma_mask().
191 191
192If your 64-bit device is going to be an enormous consumer of DMA
193mappings, this can be problematic since the DMA mappings are a
194finite resource on many platforms. Please see the "DAC Addressing
195for Address Space Hungry Devices" section near the end of this
196document for how to handle this case.
197
198Finally, if your device can only drive the low 24-bits of 192Finally, if your device can only drive the low 24-bits of
199address during PCI bus mastering you might do something like: 193address during PCI bus mastering you might do something like:
200 194
@@ -203,8 +197,6 @@ address during PCI bus mastering you might do something like:
203 "mydev: 24-bit DMA addressing not available.\n"); 197 "mydev: 24-bit DMA addressing not available.\n");
204 goto ignore_this_device; 198 goto ignore_this_device;
205 } 199 }
206[Better use DMA_24BIT_MASK instead of 0x00ffffff.
207See linux/include/dma-mapping.h for reference.]
208 200
209When pci_set_dma_mask() is successful, and returns zero, the PCI layer 201When pci_set_dma_mask() is successful, and returns zero, the PCI layer
210saves away this mask you have provided. The PCI layer will use this 202saves away this mask you have provided. The PCI layer will use this
@@ -652,18 +644,6 @@ It is planned to completely remove virt_to_bus() and bus_to_virt() as
652they are entirely deprecated. Some ports already do not provide these 644they are entirely deprecated. Some ports already do not provide these
653as it is impossible to correctly support them. 645as it is impossible to correctly support them.
654 646
655 64-bit DMA and DAC cycle support
656
657Do you understand all of the text above? Great, then you already
658know how to use 64-bit DMA addressing under Linux. Simply make
659the appropriate pci_set_dma_mask() calls based upon your cards
660capabilities, then use the mapping APIs above.
661
662It is that simple.
663
664Well, not for some odd devices. See the next section for information
665about that.
666
667 Optimizing Unmap State Space Consumption 647 Optimizing Unmap State Space Consumption
668 648
669On many platforms, pci_unmap_{single,page}() is simply a nop. 649On many platforms, pci_unmap_{single,page}() is simply a nop.