this is a software part of new (additional) diagnostics for WR PTP Core.
It allows to access diagnostics values through WB registers (e.g. PCI
bus). This is useful for integration of WR with CERN cotrols infrastructure,
such as FESA. It allows the host machine (of SPEC/SVEC/etc) to easily
access information about the health of WR PTP Core.

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

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

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

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

When a number contains "0" on 9th and adjacent lower decimal position
these 0's were not printed.
In practice number:
1000000000 was badly printed as 10
1000000001 was badly printed as 11
1000234567 was badly printed as 1234567
1234567890 was correctly printed as 1234567890
1200000000 was correctly printed as 1200000000

Both stat and gui were affected by this bug.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

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

This allows several functions to be static in the files where they
are defined. See temperature.c for an example.

But mainly, the idea is allowing ease addition of features (likely
Kconfig'd ones) for specific WR users, without any modification to the
main function and other generic code.  This will happen soon for snmp,
for example.

We may push this a little further, by moving all shell stuff into
shell.c, the ptp task within ppsi itself, and so on. But now my time
is over.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This commit adds data structures, methods and a process to manage
temperature.  Currently the only temperature being read is the onewire
thermometer, so there is no difference with what we had before.
The cost is 1.1 kB in binary size.

Well, there is a difference: only the stat engine was reading
temperature, while now the thermometer is read continuously (every 15
seconds, or another Kconfig-urable interval).  This takes quite some
CPU time (18.5ms per polling loop, but allows any user to read
temperature (using the API we now provide) without re-reading the
onewire bus.

The real aim of this is monitoring a board-specific set of sensors,
as implemented and show in the next commit.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

This solves http://www.ohwr.org/issues/1218

We used to have a "needIP" variable, but we need three states:
if the address was set by bootp, we run bootp again when the link goes
up, but if it was a static assignment we do not (and keep the static one).

So I renamend needIP to a 3-valued ip_status. The rename ensured the
compiler found all users.  Also, the messages are now 3-headed, so
the user know whether the address is static or it comes from bootp.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This is a step towards profiling. The functions being polled return
whether or not they did actually work.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

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

* library files can be built even if not used (this gets us more build-time
testing, as for example I usually build with no IP support).

* Some ifdefs are not needed, use HAS_IP instead. This adds a few
bytes to some configurations (not all, can't tell why), but I find it
acceptable.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Actually, Etherbone is in gateware, and this option only enables Internet
Protocol in the software.  This fixes a long-standing misunderstanding.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We have not been using mprintf for ages now, and it's better for the
code to explicitly call pp_printf, so people is aware of it.

We might "#define printf pp_printf", but currently we'd better not.
Maybe when we turn this into a real operating system, next millennium...
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The gui is timely: it refreshes every that many seconds, but I'd
better see a change immediated when it happens.  This commit
introduces monitoring of the wr-servo update count, so if anything
changed an information scree is dumped.

This is different from stats (two commits ago), because we want to
refresh timely in any case, so the user sees the thing is active.

You can verify the effect of the commit after "refresh 4": timely
refresh is now slower than servo updated and you'll see how gui
updates are synced with the ptp protocol.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

With the new "only print if sth happens" way, sometimes stats is
just silent forever. This happens if we are master or if no slave
is active (well, and during initial setting up the wr link).

So now typing "stat" or "stat on" will turn on stats and print a line
of statistics, every time -- or the line "statistics now off".
This happens by changing the internal status of monitor_ppsi.c,
now exported to the cmd_stat.c.

This is the result on a master system:

   wrc# stat
   lnk:1 rx:0 tx:3 lock:1 sv:0 ss:'' aux:1 sec:5 [...]
   wrc#
   wrc#
   wrc# stat
   statistics now off
   wrc#
   wrc#
   wrc# stat
   lnk:1 rx:0 tx:11 lock:1 sv:0 ss:'' aux:1 sec:8 [...]
   wrc#
   wrc#

And this is what happens when we become slave:

   wrc# mode slave
   Locking PLL
   wrc# ptp start
   Slave Only, clock class set to 255
   wrc# lnk:1 rx:57 tx:60 lock:1 sv:1 ss:'SYNC_SEC' aux:1 sec:49 [...]
   lnk:1 rx:70 tx:64 lock:1 sv:1 ss:'SYNC_NSEC' aux:1 sec:1444901411 [...]
   lnk:1 rx:77 tx:66 lock:1 sv:1 ss:'SYNC_PHASE' aux:1 sec:1444901414 [...]
   lnk:1 rx:83 tx:68 lock:1 sv:1 ss:'WAIT_OFFSET_STABLE' aux:1 sec:1444901416 [...]
   lnk:1 rx:87 tx:69 lock:1 sv:1 ss:'WAIT_OFFSET_STABLE' aux:1 sec:1444901417 [...]
   lnk:1 rx:90 tx:70 lock:1 sv:1 ss:'TRACK_PHASE' aux:1 sec:1444901418 [...]
   lnk:1 rx:94 tx:71 lock:1 sv:1 ss:'TRACK_PHASE' aux:1 sec:1444901419 [...]
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This change monitors the update_count of wr_servo, and only prints
a statistics line when something happens.

This means we won't have long "TRACK_PHASE" listings when the master
is dead. Moreover, we see changes when they happen, not at a random
time during the next second.

The bad side of the thing is that if nothing happens in the wr servo,
nothing is ever printed. But see next commit.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

The function was only called with "0" as argument. Drop it.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This time I added -Wmissing-prototypes and fixed accordingly. Again, this
used to be part of -Wall and I'm disgusted by it not being so any more.

What does "all" mean, then?
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

I added -Wstrict-prototypes, that used to be included in -Wall settings
but is not.  Actually, I think it should be an error to not specify an
argument list by now.  If any, -traditional is there for old timers.

Fortunately no bug was exposed by the missing prototypes.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

remove waiting state, make waiting flag instead
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

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

Needed since ppsi moved to shmem and removed cur_servo_state structure from
servo.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Done as a part of work to move hal to shm in wrs.

Done in this commit:
--use wrpc_get_port_state instead of halexp_get_port_state
--make wrpc_get_port_state fill hal_port_state structure in the way how HAL
  fills shmem.
--update lib/net.c to use struct hal_port_state instead of hexp_port_state_t
--update monitor/monitor_ppsi.c to use struct hal_port_state instead of
  hexp_port_state_t
--update ppsi to get needed changes
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>

	- Add new command "refresh" to change update period of gui and stat
	- Delete "stat cont" command
	- Update "stat" command to work as older "stat cont" one
	- Update the wrc_main.c file to check if the log messages must be generated one time

Note: If you set period to 0, the log messages are only generated one time.

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

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