The S1 treatment must be called only if the foreign master is
accepted/registered by the BMCA.

- In case of handshake failure due to the reception of an unexpected
message, execute the same procedure executed in case of time-out. The
behavior will be more coherent.
- better diagnostics

This version of ppsi, currently submodule of proposed_master of
wr-switch-sw, is not building because of INT_MAX, UINT_MAX and the like.

This includes <limits.h> in all files where this is needed.

Obviously, <limits.h> will be missing in wrpc-sw and bare builds, but
this version does not build for most architectures anyways (including
arch-unix).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Bug description : When a MASTER port is at a lower port number than a
SLAVE port, the SLAVE port is jumping all the time between UNCALIBRATED
and SLAVE state.

The 2 octets were displayed as as int16 so they can be swapped depending
of the architecture.

When the PPS generation is forced by configuration, the PPS was disabled
when an instance was leaving the UNCALIB/SLAVE states to another state.

- When a new GM has been detected by the BMCA, the SLAVE state must
transition to UNCALIBRATED. If the state is already set to UNCALIBRATED
, nothing must be done.

- All announce messages not received from erbest are not been taken into
account. erbest is the best qualified foreign master.
- Comments added

Introduction of an other way to calculate the best foreign master. It
has been changed to fix bugs found during ISPC20119 (IOL test). Tests
showed unstable behavior in the computation of foreign master
qualification in some specific circumstances (time window of 8s with
announce messages every 5s)

Issue detected by IOL test in ICALEPS2019
The selection of the ErBest was not taking account all the time of the
qualification.

- New mechanism for clock degradation (degrade clock class, clock
accuracy, clock variance, timeSource, ptpTimeScale, frequencyTraceable,
timeTraceable)
- timeSource can be configured now
- If clock accuracy, clock variance and timeSource are not set in
ppsi.conf, default values are used depending of the clock class.

Change clock accuracy from 0x21(100ns) to 0x20(25ns) for ARB Grand Master.

This field is used to store the active peer connected to an instance. In
wr_mon tool, it replaces the field peer on the display which was not
very explicit when many peers are connected on the same port. The field
activePeer takes the value of peer field in the following cases :

           MASTER          UNCALIBRATED/SLAVE
P2P     Rx PDELAY_RESP    Rx qualified ANNOUNCE
          (Filtered)
E2E       DELAY_RESP      Rx qualified ANNOUNCE

In other cases, the activePeer field is set to 0

The fields in timePropertiesDS are been reevaluated. The file bmc.c
contains a table showing the different use cases.

For a GM the FSM must not be called until:
- the timing mode has not been programmed
- the clock quality has not been verified

These 2 actions : locking_reset() and enable_timing_output(0) must be
done also when the extension is not active.

If a port is in INITIALIZING state, we must not leave from this state as
for a GM we must stay in this state until the GM is locked.

The frequencyTraceable and timeTraceable fields in timePropertiesDS are
now set to TRUE only when the defaultDS clock class is
PTP_CLASS_GM_LOCKED(6) or PTP_CLASS_GM_HOLDOVER(7). These field values
will follow the degradation of the clock class in case of locking issue.

The wrs_locking_reset() function was sending a reset command that was
making the port going down. This function just play with the timing mode
now.

During intensive tests playing with ports up and down, the select() call
returned sometime the error value EINVAL because the given timeout was
negative.

This modification avoids duplication of files.

The timeout_t structure is already defined in libwr (wrs arch) and has
different fields. Renaming this local structure avoid compilation
conflicts.

Some default attribute values were not compliant with the PTP standard.
These default attribute values are used when :
- attributes are not defined in ppsi.conf file
- attribute values in ppsi.conf file are out of range

- Force L1SYNC DISABLE state when the extension is not ON
- Disabling of the PLL must be done only on slave/uncalibrated states
when we leave l1sync UP state.