Hi Miroslav, On Wed, 1 Jun 2022 at 16:27, Miroslav Lichvar <[email protected]> wrote:
> On Wed, Jun 01, 2022 at 04:08:23PM +0530, Devasish Dey wrote: > > As of now the *"tsproc_update_offset" * looks for a valid *t3 * and > > *filtered_delay_valid > > *to be True to calculate the offset. > > It doesn't check t3 in the default (filter) mode. The initial_delay > option relies on that. The other tsproc modes cannot be used when > delay is not measured at all. > Using "*initial_delay" *with non-zero values we can induce fixed pre-calculated delay. This is good when the user is aware or has the mechanism to calculate the path delay. This mechanism works when we have non-zero delay. NO_DELAY mechanism address when user or system does not have any delay measurement mechanism. The Newly introduced options for ts_proc gives users clear indication that delay measurement mechanism is not going to be used in this mode of operation. Currently we do not see any available option to work with no_delay mechanism. If we need to use the same option as suggested we need to update the existing behavior. Thanks, Devasish Dey SyncMonk Technologies
_______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
