Hi Tony, On Wed, Nov 14, 2012 at 6:51 PM, Tony Lindgren <t...@atomide.com> wrote: > * Jean Pihet <jean.pi...@newoldbits.com> [121114 08:43]: >> >> The patch should change the name of the hwmod entry as well, can you >> fold this change in the current patch? > > This was caused by the merge of omap-for-v3.8/pm into omap-for-v3.8/clock. > I noticed a smilar issue for omap3, but missed at least this one. > > Jean, can you please check omap-for-v3.8/clock for the smartreflex > clock names in case there are more issues like this remaining? The hwmod clock names are OK for 3xxx, 36xx, 33xx and 44xx. The hwmod names are OK excepted for 33xx where they respectively should be "smartreflex_mpu_iva" and ""smartreflex_core".
This issue is caused by 99e7938d "ARM: OMAP3: clock: Add 3xxx data using common struct clk" in omap-for-v3.8/clock. > Regards, > > Tony Regards, Jean -- 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
