On Sun, Nov 08, 2020 at 08:34:33AM -0800, Richard Cochran wrote:
> @@ -1114,8 +1114,9 @@ struct clock *clock_create(enum clock_type type, struct
> config *config,
> /* Due to a bug in older kernels, the reading may silently fail
> and return 0. Set the frequency back to make sure fadj is
> the actual frequency of the clock. */
> - clockadj_set_freq(c->clkid, fadj);
> -
> + if (!c->free_running) {
> + clockadj_set_freq(c->clkid, fadj);
> + }
Makes sense to me, but maybe it's time to drop the workaround? Looking
at the git log, it was added in 2013. Are people still using linuxptp
on kernels older than that?
--
Miroslav Lichvar
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
