On Sat, 9 Jun 2012, Hiremath, Vaibhav wrote: > On Sat, Jun 09, 2012 at 04:40:03, Paul Walmsley wrote: > > On Fri, 8 Jun 2012, Hiremath, Vaibhav wrote: > > > > > So the approach I had taken is, I had implemented almost similar > > > function specific to cpsw and introduced flag called > > > HWMOD_SWSUP_RESET_BEFORE_IDLE. > > > > Why "SWSUP" ? > > Since it was SW initiated reset assertion so I added this prefix. Maybe just use HWMOD_RESET_BEFORE_IDLE. The code use SWSUP to mean "software-supervised" in the context of idle. > > > Now the question here would be, should we consider this IP bug or > > > integration bug? If it is integration bug, then isn't this device issue? > > > > I don't know if it's a bug in either place, but it sounds like something > > that needs to be handled in the _am335x_disable_module() code in > > mach-omap2/omap_hwmod.c. > > Yes, certainly it should be part of _am335x_disable_module(). Great. Care to send a patch? - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
