diff options
author | Amit Cohen <[email protected]> | 2022-07-24 11:03:24 +0300 |
---|---|---|
committer | David S. Miller <[email protected]> | 2022-07-25 13:58:55 +0100 |
commit | 22d950b79ea70b69386b3b131051fbe22f065bdf (patch) | |
tree | 755c91f7d398aa050d06c4618435a166adc5d454 /tools/perf/scripts/python/event_analyzing_sample.py | |
parent | 33a9583f9a02d2d8d820f41eb1ed83e06a016bba (diff) |
mlxsw: spectrum_ptp: Initialize the clock to zero as part of initialization
As lately recommended in the mailing list[1], set the clock to zero time as
part of initialization.
The idea is that when the clock reads 'Jan 1, 1970', then it is clearly
wrong and user will not mistakenly think that the clock is set correctly.
If as part of initialization, the driver sets the clock, user might see
correct date and time (maybe with a small shift) and assume that there
is no need to sync the clock.
Fix the existing code of Spectrum-1 to set the 'timecounter' to zero.
[1]:
https://lore.kernel.org/netdev/[email protected]/
Signed-off-by: Amit Cohen <[email protected]>
Reviewed-by: Petr Machata <[email protected]>
Signed-off-by: Ido Schimmel <[email protected]>
Acked-by: Richard Cochran <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions