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>

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

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.

- Better information display
- Change easily the timing mode

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

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

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.

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

- 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.

The WR time adjustment was not taken into account in the driver. The
side effect was a big jump sometime of the monotonic clock used in PPSI
for the calculation of the timeouts. The side effect was that many
timeouts were firing too early.
The driver registration take now into account the adjustment and also
the calculation of the offset in the read() call.

The parameter was already present in pps.conf but not yet managed by
kconfig and the ppsi.conf generator

This new parameter is used to control the configurable parameter
L1SyncOptParamsPortDS.timestampsCorrectedTx when
L1SyncBasicPortDS.optParamsEnabled is set to true.

The profile is included in the port instance name. With the new profile
"custom", the port instance name become too big. So only the two first
letters of the profile are now included in the name.

- Timeout management
- Configuration enhancement
- Erbest/ebast calculation
Note: The pp_instance structure has changed so all related programs
depending on pp_instance structure must be rebuild.

        - Add new config parameters (l1SyncRxCoherencyIsRequired,...)
        - Add new profile: CUSTOM. It will be mostly used for testing
        - Fix issue on state name: "pre_master" instead of "pre-master"

Change the format of diplayed data in order to facilitate the extraction
of data with grep like command
Signed-off-by: baujc <jean-claude.bau@cern.ch>
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

When the WR profile is used ingressLatency and egressLacenty a set to 0
by default. This has to be done to avoid to use twice this values in the
delay calculation (ppsi + hal)

As the bitslide is already taken into account in PPSI for all protocol
extensions as the semiStaticLatency, it is no longer needed to use it in
the calculation of delta_rx_phy.