Benoit Rat authored 5 years ago and Adam Wujek committed 5 years ago

Use gmtime instead of localtime (TAI should never used localtime)
Add verbose option to also display linux time

Benoit Rat authored 5 years ago and Adam Wujek committed 5 years ago

The output will be something like:

wr_date -v diff
TAI(HW)-UTC(SW): +36.602286
UTC(HW)-UTC(SW): -0.397714

Conflicts:
	userspace/tools/wr_date.c

Benoit Rat authored 5 years ago and Adam Wujek committed 5 years ago

In the previous version `wr_date get` would override kernel TAI time
(using local file) and this could cause some problems in case leap
second from /etc/leap-seconds.list was not the same than from PTP/WR
protocol.

Benoit Rat authored 5 years ago and Jean-Claude BAU committed 5 years ago

We have 37s of leap second but we were showing without usec the
following which could be seen as a wrong leap second offset.

WR time (TAI):     2019-03-15 05:40:48.006697
Switch time (UTC): 2019-03-15 05:40:10.975551

localtime has also been replaced by gmtime (TAI should never be
converted using localtime in case TZ variable is set)

Conflicts:
	userspace/tools/wr_mon.c

- Display in wr_mon the current timing mode and the PLL locking state
- Import PPsi changes related to this issue

- Increase up to 18 the number of SFPs and Fibers
- Add config parameter: CONFIG_N_SFP_ENTRIES (Number of SFP entries in
the DB)
- Add config parameter: CONFIG_N_FIBER_ENTRIES (Number of FIBER entries
in the DB)
- This 2 new parameters are used by HAL to parse the DB
- Use the TX SFP wave length as a key to retreive the SFP entry in the
DB

- New delayAsymCoeff and delayAsymmetry calculation
- Restart WR calibration when the PLL unlocks
- [BUG: 2] ptpdump wrongly shows Announce Msg parameters

The main change comes from the protocol detection state.

The logic used to control WR switch leds is removed from HAL and
imported into PPSi. It prevents HAL from reading PPSi shared memory.

Include again the commit:
[BUG: 1575] userspace: add "monitor" port parameter to HAL and snmp
74e16153



This time on top of HA

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

baujc authored 5 years ago and Adam Wujek committed 5 years ago

Now, the control of the timing mode and the PPS generation is two
separate things that can be controlled independently by PPSi.

baujc authored 6 years ago and Adam Wujek committed 5 years ago

The previous version expected that the "source" and "config" keys were
at the beginning of the line but it is not mandatory in the Kconfig
file.

baujc authored 6 years ago and Adam Wujek committed 5 years ago

- Better information display
- Change easily the timing mode

baujc authored 6 years ago and Adam Wujek committed 5 years ago

This feature is very useful when we reboot very often the switch
especially during the development process.

baujc authored 6 years ago and Adam Wujek committed 5 years ago

- Adapt the code to PPSi Kconfig changes
- Display the port link state
- Display the protocol used (Ext or PTP)

baujc authored 6 years ago and Adam Wujek committed 5 years ago

The previous fix didn't solved completelly this issue: Negative nano WR
time adjustement generate a big jump of the monotonic clock used in
PPSI.
The current fix solves this issue.

baujc authored 6 years ago and Adam Wujek committed 5 years ago

This library is used by wr_mon and wrs_dump_shmem to avoid duplication
of code.

baujc authored 6 years ago and Adam Wujek committed 5 years ago

- Add new option "stat" to display statistic about the evolution between
WR and Unix time
- When we set the WR time with the current UNIX time, the driver
wr_clocksource must be removed first and then reinstalled when the time
is set. If it is not done, the WR and Unix time are not well
synchronized.
- When the WR time is set, the sec and ns and set in one call. We don't
need to call twice the wr_date tool.