Question about arm smmu
Hi Will,
I am trying to enable SMMU(mmu500) on an platform.
My platform support only 32 SIDs, but it have more than 100 masters. So I need to let different masters share one SID. I read current arm-smmu.c, but it needs each master has unique SID. Do you have some suggestions about how to let different masters sharing one SID?
On my platform, SID can be dynamically programmed. So I can program DMA0 and DMA1 using one SID, saying 0x5. But I do not have a good idea how to support this use case in arm-smmu.c driver.
Thanks,
Peng.
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line · Peng Fan
Hi Will,
Hello,
Quoted 6 lines
I am trying to enable SMMU(mmu500) on an platform.
My platform support only 32 SIDs, but it have more than 100 masters. So I need to let different masters share one SID. I read currentarm-smmu.c, but it needs each master has unique SID. Do you have some suggestions about how to let different masters sharing one SID?
We can achieve that using iommu_groups, but then we need a way to describe those groups in the device-tree, as opposed to putting each device into its own group like we do at present. Robin (CC'd) had some work-in-progress for this, iirc.
Quoted 3 lines
On my platform, SID can be dynamically programmed. So I can program DMA0 and DMA1 using one SID, saying
0x5. But I do not have a good idea how to support this use case inarm-smmu.cdriver.
I think we've have the firmware allocating the SIDs, then describing the grouping to Linux in the device-tree.
Will
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Will Deacon
Quoted 1 line · Peng Fan
Hi Will,
Hello,
Quoted 2 lines
I am trying to enable SMMU(mmu500) on an platform.
My platform support only 32 SIDs, but it have more than 100 masters.
Do you mean the MMU-500 configuration really only has 5 bits of stream ID wired up (which seems a bit unlikely, especially given that in such a configuration you should gain extra bits from the prepended TBU number), or that you have a sufficient number of stream ID bits but only have 32 stream matching groups?
Quoted 9 lines
Quoted 4 lines
So I need to let different masters share one SID. I read current
arm-smmu.c, but it needs each master has unique SID. Do you have some suggestions about how to let different masters sharing one SID?We can achieve that using
iommu_groups, but then we need a way to describe those groups in the device-tree, as opposed to putting each device into its own group like we do at present. Robin (CC'd) had some work-in-progress for this, iirc.
I spent enough time on it that I reached the point of thinking there's no feasible DT binding that is sufficiently hardware-agnostic, and isn't just trying to paint a Linux implementation detail as hardware description - the master IDs are already there, so it might as well be up to the thing parsing them to work out what, if anything, it wants to do with duplicates.
What I have now is a simple little lookup table solution inside the SMMUv2 driver to automatically track groups by stream ID for platform devices. I've not yet tried pulling in Joerg's generic group series, but I think it's going to slot together really neatly with that, so I might try breaking it out of the big stream ID probing rework I'm currently half-way through.
Quoted 6 lines
Quoted 3 lines
On my platform, SID can be dynamically programmed. So I can program DMA0 and DMA1 using one SID, saying
0x5. But I do not have a good idea how to support this use case inarm-smmu.cdriver.I think we've have the firmware allocating the SIDs, then describing the grouping to Linux in the device-tree.
Yeah, regardless of how we handle groups we need the SIDs to be in the DT and not change at runtime, so the programming is going to have to be done before the kernel even runs.
Robin.
Quoted 3 lines
Will
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi Robin, Will,
Quoted 6 lines · Robin Murphy
Quoted 5 lines · Will Deacon
Quoted 1 line · Peng Fan
Hi Will,
Hello,
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
I am trying to enable SMMU(mmu500) on an platform.
My platform support only 32 SIDs, but it have more than 100 masters.Do you mean the MMU-500 configuration really only has 5 bits of stream ID wired up (which seems a bit unlikely, especially given that in such a configuration you should gain extra bits from the prepended TBU number), or that you have a sufficient number of stream ID bits but only have 32 stream matching groups?
There are 32 Stream matching registers, 32 Contexts. The stream id width seems to be 10 bits.
Quoted 18 lines
Quoted 10 lines
Quoted 5 lines
So I need to let different masters share one SID. I read current
arm-smmu.c, but it needs each master has unique SID. Do you have some suggestions about how to let different masters sharing one SID?We can achieve that using
iommu_groups, but then we need a way to describe those groups in the device-tree, as opposed to putting each device into its own group like we do at present. Robin (CC'd) had some work-in-progress for this, iirc.I spent enough time on it that I reached the point of thinking there's no feasible DT binding that is sufficiently hardware-agnostic, and isn't just trying to paint a Linux implementation detail as hardware description - the master IDs are already there, so it might as well be up to the thing parsing them to work out what, if anything, it wants to do with duplicates.
Quoted 6 lines
What I have now is a simple little lookup table solution inside the SMMUv2 driver to automatically track groups by stream ID for platform devices. I've not yet tried pulling in Joerg's generic group series, but I think it's going to slot together really neatly with that, so I might try breaking it out of the big stream ID probing rework I'm currently half-way through.
Would you mind share me you code? I'd like to try on my platform.
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
On my platform, SID can be dynamically programmed. So I can program DMA0 and DMA1 using one SID, saying
0x5. But I do not have a good idea how to support this use case inarm-smmu.cdriver.I think we've have the firmware allocating the SIDs, then describing the grouping to Linux in the device-tree.
Yeah, regardless of how we handle groups we need the SIDs to be in the DT and not change at runtime, so the programming is going to have to be done before the kernel even runs.
Yeah. I programmed the SID in bootloader. When kernel runs, the SID will not change.
Thanks,
Peng.
Quoted 7 lines
Robin.
Quoted 3 lines
Will