On Tue, Dec 14, 2010 at 3:07 PM, Fernando Guzman Lugo <[email protected]> wrote: > From: Guzman Lugo, Fernando <[email protected]> > > Some IOMMUs cannot use the whole 0x0 - 0xFFFFFFFF rage. > With this new API the valid range can be set. > > Signed-off-by: Fernando Guzman Lugo <[email protected]> > Acked-by: Hiroshi DOYU <[email protected]>
I still don't see where this API is being used. Also, the point of using platform data was to add it to omap3_devices in omap-iommu.c, see[1]. I thought the platform data start/end would move to struct iommu, and iommu_set_da_range would change the start/end on struct iommu, but that would only be necessary if the platform data doesn't match that. If there's no sensible platform data default, then there's no point in using platform data, as the platform is not the limiting factor, but the DSP SW. [1] http://article.gmane.org/gmane.linux.kernel/1051268 -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
