X-Git-Url: http://git.rot13.org/?a=blobdiff_plain;f=Documentation%2FDMA-mapping.txt;h=63392c9132b4d08bf32f3fab82cc0c14c39e15b1;hb=f9bcda7760e1373615c9f6d9ce24209b0ab97de1;hp=7c717699032c90f403432ef793cfeed8c359fe7b;hpb=61fb46c5b3578fda7cc780e8bc53b3e8f8c1a143;p=powerpc.git diff --git a/Documentation/DMA-mapping.txt b/Documentation/DMA-mapping.txt index 7c71769903..63392c9132 100644 --- a/Documentation/DMA-mapping.txt +++ b/Documentation/DMA-mapping.txt @@ -698,12 +698,12 @@ these interfaces. Remember that, as defined, consistent mappings are always going to be SAC addressable. The first thing your driver needs to do is query the PCI platform -layer with your devices DAC addressing capabilities: +layer if it is capable of handling your devices DAC addressing +capabilities: - int pci_dac_set_dma_mask(struct pci_dev *pdev, u64 mask); + int pci_dac_dma_supported(struct pci_dev *hwdev, u64 mask); -This routine behaves identically to pci_set_dma_mask. You may not -use the following interfaces if this routine fails. +You may not use the following interfaces if this routine fails. Next, DMA addresses using this API are kept track of using the dma64_addr_t type. It is guaranteed to be big enough to hold any