If a leap second lookup fails, the likely reason is that the table is out
of date. After all, the leap second table has an expiration date. The
user will surely appreciate if the software complains loudly in this case.
Signed-off-by: Richard Cochran <richardcoch...@gmail.com>
---
ts2phc_nmea_master.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/ts2phc_nmea_master.c b/ts2phc_nmea_master.c
index b217703..e89c2c7 100644
--- a/ts2phc_nmea_master.c
+++ b/ts2phc_nmea_master.c
@@ -190,7 +190,11 @@ static int ts2phc_nmea_master_getppstime(struct
ts2phc_master *master,
lstab_error = 0;
break;
case LSTAB_UNKNOWN:
+ pr_err("nmea: unable to find utc time in leap second table");
+ lstab_error = -1;
+ break;
case LSTAB_AMBIGUOUS:
+ pr_err("nmea: utc time stamp is ambiguous");
lstab_error = -1;
break;
}
--
2.20.1
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
