Hi Philipp, On Monday 09 September 2013 02:36 PM, Philipp Zabel wrote: > So if I understand correctly, the only problem is that on OMAP the clock > needs to be enabled to deassert the reset, but as long as the clock > domain is in hardware supervised mode, it won't be enabled? Yes, enabling clock with reset deassertion might not reset the module if the clock domain is in hardware supervised mode. > Would it be possible to create an internal API to switch the clock > domain to software supervised mode, which can be used both by the code > behind pm_runtime_get_sync and reset_control_deassert? I will see if that is acceptable. Another option that would have to be explored is invoking device_reset() (taking care of clear, deassert & status checking as you suggested) midway through pm_run_time_get_sync(), when the clockdomain is in software supervised mode with reset driver taking care of any particular sequence in the case of multiple reset signals, instead of the IP driver requiring to take care of it. Regards Afzal -- 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
