Commit based on the commit mentioned below from wr-switch-sw repo.
It required to add a header wrs-msg.h to support "pr_error" function.
"pr_error" will be printed as regular error, all other pr_* are ignored.

userspace/libwr: Print error message on multiple shmem locks

Print error message when shmem is locked or unlocked multiple times.
To be precise it will print error only on even locks or unlocks.

Move the increment of sequence before checking the flags to simplify further
if-conditions.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

add util.c for functions get_monotonic_*
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Because picos_mu_prev was not updated in the correct place, variable
n_err_delta_rtt was increased at every update. This resulted in errors
on the switch via SNMP.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

shmem is locked already in the function wr_servo_update
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Increase of WRS_PPSI_SHMEM_VERSION is needed at least due to the commit:
pdelay/wrservo: wr_servo calculates link delay and offset to master using P2P
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Merge commits needed due to changes in the switch:
--uplift of the buildroot
--change names of the interfaces from wrX (0-17) to wriX (1-18)
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We just reinit timeouts on reception of a delay response This way the
delay request interval is reinitialized and set to the proper value.

previous code failed for logSyncInterval < 0
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This fixes a bug introduced by f1d048c3
(conf.c: use f_simple_int() for assigning simple integer options):
we used ASSIGN_INT_FIELD for assigning values to variables shorter than
int, while the destination pointer was set to int *, so neighbouring
fields were overwritten.

Another commit in a non-merged branch adds a build-time check to
avoid repeating this bug, but field names changed, so let's avoid
cherry-picking it here at this point.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Before this commit, ANNOUNCE messages were sent with grandmaster-related
fields equal to 0. Values for such fields were taken from the parentDS data
set, which did not look properly initialized.

Paragraphs 8.2.3.2 to 8.2.3.9 of the ieee1588 standard specify
initialization values for the parentDS data set.
Many such values come from the defaultDS, so care must be taken to
initialize the parent data set __after__ the default data set.
We do this in pp-initializing().
Signed-off-by: Davide Ciminaghi <ciminaghi@gnudd.com>

This kills the ambiguously-named pp_ms_to_timeout(), and
adds pp_next_delay_{1,2,3}.

This commit meanwhile fixes the timeouts in the pdelay master (who didn't
consider the request timeout), and in the pdelay listener (because
LISTEN mode must send pdelay requests).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We don't zero timer any more (see preceding commit), no need
to special case anything.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This was only used by timeout_z() (check if expired and disable it)
that is not useful nor used since last commits.

Timeouts are always running (time is always running...), it's just a matter
of whether we check them or not.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

It was not a good idea: there is no need to clear a timeout if
it is being re-initialized in the same function anyways. If, OTOH,
we change state, it won't be referenced any more so there's no need
to disable it.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We now have the simpler pp_timeout(). Moreover, most uses were
needless, because now we reset all timeouts when we change state.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This, btw, made me note that we have a problem with pdelay and
multiple vlans.

Multiple vlan is a hack anyways....
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

To help me knowning what is audited and what is not, I will rename
the "common functions" to fsm-lib. Let's now open this pp_lib_*
name space with some more timeout cleanup.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Several changes to the timeout API, simplifying the code and allowing
more simplification later.

 * TO_ANN_INTERVAL renamed to TO_ANN_SEND (as opposed to TO_ANN_RECEIPT)

 * TO_SYNC renamed to TO_SYNC_SEND for symmetry with above

 * added timeout_init() to take not of the waiting values

 * timeout_set now receives only the index, not the value (see above)

 * __timeout_set added for those that want a specific value

 * timeout_rand is gone, as timeout_set knows which to randomize

 * all users fixed
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This moves all functions to timeout.c, so the header is more readable.
As a side effect, the binary is smaller (a few hunded bytes for all
archs, almost 1k for wrpc).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Currently, only the slave sends pdelay_request, so only the master
is handling them.  However, only the slave called pp_hooks.handle_preq()
-- thus it was never called.

Waiting for a test session about this assignment to correctionfield
done by wr_handle_preq(), this removes a little duplication and ensures
the hook is always called.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

state-slave now does the same as state-pclock, according to the
delay mechanism being configured in the globals (still, it
replies to pdelay_request irrespective of the delay mechanism being
configured, which may not be standard but is good in itself).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

(the previous commit picked two similar tivial changes)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>