Currently "tidspbridge" driver uses its own mmu implementation and will migrate to use this "omap iommu" eventually. This config is provided to make this migration happen smoothly.
Signed-off-by: Hiroshi DOYU <[email protected]> --- arch/arm/mach-omap2/omap3-iommu.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-omap2/omap3-iommu.c b/arch/arm/mach-omap2/omap3-iommu.c index 91ee38a..194189c 100644 --- a/arch/arm/mach-omap2/omap3-iommu.c +++ b/arch/arm/mach-omap2/omap3-iommu.c @@ -36,11 +36,13 @@ static const struct iommu_platform_data omap3_iommu_pdata[] __initconst = { .nr_tlb_entries = 8, .clk_name = "cam_ick", }, +#if defined(CONFIG_MPU_BRIDGE_IOMMU) { .name = "iva2", .nr_tlb_entries = 32, .clk_name = "iva2_ck", }, +#endif }; #define NR_IOMMU_DEVICES ARRAY_SIZE(omap3_iommu_pdata) -- 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
