"Ramirez Luna, Omar" <omar.rami...@ti.com> writes: > Hi, > > On Fri, Nov 4, 2011 at 6:23 PM, Kevin Hilman <khil...@ti.com> wrote: >>> + .flags = HWMOD_INIT_NO_RESET, >> >> Why is this needed? > ... >>> + .flags = HWMOD_INIT_NO_RESET, >> >> And this? > > I have this because the hwmod complains about a failure in hard reset, > even though the reset deassert does complete after the clock is > enabled. Later on, hwmod will warn again because of a wrong state when > enabling, I believe because of the failure on _setup but didn't dig > into it yet.
Please dig deeper into the reset failure. We don't merge HWMOD_INIT_NO_RESET changes without a very good reason (that is also well described in the changelog.) Thanks, Kevin -- 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
