> Currently the iva2 code (tidspbridge) is not using iommu, therefore it
> can't be
> used as-is with the current omap iommu.
Bridge can use IOMMU module that Hiroshi has sent by calling below 2 lines of
code.
struct iommu *iva_iommu_ptr;
iva_iommu_ptr = iommu_get("iva2");
Thank you,
Best regards,
Hari
> -----Original Message-----
> From: [email protected] [mailto:linux-omap-
> [email protected]] On Behalf Of Felipe Contreras
> Sent: Thursday, May 07, 2009 3:11 PM
> To: [email protected]
> Cc: Hiroshi DOYU; Felipe Contreras; Tony Lindgren; Felipe Contreras
> Subject: [RFC/PATCH 0/3] omap3-iommu: cleanups and remote registration
>
> This patch series cleanups up a bit the opap3-iommu device registration
> and
> then allows registration from other parts of the code.
>
> Currently the iva2 code (tidspbridge) is not using iommu, therefore it
> can't be
> used as-is with the current omap iommu. By allowing devies to be
> registered
> externaly (either isp, or iva2) this problem goes away.
>
> Felipe Contreras (3):
> omap3-iommu: reorganize
> omap3-iommu: split init function into omap_iommu_add
> omap3-iommu: remote registration
>
> arch/arm/mach-omap2/omap3-iommu.c | 130 ++++++++++++++------------
> -----
> arch/arm/plat-omap/include/mach/iommu.h | 2 +
> 2 files changed, 62 insertions(+), 70 deletions(-)
>
> --
> 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
--
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
