On 26.11.2012 09:33, Arto Merilainen wrote: > AFAIK dma-mapping API is not smart enough to determine whether a > given buffer is already mapped to some address space. It just maps > and potentially creates duplicates (please correct me if I am wrong). > Therefore, if the "generic case solution" is applied to our "specific > case", there will always be duplicates and I do not think that is a > good practice. I also considered doing a smart optimisation here, but > dma-mapping API did not seem to support querying of the address space > of a certain device. This coupled with the facts that CMA helper calls dma mapping API, and that CMA helper doesn't know if IOMMU is enabled or disabled for a particular device, we need to keep the prime support as tegradrm specific code for now. Terje -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
