On Mon, May 25, 2015 at 09:29:58PM +0200, Richard Cochran wrote:
> When running with Synchronous Ethernet (SyncE), the correct clock
> frequency is provided by the link partner. In this case, only the
> offset needs correcting.
I'm not familiar with SyncE. What does this mean for the PHC device?
The frequency is automatically corrected by the driver or the device
itself and the correction is visible in the timex structure from
clock_adjtime() or that the apparent frequency offset is 0?
> @@ -1393,6 +1395,10 @@ enum servo_state clock_synchronize(struct clock *c,
> tmv_t ingress, tmv_t origin)
>
> tsproc_set_clock_rate_ratio(c->tsproc, clock_rate_ratio(c));
>
> + if (c->freq_noadj) {
> + adj = 0.0;
> + }
> +
> switch (state) {
> case SERVO_UNLOCKED:
> break;
Hm, so this effectively disables the servo and the only correction of
the clock is step when the threshold is reached?
I'm wondering if this could be done as a servo option or a completely
new servo.
--
Miroslav Lichvar
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
