diff options
| author | Robin Murphy <Robin.Murphy@arm.com> | 2015-07-29 19:46:04 +0100 |
|---|---|---|
| committer | David Keitel <dkeitel@codeaurora.org> | 2016-03-22 11:15:17 -0700 |
| commit | d0bbb1ad175cde0e6cc0a2a6714e2251460c8c20 (patch) | |
| tree | 913265d2f49cd5ac5b116a9fa831728b260d89cd /include/uapi/linux | |
| parent | 5c214164ac012429344746635d011b94b80ea169 (diff) | |
iommu/io-pgtable-arm: Allow appropriate DMA API use
Currently, users of the LPAE page table code are (ab)using dma_map_page()
as a means to flush page table updates for non-coherent IOMMUs. Since
from the CPU's point of view, creating IOMMU page tables *is* passing
DMA buffers to a device (the IOMMU's page table walker), there's little
reason not to use the DMA API correctly.
Allow IOMMU drivers to opt into DMA API operations for page table
allocation and updates by providing their appropriate device pointer.
The expectation is that an LPAE IOMMU should have a full view of system
memory, so use streaming mappings to avoid unnecessary pressure on
ZONE_DMA, and treat any DMA translation as a warning sign.
Change-Id: I954414051c3cdee407613fea9447f15cfa94fada
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
[pdaly@codeaurora.org Call io_pgtable_alloc_pages()]
Diffstat (limited to 'include/uapi/linux')
0 files changed, 0 insertions, 0 deletions
