RFC How to pass IOMMU map attr via DMA API?
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/3] How to pass IOMMU map attr via DMA API?
Quoted 1 line · Hiroshi Doyu
Hi Will,
Hi Hiroshi,
Quoted 7 lines
Will Deacon <[email protected]> wrote @ Thu, 20 Jun 2013 11:31:52 +0200:
Quoted 5 lines
Quoted 4 lines
Hiroshi Doyu (3):
common: DMA-mapping: addDMA_ATTR_READ_ONLYattribute
ARM: dma-mapping: Pass DMA attrs as IOMMU prot iommu/tegra: smmu: Support read-only mapping
Quoted 5 lines
Quoted 2 lines
These patches don't seem to have made it to the linux-arm-kernel list (either in my inbox or the list archive). Could you try and resend them please?
I'm sorry but linux-arm-kernel list someitmes requires me moderators approval. I don't know why. I'll find a way to work around.
Strange. It would definitely be good to get that fixed!
Quoted 6 lines
Here are links for the original post:
http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005860.html
http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005861.html
http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005862.html
http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005863.html
Thanks, but I can't reply inline to those :)
Quoted 10 lines
Quoted 3 lines
Also: how do they interact with my patch here?:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/175124.html
This conversion looks reasonable enough, but some platform may need more attrs to pass IOMMU like OMAP.
#define IOMMU_FLAG (IOVMF_ENDIAN_LITTLE | IOVMF_ELSZ_8)How can we deal with those cases?
Well, if we have weird and wonderful flags like this, which are IOMMU-specific, then I'd suggest short-circuiting the flags altogether and putting them inside somewhere like dev_archdata.iommu.
Will