Nishanth Menon wrote:
From: Aneesh V<ane...@ti.com>Make all hwmod data used for OMAP4430 available for the OMAP44XX class so that OMAP4460 can use them. We will modify the required 4460 hwmod in further patch(es). [n...@ti.com: just rebased to .39] Signed-off-by: Nishanth Menon<n...@ti.com> Signed-off-by: Aneesh V<ane...@ti.com> --- arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 164 ++++++++++++++-------------- 1 files changed, 82 insertions(+), 82 deletions(-) diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c index abc548a..2f51a5a 100644 --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c @@ -124,7 +124,7 @@ static struct omap_hwmod omap44xx_dmm_hwmod = { .slaves_cnt = ARRAY_SIZE(omap44xx_dmm_slaves), .mpu_irqs = omap44xx_dmm_irqs, .mpu_irqs_cnt = ARRAY_SIZE(omap44xx_dmm_irqs), - .omap_chip = OMAP_CHIP_INIT(CHIP_IS_OMAP4430), + .omap_chip = OMAP_CHIP_INIT(CHIP_IS_OMAP44XX),
I guess at the time that CHIP_IS_OMAP4430 was introduced it was totally unthinkable that another 44xx based chip would ever exist? -- 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
