Introduced hwmod support for OMAP3 (iva, isp) and OMAP4 (ipu, dsp), along with the corresponding runtime PM routines to deassert reset lines, enable/disable clocks and configure sysc registers.
v4: - Rebased to 3.2-rc5 LO. - Added missing clkdm field for OMAP4 hwmod data. - Moved pm runtime enable/disable to probe/remove functions as suggested by MyungJoo Ham. - Removed HWMOD_INIT_NO_RESET as it is not needed and because of Kevin Hilman's comments, the failure I was seeing without HWMOD_INIT_NO_RESET might have been related to local changes as it couldn't be reproduced anymore. - Removed iommu latency as it is the same as the default omap latency. - Tested on OMAP3 (zoom3 + tidspbridge) and OMAP4 (Panda + rpmsg). v3: - Rebased to 3.1-rc10 lo rebuilt, added structure terminators, and removed .omap_chip field. v2: - Added oh reset info to assert/deassert mmu reset lines. - Addressed previous comments on v1 http://www.spinics.net/lists/arm-kernel/msg103271.html Due to compatibility an ifdef needs to be propagated (previously on iommu resource info) to hwmod data in OMAP3, so users of iommu and tidspbridge can avoid issues of two modules managing mmu data/irqs/resets; this until tidspbridge can be safely migrated to iommu framework. Omar Ramirez Luna (4): OMAP3: hwmod data: add mmu data for iva and isp OMAP4: hwmod data: add mmu hwmod for ipu and dsp OMAP3/4: iommu: migrate to hwmod framework OMAP3/4: iommu: adapt to runtime pm arch/arm/mach-omap2/iommu2.c | 36 ------- arch/arm/mach-omap2/omap-iommu.c | 156 +++++----------------------- arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 135 ++++++++++++++++++++++++ arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 154 +++++++++++++++++++++++++-- arch/arm/plat-omap/include/plat/iommu.h | 17 +++- arch/arm/plat-omap/include/plat/iommu2.h | 2 - drivers/iommu/omap-iommu.c | 47 +++----- 7 files changed, 334 insertions(+), 213 deletions(-) -- 220.127.116.11 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html