The capability command for phc_ctl does not display the number of pins
or the cross timestamping support. Add this as output so that the user
can see the complete device capabilities.
Signed-off-by: Jacob Keller
---
phc_ctl.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff
This series provides a couple of updates to the phc_ctl utility. First, we
display additional capabillity information such as the cross timestamping
support as well as the number of pins.
The second patch adds a new command, "pin_cfg", which will query the pin
configuration for all of the
Add a new function to phc_ctl to display the devices pin configuration
data. First, obtain the device capabilities to determine the number of
pins. Then, for each pin, print the name, function, and channel
information.
Signed-off-by: Jacob Keller
---
phc_ctl.c | 73
Hi Yangbo,
> > > May I have your suggestion here? To maintain gPTP time in software,
> > > I just copied kernel timecounter code into linuxptp for usage.
> >
> > Why? That sounds wrong.
>
> Regarding to physical clock adjustment, that's confusing. This will changes
> neighbor rate ratio
In port_synchronize(), when the clock returned SERVO_UNLOCKED and
port_dispatch() triggered a switch of the PHC, the variable "s" would
point to a servo which was already freed and the following call of
servo_offset_threshold() would read invalid memory.
Don't save the servo before dispatching
Signed-off-by: Miroslav Lichvar
---
port.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/port.c b/port.c
index 07ad3f0..d051403 100644
--- a/port.c
+++ b/port.c
@@ -3036,14 +3036,14 @@ struct port *port_open(int phc_index,
p->versionNumber = PTP_VERSION;
The first two patches fix bugs I came across when developing and testing
the third patch, but are not really related to it.
The third patch allows a unicast master table in the config to be used
by multiple ports, which should simplify ptp4l configuration in some
cases and make it usable with
Don't require each port to have its own master table specified in the
config. Instead of ports claming configured tables, clone the table in
each port, so different ports don't interfere with each other.
Signed-off-by: Miroslav Lichvar
---
port.c | 3 ++-
ptp4l.8 | 4 +---
