On Mon, May 14, 2012 at 5:03 AM, Tero Kristo <t-kri...@ti.com> wrote:
[...]
> +/**
> * _enable - enable an omap_hwmod
> * @oh: struct omap_hwmod *
> *
> @@ -1599,6 +1629,8 @@ static int _enable(struct omap_hwmod *oh)
> _enable_clocks(oh);
> _enable_module(oh);
>
> + _omap4_update_context_lost(oh);
> +
> r = _wait_target_ready(oh);
> if (!r) {
> /*
Dumb q: Since we monitor the count around _enable, how do we ensure
that context loss counter is accurate
around OFF and idle transitions for domains that could have been
hwauto? it might be good to have limitations
in the $commit_message if it is not targeted to do so.
Regards,
Nishanth Menon
--
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
