greybus: timesync: Ensure parallel synchronous calls succeed

The guard for initiating a new synchronization operation should allow for
that resync to happen in every single state except for INVALID. This patch
fixes by ensuring the guard does just that. With local testing it was
possible to break a sync to a Module. This hasn't been observed in a buglog
but should be fixed anyway.

Signed-off-by: Bryan O'Donoghue <[e-mail]>
Acked-by: David Lin <[e-mail]>
Signed-off-by: Greg Kroah-Hartman <[e-mail]>

drivers/staging/greybus/timesync.c

···
 		return -EINVAL;
 
 	mutex_lock(&timesync_svc->mutex);
-	if (timesync_svc->state ==  GB_TIMESYNC_STATE_INACTIVE ||
-	    timesync_svc->state == GB_TIMESYNC_STATE_ACTIVE) {
+	if (timesync_svc->state !=  GB_TIMESYNC_STATE_INVALID) {
 		gb_timesync_set_state_atomic(timesync_svc, state);
 	} else {
 		ret = -ENODEV;