tsproc: allow zero remote timestamps in delay update
When remote timestamps from P2P delay measurement are not known (the remote processing time is saved in the correction field), they are set to zero. Fix tsproc to not require non-zero t1 and t4. Signed-off-by: Miroslav Lichvar <mlichvar@redhat.com>master
parent
6eec5a0d48
commit
999c86f4a9
3
tsproc.c
3
tsproc.c
|
@ -144,8 +144,7 @@ int tsproc_update_delay(struct tsproc *tsp, tmv_t *delay)
|
||||||
{
|
{
|
||||||
tmv_t raw_delay;
|
tmv_t raw_delay;
|
||||||
|
|
||||||
if (tmv_is_zero(tsp->t1) || tmv_is_zero(tsp->t2) ||
|
if (tmv_is_zero(tsp->t2) || tmv_is_zero(tsp->t3))
|
||||||
tmv_is_zero(tsp->t3) || tmv_is_zero(tsp->t4))
|
|
||||||
return -1;
|
return -1;
|
||||||
|
|
||||||
raw_delay = get_raw_delay(tsp);
|
raw_delay = get_raw_delay(tsp);
|
||||||
|
|
Loading…
Reference in New Issue