I need to be more careful before pushing to master...
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

comments used to extend to the next terminator (including the
semicolon), but editors paint comment-color the whole line, so we'd
better fix it rather than documenting an uncommon behaviour.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Davide Ciminaghi <ciminaghi@gnudd.com>

Signed-off-by: Davide Ciminaghi <ciminaghi@gnudd.com>

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

Even if we count failure events for SNMP (in the switch), we actually
never generate them.  The code has always been tracking phase for
any offset smaller than one clock tick (8ns or 16ns), but we'd better
jump in phase (and leave TRACK_PHASE servo state) and this is a failure.

With this commit, to loos track_phase in wrpc you can just force
the setpoint far enough from the calculated one: e.g.

  [..] cko:2 setp:929 [...]

  wrc# pll sps 0 500

  [...]  ss:'SYNC_PHASE' [...] cko:431 setp:1367 [...]

then it takes 15 iterations to converge, but that's because the
calculations the first time (as shown) are wrong. A real glitch
loosing track_phase would be recovered in 3 iterations.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

This is needed for profiling in wrpc-sw.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

when using VLANs, reception of each VLAN-tagged ptp frame resulted
in printf(), which was syslog-ed to the server... changed printf
into pp_dial(ppsi, frame, 1,...)

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>

This commit has to be preserved as it is included in WRS release 4.2

for tx stamps, when we added the check about the frame content
(to avoid problems with high data load, see 4179fcdc), it got broken
for UDP. That's because the cmesg we get back includes a raw frame
anyways, even if we transmitted UDP or other protocols.

So now check for the trailing part of the frame we get back, to
avoid any extra leading header whatever its lenght.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

During track-phase we used to find the setpoint and then track changes in
the master-to-slave delay, thus not zeroing any initial error that may
happen (e.g. the initial sample was more jittery than average).

Now we use the clock offset as correction source. Setpoint is
adjusted by 1/4th of the current offset, to smooth a little the jitter.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This is likely the result of my cleanup of wr-servo, where I forgot
some pieces.

Greg collected some interesting logs in wrpc where the setpoint
was calculated wrongly. This fixes the thing and removes some redundancy.

I "git diff" order:

- avoid WR_UNINITIALIZED, really unused. Do what's needed at
  wr_servo_init() time

- adjust phase to 0 at init time, where s->cur_setpoint is set (we
  really should set and use in a single unified place)

- set delta_ms_prev before entering TRACK_PHASE, not earlier where it
  doesn't fit

- avoid extra checks of non-zero offset.seconds and
offset.nanoseconds, because they are checked at the beginning anyways.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This adds -Wstrict-prototypes -Wmissing-prototypes and takes actions
accordingly.

Some of the solutions are ugly, especially in the bare architectures,
but I prefer to be warned if I take dangerous paths wrt prototypes while
writing further code.

I'm upset by those two not being included in -Wall, as they used to.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The existing rule to check whether WRPCSW_ROOT is properly set (by
environment or default in Kconfig) forced a dependency on all object
file.  Thus, all files were rebuilt every time.

We now force the check only as a dependency for the first object file,
which means ony fsm.o (and then ppsi.o) is built if you run "make" on
a just-built source tree.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This reverts commit 1d5a461d.

actually, the error count must be zeroed every time, not only after
printing: we want to print if the error persists for 5 iterations, not
every 5th time.

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

This is a temporary workaround. We are going to fix the tx/rx functions
to received the header and payload together, but currently they are
separate so the offset must be 0 for raw ethernet.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

It's done to prevent PPSi leaving Slave state on the WRS when high load of
background traffic is present. It's just a temporary workaround. In the future
the HDL of the switch has to be fixed so that PPSi frames have higher priority
than the normal traffic and are not dropped when WRS is overloaded.

Make max offset range from -500ps to +500ps, instead of -1000ps to +1000ps
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Fix problem with hanging send in PPSI

Even under load, with queues full, the wrs delays frames less than one ms.

Thus, if we didn't get a timestamp in 1ms, we won't ever get it. Add
some software delay and clearly we don't need 100ms as in current
code.  Please note that all state machines are not running during this
wait, as we are single-process single-thread.

So now we wait for 6ms at most (3 times 2ms at most, but the first
time we may get an older timestamp, then discarded).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This turns the while(1) with internal retry++ to a loop based on retry.
With two changes:

1- when recvmsg() gets EAGAIN (or other errors), we loop over instead
of returning. Maybe this doesn't happen anymore thanks to the change
from POLLIN to POLLERR (previous commit), but this is philosophically
correct anyways.

2- we don't print anything when poll() returns 0, as these messages
were redundant, especially when there were many in a row. And if
nothing is there we expect to get 0. So we removed these:

   poll_tx_timestamp: poll() = 0 (Success)

Still, knowing the timestamp was late is useful, but a single message
suffices, and it's there now.  If you wonder why we loop instead of
using a longer timeout, the reason is we must get rid of timestamps
for older frames (the ones that timeout at the previous iteration).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

It may happen, though rarely, that frames are not sent (or not freed
at kernel level), and we build up an output queue, so at some point we
get -EAGAIN on sending.

With blocking writes, this situation was stalling the whole process.
This patch helped us diagnosing a problem in our own network driver,
which had a memory leakage, but using non-blocking sockets and
reporting erors is the right thing to do anyways.

This patch reports the error using pp_diag with a priority 0; thus
the message is always printed, but by virtue of pp_diag we have the
name of the port automatically added.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

While the manual pages say nothing, https://lwn.net/Articles/291793/
hints that we should use POLLERR instead of POLLIN.

I hoped to get rid of some of the poll messages, but nothing changes
in simple tests. I hope we get rid of the EAGAIN in the later recvmsg()
(likely with POLLIN we got the socket as readable, but nothing was
in the error queue -- we had a new incoming frame instead).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

commit 3b985b02 added the new vlan-aware issue function, but didn't
remove the old call. Thus, wrs is sending out announce messages twice
in a row (with two proper sequence numbers).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

The old code used to discard every other tuple, because when "wait for
hardware was set", the code cleared the flag and did nothing. This was
exposed by one of the clean-up passes, but I chose not to change the
behaviour.

Now I do the normal work when wait_for_hw gets cleared.  However, as a
side effect, wr_mon was always saying "wait for hardware", because any
action would set the flag.

Thus, the solution is not setting the flag in TRACK_PHASE, but only
in the initial SYNC_SEC and SYNC_NSEC states. The code then checks
if the hardware is busy, irrespective of any flag.  The result in wr_mon
is matching reality, and the code works twice as fast as it used to.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The previous code to set system time from WR time is not really
working.

It is implemented in wrs_time_ops->set and it relies on ppsi being
non-wr slave before being wr slave, but this should not happen.  Such
code, with its "weird" message, remains in place to be used when we
run in non-wr mode (as slaves).

This new code is the right thing to do: when we are done syncing the
"big steps" in WR, and start dealing with sub-tick, we jump system
time.

There is no correction for TAI/UTC because the time operations for
arch-unux (set/get) already do the conversion.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Since commit f3d427ee, we lost the concept of "next_state" (to make code
simple), but this means that we should report to wr_mon the state string
we acted on, not the next. Otherwise, we see SYNC_PHASE all the time,
when we are actually waiting for SYNC_SEC or SYNC_NSEC to complete the
adjustment.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

Earlier we only called it in from slave state, but it's correct to do
it in any state (thus also from st_com_master_handle_announce, used by
listening and master mode.

This makes WR syncing much faster.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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