Review configuration interface

[davidcemin]

Current configuration interface is done through switches upon gPTP initialization. Improve the current one to support more parameters.

Here the current configuration switches we have:
./daemon_cl [-S] [-P] [-M ] [-A ] [-G ] [-R <priority 1>]
-S start syntonization
-P pulse per second
-M save/restore state
-A initial accelerated sync count
-G group id for shared memory
-R <priority 1> priority 1 value
-T force master
-L force slave

We could embed that on a gPTP.cfg and read this file on its initialization. Eventually we will need more parameters, as for instance the phy delay, which currently has to be manually set on a define (and hence recompile the gPTP). Code below:

linux/src/linux_hal_generic.cpp:52:#define TX_PHY_TIME 184
linux/src/linux_hal_generic.cpp:53:#define RX_PHY_TIME 382
linux/src/linux_hal_generic.cpp:55://#define TX_PHY_TIME 8000
linux/src/linux_hal_generic.cpp:56://#define RX_PHY_TIME 8000

[andrew-elder]

Need more details David....

[davidcemin]

Andrew, please take a look now.

[andrew-elder]

Thanks. .cfg file sounds like a good idea.

[andrew-elder]

Duplicate of #253

[davidcemin]

If we put the default configuration from daemon_cl in a file called lets say gPTP.cfg, we would have something like below.

The idea would be starting the daemon using the file as another option, as for instance:

daemon_cl eth0 -f gPTP.cfg.

Default command line parameters

sintonize = true
pulse_per_second = false
accelerated_sync_count = 0
override_port_state = false
port_state = PTP_MASTER
priority1 = 248
restore_state = false
restore_state_file = restore.dat
ipc_groupname = ptp

PHY Ingress/Egress delay in nanoseconds

tx_phy_time = 184
rx_phy_time = 382