proto-standard/state-slave: don't change minDelayReqInterval timeout

The intention of the removed code was to speed up the receive of the first delay_resp frame by changing the minDelayReqInterval timeout, that triggers the issue of delay_req. The timeout was reduced to half, but later never restored to the intentional value. Signed-off-by: Adam Wujek <dev_public@wujek.eu>

proto-standard/state-slave: don't change minDelayReqInterval timeout
The intention of the removed code was to speed up the receive of the first delay_resp frame by changing the minDelayReqInterval timeout, that triggers the issue of delay_req. The timeout was reduced to half, but later never restored to the intentional value. Signed-off-by: Adam Wujek <dev_public@wujek.eu>
2493797e · Adam Wujek · b70b7926 · 2493797e
Commit 2493797e authored Sep 19, 2023 by Adam Wujek
Hide whitespace changes
Inline Side-by-side

Showing with 0 additions and 7 deletions

state-slave.c proto-standard/state-slave.c +0 -7

No files found.
--- a/proto-standard/state-slave.c
+++ b/proto-standard/state-slave.c
@@ -44,13 +44,6 @@ static int slave_handle_sync(struct pp_instance *ppi, void *buf,
 		return 0;
 	}

-	if ( is_delayMechanismE2E(ppi) &&  ppi->t1.scaled_nsecs==0 && ppi->t1.secs==0 ) {
-		/* First time we receive the SYNC message in uncalib/slave state
-		 * We set the REQUEST time-out to the minDelayReqInterval/2 value (500ms)
-		 * in order to provide quickly a DelayReq message
-		 */
-		pp_timeout_set(ppi, PP_TO_REQUEST, (1000*(1<<PP_MIN_MIN_DELAY_REQ_INTERVAL))/2);
-	}
 	/* t2 may be overriden by follow-up, save it immediately */
 	ppi->t2 = ppi->last_rcv_time;
 	msg_unpack_sync(buf, &sync);