[PATCH v6 8/8] arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops
will.deacon at arm.com
Wed Jan 14 02:46:10 PST 2015
On Wed, Jan 14, 2015 at 09:00:24AM +0000, Alexandre Courbot wrote:
> On 12/02/2014 01:57 AM, Will Deacon wrote:
> > This patch plumbs the existing ARM IOMMU DMA infrastructure (which isn't
> > actually called outside of a few drivers) into arch_setup_dma_ops, so
> > that we can use IOMMUs for DMA transfers in a more generic fashion.
> > Since this significantly complicates the arch_setup_dma_ops function,
> > it is moved out of line into dma-mapping.c. If CONFIG_ARM_DMA_USE_IOMMU
> > is not set, the iommu parameter is ignored and the normal ops are used
> > instead.
> A series for IOMMU support with Tegra/Nouveau ceased to work after this
Which series? This code shouldn't even be executed unless you start using
of_xlate and the generic bindings.
> The Tegra IOMMU is not registered by the time the DT is parsed,
> and thus all devices end up without the proper DMA ops set up because
> the phandle to the IOMMU cannot be resolved.
You might want to look at the patches posted for the exynos, renesas and ARM
SMMUs for some hints in how to use the new API.
> Subsequently calling arm_iommu_create_mapping() and
> arm_iommu_attach_device() from the driver (as I used to do until 3.18)
> does not help since the call to set_dma_ops() has been moved out of
> arm_iommu_attach_device(). Therefore there seems to be no way for a device
> to gets its correct DMA ops unless the IOMMU is ready by the time the DT
> is parsed.
> Also potentially affected by this are the Rockchip DRM and OMAP3 ISP
> drivers, which follow the same pattern.
I don't understand why any code currently in mainline should be affected.
Please can you elaborate on the failure case?
> This raises the following questions:
> 1) Why are arm_iommu_create_mapping() and arm_iommu_attach_device()
> still public since they cannot set the DMA ops and thus seem to be
> useless outside of arch_setup_dma_ops()?
It has callers outside of the file. I'd like to make it static, but that
means doing some non-trivial porting of all the callers, which I'm also
unable to test.
> 2) Say you want to use the IOMMU API in your driver, and have an iommu
> property in your device's DT node. If by chance your IOMMU is registered
> early, you will already have a mapping automatically created even before
> your probe function is called. Can this be avoided? Is it even safe?
Currently, I think you have to either teardown the ops manually or return
an error from of_xlate. Thierry was also looking at this sort of thing,
so it might be worth talking to him.
More information about the linux-arm-kernel