aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/DMA-mapping.txt
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@nuerscht.ch>2006-04-11 01:54:21 -0400
committerLinus Torvalds <torvalds@g5.osdl.org>2006-04-11 09:18:44 -0400
commit56b146d36db933844011d5026c6f55593037c7b8 (patch)
treee8b9bed7bf22f658f9b62bf13e512bf08f137efc /Documentation/DMA-mapping.txt
parent31cc48bfeef7a021d6e29f3454a4505edcfd6daa (diff)
[PATCH] Last DMA_xBIT_MASK cleanups
These are the last conversions of pci_set_dma_mask(), pci_set_consistent_dma_mask() and pci_dma_supported() to use DMA_xBIT_MASK constants from linux/dma-mapping.h Signed-off-by: Tobias Klauser <tklauser@nuerscht.ch> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/DMA-mapping.txt')
-rw-r--r--Documentation/DMA-mapping.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/DMA-mapping.txt b/Documentation/DMA-mapping.txt
index ee4bb73683cd..10bf4deb96aa 100644
--- a/Documentation/DMA-mapping.txt
+++ b/Documentation/DMA-mapping.txt
@@ -194,7 +194,7 @@ document for how to handle this case.
194Finally, if your device can only drive the low 24-bits of 194Finally, if your device can only drive the low 24-bits of
195address during PCI bus mastering you might do something like: 195address during PCI bus mastering you might do something like:
196 196
197 if (pci_set_dma_mask(pdev, 0x00ffffff)) { 197 if (pci_set_dma_mask(pdev, DMA_24BIT_MASK)) {
198 printk(KERN_WARNING 198 printk(KERN_WARNING
199 "mydev: 24-bit DMA addressing not available.\n"); 199 "mydev: 24-bit DMA addressing not available.\n");
200 goto ignore_this_device; 200 goto ignore_this_device;
@@ -212,7 +212,7 @@ functions (for example a sound card provides playback and record
212functions) and the various different functions have _different_ 212functions) and the various different functions have _different_
213DMA addressing limitations, you may wish to probe each mask and 213DMA addressing limitations, you may wish to probe each mask and
214only provide the functionality which the machine can handle. It 214only provide the functionality which the machine can handle. It
215is important that the last call to pci_set_dma_mask() be for the 215is important that the last call to pci_set_dma_mask() be for the
216most specific mask. 216most specific mask.
217 217
218Here is pseudo-code showing how this might be done: 218Here is pseudo-code showing how this might be done: