<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
><br>
> In contrast to the standard Linux system clock, a PHC is<br>
> adjustable in hardware, for example using frequency compensation<br>
> registers or a VCO. The ability to directly tune the PHC is<br>
> essential to reap the benefit of hardware timestamping.<br>
<br>
</div>There is a reason for not being able to shift posix clocks: The system has<br>
one time base. The various clocks are contributing to maintaining that<br>
sytem wide time.<br>
<br></blockquote><div>Adjusting clocks is absolutely essential for proper functioning of the PTP protocol. The slave obtains and calculates the offset from master and uses that in order to adjust the clock properly, The problem is that the timestamps are done via the hardware. We need a method to expose that hardware so that the ptp software can properly adjust those clocks.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I do not understand why you want to maintain different clocks running at<br>
different speeds. Certainly interesting for some uses I guess that I<br>
do not have the energy to imagine right now. But can we get the PTP killer<br>
feature of synchronized accurate system time first?<br></blockquote><div><br>The problem is maintaining a hardware clock at the correct speed/frequency and time. The timestamping is done via hardware, and that hardware clock needs to be accurate. We need to be able to modify that clock. Yes, having the system time be the same value would be nice, but the problem comes because we don't want to jump through hoops to keep that hardware clock accurate to the ptp protocol running on the network.<br>
</div><div><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> Instead, the patch set provides a way to offer a Pulse Per Second<br>
> (PPS) event from the PHC to the Linux PPS subsystem. A user space<br>
> application can read the PPS events and tune the system clock, just<br>
> like when using other external time sources like radio clocks or<br>
> GPS.<br>
<br>
</div>User space is subject to various latencies created by the OS etc. I would<br>
that in order to have fine grained (read microsecond) accurary we would<br>
have to run the portions that are relevant to obtaining the desired<br>
accuracy in the kernel. <br></blockquote><div><br>All of the necessary features for microsecond or better accuracy are done via the hardware. You can get accuracy to within <10 mircoseconds while only sending sync packets and such once per second. The reason is because the hardware timestamps are very accurate. But if we can't properly adjust the clocks time and frequency, we cannot maintain the accuracy of the timestamps. <br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div> </div></div></blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="h5">
--<br>
To unsubscribe from this list: send the line "unsubscribe netdev" in<br>
the body of a message to <a href="mailto:majordomo@vger.kernel.org">majordomo@vger.kernel.org</a><br>
More majordomo info at <a href="http://vger.kernel.org/majordomo-info.html" target="_blank">http://vger.kernel.org/majordomo-info.html</a><br>
</div></div></blockquote><br></div><br>