wr-servo: fix a wrong state change (with no effect)

After changing the nsec counter, the next state should be SYNC_PHASE, not SYNC_NSEC. This was a mistake when making order in the wr-servo file, initially, but has no effect as we move to a later step anyways if offset_hw.nanoseconds is already 0. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

wr-servo: fix a wrong state change (with no effect)
After changing the nsec counter, the next state should be SYNC_PHASE, not SYNC_NSEC. This was a mistake when making order in the wr-servo file, initially, but has no effect as we move to a later step anyways if offset_hw.nanoseconds is already 0. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
c92b4290 · Alessandro Rubini · 3165143f · c92b4290
Commit c92b4290 authored Jun 09, 2015 by Alessandro Rubini
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

wr-servo.c proto-ext-whiterabbit/wr-servo.c +1 -1

No files found.
--- a/proto-ext-whiterabbit/wr-servo.c
+++ b/proto-ext-whiterabbit/wr-servo.c
@@ -343,7 +343,7 @@ int wr_servo_update(struct pp_instance *ppi)
 	case WR_SYNC_NSEC:
 		wrp->ops->adjust_counters(0, ts_offset_hw.nanoseconds);
-		s->next_state = WR_SYNC_NSEC;
+		s->next_state = WR_SYNC_PHASE;
 		s->state = WR_WAIT_SYNC_IDLE;
 		s->last_tics = tics;
 		break;