On 1/31/23 15:15, Robin Murphy wrote:
On 31/01/2023 1:08 pm, Alexandre Bailon wrote:
Hi Robin
On 1/30/23 13:04, Robin Murphy wrote:
On 2023-01-30 10:27, Alexandre Bailon wrote:
Currently, the driver can allocate an unmanaged iommu domain.
But, this only works for SoC having multiple bank or multiple iova
region.
That is for good reason - there is only a single pagetable per bank,
so if there are multiple devices assigned to a single bank, they
cannot possibly be attached to different domains at the same time.
Hence why the banks are modelled as groups.
I understand.
I am trying to upstream a remoteproc driver but the remote processor is
behind the iommu.
remoteproc can manage the iommu but it requires an unmanaged domain.
I tried a couple of things but this cause code duplication,
implies many hacks and not always reliable.
Do you have any suggestion ?
If there are other active devices behind the same IOMMU, and the
remoteproc device cannot be isolated into its own bank using the
existing IOMMU driver logic, then the remoteproc driver cannot manage
the IOMMU directly, and must just use the regular DMA API. There's no
way around it; you can't have two different parts of the kernel both
thinking they have exclusive control of a single IOMMU address space at
the same time. Similarly, remoteproc also cannot take explicit control
of a multi-device group if it's not actually in control of the other
devices, since their drivers will not be expecting the DMA address space
to suddenly change underfoot - that's why iommu_attach_device() has the
check which you presumably ran into.
Unfortunately, we can't just use the regular DMA API.
Basically, the firmware use static addresses (and the remote core is
only supposed to access addresses between 0x60000000 and 0x70000000).
When we use DMA API, we get a random address that doesn't match what the
firmware would expect.
remoteproc use directly the iommu API to map physical address to the
static address expected by the firmware when DMA API can't be use.
Thanks,
Alexandre
