On Thu, Mar 15, 2012 at 1:25 AM, Paul Walmsley <[email protected]> wrote: > Hola Omar,
Hola :) > On Wed, 14 Mar 2012, Ramirez Luna, Omar wrote: > >> If we reached here the reset lines will be asserted, and then the code >> below touches sysc registers on a module under reset. > > Do you know of any case where this would be a problem? Seems like it > would only affect IP blocks that have both hard reset lines and SYSCONFIG > registers, and as far as I know, we don't have any of those defined? MMU (not yet mainlined) has both, a reset line and a sysconfig. I have been holding the hwmod for some time, but now that rpmsg/remoteproc is going to mainline it could make use of it along with omap3isp, however now I need to define functions to handle the reset lines (although I was fine with hwmod handling it). AFAIKnew, hwmod handling the reset line was fine (IMHO), the only 2 things were: - For the drivers to somehow make use of shutdown/enable if they needed they hwmod under reset and out. - The annoying: hwmod XX failed to hardreset because of the wrong reset sequence but causing no functional issues. Regards, Omar -- 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
