aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorBryan O'Donoghue <[email protected]>2016-06-16 13:42:15 +0100
committerGreg Kroah-Hartman <[email protected]>2016-06-16 09:07:41 -0700
commit0cc3bc6930d02ff5083b7b7bc18ca53299bb383a (patch)
tree9266994b6945584f484c6f427b3837d4d8de856b /tools/perf/scripts/python
parentc9e8f893eeef4f0e2d10333aed2d175e50a56dab (diff)
greybus: timesync: Fix transitions to the INACTIVE state
Analysing a backtrace associated with the current EHCI runtime suspend code has highlighted several places where its perfectly valid to make a transition to GB_TIMESYNC_STATE_INACTIVE when not already in the GB_TIMESYNC_STATE_INIT state, for example failure to issue a TimeSync enable command to the SVC can and should legitimately call gb_timesync_teardown() - at this point the state will be GB_TIMESYNC_STATE_WAIT_SVC and it's legitimate and desirable to transition to the INACTIVE state in this case. This patch fixes by removing the restrictive and incorrect restriction on the transition to INACTIVE only being valid when state == GB_TIMESYNC_STATE_INIT. Signed-off-by: Bryan O'Donoghue <[email protected]> Reviewed-by: Vaibhav Hiremath <[email protected]> Tested-by: Vaibhav Hiremath <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions