diff options
author | Jean-Philippe Brucker <jean-philippe@linaro.org> | 2021-06-18 18:20:59 +0300 |
---|---|---|
committer | Joerg Roedel <jroedel@suse.de> | 2021-06-25 16:02:43 +0300 |
commit | ac6d704679d343e55615551f19e9b2e18d68518b (patch) | |
tree | 0762bd7409d3fcdebca18735f17ded026a31bd4b /drivers/acpi/arm64/iort.c | |
parent | 3cf485540e7b8550936ce3602edf2f58e4007304 (diff) | |
download | linux-ac6d704679d343e55615551f19e9b2e18d68518b.tar.xz |
iommu/dma: Pass address limit rather than size to iommu_setup_dma_ops()
Passing a 64-bit address width to iommu_setup_dma_ops() is valid on
virtual platforms, but isn't currently possible. The overflow check in
iommu_dma_init_domain() prevents this even when @dma_base isn't 0. Pass
a limit address instead of a size, so callers don't have to fake a size
to work around the check.
The base and limit parameters are being phased out, because:
* they are redundant for x86 callers. dma-iommu already reserves the
first page, and the upper limit is already in domain->geometry.
* they can now be obtained from dev->dma_range_map on Arm.
But removing them on Arm isn't completely straightforward so is left for
future work. As an intermediate step, simplify the x86 callers by
passing dummy limits.
Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
Link: https://lore.kernel.org/r/20210618152059.1194210-5-jean-philippe@linaro.org
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/acpi/arm64/iort.c')
0 files changed, 0 insertions, 0 deletions