[PATCHv4 3/7] iommu/tegra: smmu: Register IOMMU'able devices dynamically
Stephen Warren
swarren at wwwdotorg.org
Tue Nov 12 18:58:56 EST 2013
On 11/11/2013 01:31 AM, Hiroshi Doyu wrote:
> platform_devices are registered as IOMMU'able dynamically via
> add_device() and remove_device().
>
> Tegra SMMU can have multiple address spaces(AS). IOMMU'able devices
> can belong to one of them. Multiple IOVA maps are created at boot-up,
> which can be attached to devices later. We reserve 2 of them for
> static assignment, AS[0] for system default, AS[1] for AHB clusters as
> protected domain from others, where there are many traditional
> pheripheral devices like USB, SD/MMC. They should be isolated from
> some smart devices like host1x for system robustness. Even if smart
> devices behaves wrongly, the traditional devices(SD/MMC, USB) wouldn't
> be affected, and the system could continue most likely. DMA API(ARM)
> needs ARM_DMA_USE_IOMMU to be enabled.
> diff --git a/drivers/iommu/tegra-smmu.c b/drivers/iommu/tegra-smmu.c
> +static int smmu_iommu_add_device(struct device *dev)
> +{
> + int err = -EPROBE_DEFER;
> + u64 swgroups;
> + struct dma_iommu_mapping *map = NULL;
> +
> + swgroups = smmu_of_get_memory_client(dev);
BTW, that function doesn't seem to exist in this patch series nor
next-20131107. This call is removed in patch 5/7, but this does make the
series non-bisectable.
More information about the linux-arm-kernel
mailing list