On Tue, Dec 14, 2010 at 9:08 AM, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote: > On Tue, Dec 14, 2010 at 3:07 PM, Fernando Guzman Lugo > <fernando.lugo@xxxxxx> wrote: >> From: Guzman Lugo, Fernando <x0095840@xxxxxx> >> >> 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 <x0095840@xxxxxx> >> Acked-by: Hiroshi DOYU <Hiroshi.DOYU@xxxxxxxxx> > > I still don't see where this API is being used. you can find it here: http://marc.info/?l=linux-kernel&m=128805403014740&w=2 I will add it to the iommu migration set once all the dependencies are merged. > > 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. it is not clear for me. do you mean having default start/end in platform data then when iommu_get is call pass them to start/end in struct iommu and the new api change start/end in struct iommu? Please let me know if that is correct. Regards, Fernando. > > 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
