On 18/03/2020 18:13, Jacob Keller wrote:
On 3/16/2020 1:58 PM, Grygorii Strashko via Linuxptp-devel wrote:
This is the userspace program I have worked on to get the synchronization
working. Currently the servo part of the tool is in very hacky shape. Before
cleanup I wanted to get more inputs on where it can be integrated. But anyways
as you said, Ill clean it up and post it as a separate tool. We can then decide
the correct location.
And I'd like to rise additional question here.
The above solution adds PPS generation using PTP_EXTTS events and PIN output,
but, as per my understanding, there are no way now to feed phc2sys with such
PPS.
So question is how PPS generated by PTP_EXTTS events can be wired to phc2sys?
- option1: update phc2sys to accept PTP_EXTTS as PPS
- option2: allow kernel PHC to generate or PTP_CLOCK_EXTTS/or
PTP_CLOCK_PPS/or both
by somehow configuring that PTP_EXTTSx is also PPS.
Challenge with option 2 is that Kernel PPS configuration is part of
ptp_clock_register() and so static.
I think a new option that can use PTP_EXTTS as an input, and some option
to specify what the expected period of that signal is, so that any rate
could be used, not just 1 PPS.
So, a variation of option 1, where phc2sys is modified to have a mode
for PTP_EXTTS which is somewhat distinct from PPS mode.
Another thought, wouldn't it be useful to add additional interface to PWM
to adjust period/duty_cycle which actually could accept ppb/ppm values as input?
or smth. like this.
--
Best regards,
grygorii
_______________________________________________
Linuxptp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
