On Mon, Feb 14, 2011 at 04:15:10PM -0800, Kevin Hilman wrote: > Hema HK <[email protected]> writes: > > > Using omap_device_build API instead of platform_device_register for > > OMAP2430,OMAP34xx and OMAP4430 musb device registration. > > The device specific resources defined in centralized > > database will be used. > > Except for AM35x. > > NACK, for same reasons as previous version of this patch.
Does it really make sense to hold on omap2plus HWMOD conversion because of AM35x ? I mean, I understand it would be better to get all fixed up, but loose another merge window for that ? Can we get omap2plus in and AM35x on the next merge window ? At least omap2plus would have been converted to hwmod and would be using pm_runtime as we want. -- balbi -- 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
