summaryrefslogtreecommitdiffstats
path: root/drivers/iommu/shmobile-iommu.c
diff options
context:
space:
mode:
authorMarek Szyprowski <m.szyprowski@samsung.com>2014-02-25 13:01:09 +0100
committerMarek Szyprowski <m.szyprowski@samsung.com>2014-02-28 11:55:18 +0100
commit68efd7d2fb32c2606f1da318b6a851d933813f27 (patch)
tree2b86d6df14c10b8d288ad61624e485b429a1de18 /drivers/iommu/shmobile-iommu.c
parentarm: dma-mapping: Add support to extend DMA IOMMU mappings (diff)
downloadlinux-68efd7d2fb32c2606f1da318b6a851d933813f27.tar.xz
linux-68efd7d2fb32c2606f1da318b6a851d933813f27.zip
arm: dma-mapping: remove order parameter from arm_iommu_create_mapping()
The 'order' parameter for IOMMU-aware dma-mapping implementation was introduced mainly as a hack to reduce size of the bitmap used for tracking IO virtual address space. Since now it is possible to dynamically resize the bitmap, this hack is not needed and can be removed without any impact on the client devices. This way the parameters for arm_iommu_create_mapping() becomes much easier to understand. 'size' parameter now means the maximum supported IO address space size. The code will allocate (resize) bitmap in chunks, ensuring that a single chunk is not larger than a single memory page to avoid unreliable allocations of size larger than PAGE_SIZE in atomic context. Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Diffstat (limited to 'drivers/iommu/shmobile-iommu.c')
-rw-r--r--drivers/iommu/shmobile-iommu.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/iommu/shmobile-iommu.c b/drivers/iommu/shmobile-iommu.c
index 7a3b928fad1c..464acda0bbc4 100644
--- a/drivers/iommu/shmobile-iommu.c
+++ b/drivers/iommu/shmobile-iommu.c
@@ -343,7 +343,7 @@ static int shmobile_iommu_add_device(struct device *dev)
mapping = archdata->iommu_mapping;
if (!mapping) {
mapping = arm_iommu_create_mapping(&platform_bus_type, 0,
- L1_LEN << 20, 0);
+ L1_LEN << 20);
if (IS_ERR(mapping))
return PTR_ERR(mapping);
archdata->iommu_mapping = mapping;