Felipe Balbi <[email protected]> writes: > current omap_device PM implementation defines > omap-specific *_noirq methods but uses the > generic versions for all other PM methods. > > As it turns out, if a device decides to implement > non-runtime PM callbacks, we might fall into a > situation where the hwmod is still idled which > will generate an abort exception when we try > to access device's address space while clocks > are still gated.
Please explain in more detail how this could happen. Kevin > In order to solve that, we implement all other > methods taking into account that devices might > not implement those, in which case we return > early. > > Signed-off-by: Felipe Balbi <[email protected]> -- 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
