On Tue, Dec 14, 2010 at 8:59 PM, Guzman Lugo, Fernando <[email protected]> wrote: > On Tue, Dec 14, 2010 at 9:08 AM, Felipe Contreras > <[email protected]> wrote: >> 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. > > you can find it here: > > http://marc.info/?l=linux-kernel&m=128805403014740&w=2
Oh, ok, thanks. somehow I missed it. >> 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. Yeah, if you are not going to add it in the platform data (mach-omap2/omap-iommu.c), then it doesn't make sense to use platform data for that. Cheers. -- 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
