diff options
author | Dave Gerlach <d-gerlach@ti.com> | 2016-07-12 12:50:33 -0500 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2016-07-22 23:10:15 -0700 |
commit | 428929c79cc3de7f9fefd2184da6ed625676ad9e (patch) | |
tree | 5378f627537496744cf3d67e010b8abe27bc2ceb /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | ddb0d99d53fea77c568d17265b8bca6e64f2975b (diff) |
ARM: OMAP4+: Have _omap4_wait_target_* check for valid clkctrl_offs
Previously the low-level CM call internal to the
_omap4_wait_target_ready/disable calls was responsible for checking for
a valid clkctrl_offs. Now we must also consider the value of the
prcm.omap4.flags because if HWMOD_OMAP4_ZERO_CLKCTRL_OFFSET is set in
the flags then clkctrl_offs of 0 is valid.
Let's add this check into the _omap4_wait_target_ready/disable where we
have access to both the clkctrl_offs and the flags values and simply
return 0 without calling the low level CM call at all, which would have
returned 0 anyway if the clktrl_offs was zero.
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
Acked-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions