summaryrefslogtreecommitdiffstats
path: root/kernel/dma
diff options
context:
space:
mode:
authorNicolas Saenz Julienne <nsaenzjulienne@suse.de>2019-11-07 16:06:45 +0100
committerChristoph Hellwig <hch@lst.de>2019-11-11 10:52:19 +0100
commite380a0394c36a3a878c858418d5dd7f5f195b6fc (patch)
tree03b188c0d608d1c8c78cd7f0a4d867351f9f8cb0 /kernel/dma
parentb12d66278dd627cbe1ea7c000aa4715aaf8830c8 (diff)
downloadlinux-e380a0394c36a3a878c858418d5dd7f5f195b6fc.tar.gz
linux-e380a0394c36a3a878c858418d5dd7f5f195b6fc.tar.bz2
linux-e380a0394c36a3a878c858418d5dd7f5f195b6fc.zip
x86/PCI: sta2x11: use default DMA address translation
The devices found behind this PCIe chip have unusual DMA mapping constraints as there is an AMBA interconnect placed in between them and the different PCI endpoints. The offset between physical memory addresses and AMBA's view is provided by reading a PCI config register, which is saved and used whenever DMA mapping is needed. It turns out that this DMA setup can be represented by properly setting 'dma_pfn_offset', 'dma_bus_mask' and 'dma_mask' during the PCI device enable fixup. And ultimately allows us to get rid of this device's custom DMA functions. Aside from the code deletion and DMA setup, sta2x11_pdev_to_mapping() is moved to avoid warnings whenever CONFIG_PM is not enabled. Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'kernel/dma')
0 files changed, 0 insertions, 0 deletions