iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

dma: remove external references to dma_supported

Browse Source 
Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Christoph Hellwig 2015-11-09 14:58:18 -08:00 committed by Linus Torvalds
parent c56050c700
commit 0e77acef8e
4 changed files with 3 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/DMA-API.txt
View File

@ -141,19 +141,6 @@ memory back to the pool before you destroy it.
Part Ic - DMA addressing limitations Part Ic - DMA addressing limitations
------------------------------------ ------------------------------------
int
dma_supported(struct device *dev, u64 mask)
Checks to see if the device can support DMA to the memory described by
mask.
Returns: 1 if it can and 0 if it can't.
Notes: This routine merely tests to see if the mask is possible. It
won't change the current mask settings. It is more intended as an
internal API for use by the platform than an external API for use by
driver writers.
int int
dma_set_mask_and_coherent(struct device *dev, u64 mask) dma_set_mask_and_coherent(struct device *dev, u64 mask)

2
drivers/usb/host/ehci-hcd.c
View File

@ -589,7 +589,7 @@ static int ehci_run (struct usb_hcd *hcd)
* streaming mappings for I/O buffers, like pci_map_single(), * streaming mappings for I/O buffers, like pci_map_single(),
* can return segments above 4GB, if the device allows. * can return segments above 4GB, if the device allows.
* *
* NOTE: the dma mask is visible through dma_supported(), so * NOTE: the dma mask is visible through dev->dma_mask, so
* drivers can pass this info along ... like NETIF_F_HIGHDMA, * drivers can pass this info along ... like NETIF_F_HIGHDMA,
* Scsi_Host.highmem_io, and so forth. It's readonly to all * Scsi_Host.highmem_io, and so forth. It's readonly to all
* host side drivers though. * host side drivers though.

2
drivers/usb/host/fotg210-hcd.c
View File

@ -5063,7 +5063,7 @@ static int fotg210_run(struct usb_hcd *hcd)
* streaming mappings for I/O buffers, like pci_map_single(), * streaming mappings for I/O buffers, like pci_map_single(),
* can return segments above 4GB, if the device allows. * can return segments above 4GB, if the device allows.
* *
* NOTE: the dma mask is visible through dma_supported(), so * NOTE: the dma mask is visible through dev->dma_mask, so
* drivers can pass this info along ... like NETIF_F_HIGHDMA, * drivers can pass this info along ... like NETIF_F_HIGHDMA,
* Scsi_Host.highmem_io, and so forth. It's readonly to all * Scsi_Host.highmem_io, and so forth. It's readonly to all
* host side drivers though. * host side drivers though.

2
drivers/usb/host/oxu210hp-hcd.c
View File

@ -2721,7 +2721,7 @@ static int oxu_run(struct usb_hcd *hcd)
* streaming mappings for I/O buffers, like pci_map_single(), * streaming mappings for I/O buffers, like pci_map_single(),
* can return segments above 4GB, if the device allows. * can return segments above 4GB, if the device allows.
* *
* NOTE: the dma mask is visible through dma_supported(), so * NOTE: the dma mask is visible through dev->dma_mask, so
* drivers can pass this info along ... like NETIF_F_HIGHDMA, * drivers can pass this info along ... like NETIF_F_HIGHDMA,
* Scsi_Host.highmem_io, and so forth. It's readonly to all * Scsi_Host.highmem_io, and so forth. It's readonly to all
* host side drivers though. * host side drivers though.