Hi, On Fri, 15 Jul 2011, Felipe Balbi wrote: > How about something like: > > /* > * Program target state of all power domains to ON. This is to prevent > * power domains from hitting low power states during boot up and > * potentially causing accesses to the address space of an IP while it > * is disabled. > * > * PM late init code will make sure of disabling all unused IPs later. > */ > > not sure if it's a lot better though. It's not directly related to accesses to the IP block's address space. The problem happens when the driver (or the hwmod code) for a particular device causes the last clock in a clockdomain to be disabled. This allows the clockdomain to go INACTIVE. At that point, if all of the clockdomains in the powerdomain are INACTIVE, the powerdomain itself will switch to its "next power state". If the bootloader had programmed the next power state to be OFF, for example, then all devices in that powerdomain will lose context. If this happens before the PM code initializes, or if the PM code is not compiled in, then this will cause some strange behavior or crashes, since the kernel won't be expecting devices to lose their context at that point. - 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
