All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Sebastien Laveze <sebastien.laveze@oss.nxp.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	yangbo.lu@nxp.com, yannick.vignon@oss.nxp.com,
	rui.sousa@oss.nxp.com
Subject: Re: [PATCH net-next] ptp: add vclock timestamp conversion IOCTL
Date: Wed, 13 Oct 2021 06:10:17 -0700	[thread overview]
Message-ID: <20211013131017.GA20400@hoboy.vegasvil.org> (raw)
In-Reply-To: <ca7dd5d4143537cfb2028d96d1c266f326e43b08.camel@oss.nxp.com>

On Wed, Oct 13, 2021 at 11:56:00AM +0200, Sebastien Laveze wrote:
> My proposal includes handling PHC offset entirely in software. There is
> no way (and we agree on this :)) to change the PHC offset without
> impacting children virtual clocks.

That means no control over the phase of the output signals.  Super.
 
> Done in software, an offset adjustment has no impact at all on virtual
> clocks (since it can always be done atomically, not RMW).
> 
> So with, no hardware clock phase adjustment and limited frequency
> adjustments, 

But you can't make the end users respect that.  In many cases in the
wild, the GM offset changes suddenly for various reasons, and then the
clients slew at max adjustment.  So there is no expectation of
"limited frequency adjustments."

Thanks,
Richard


> we believe it can be made fully transparent to virtual
> clocks. And that would improve the current limitation of no adjustment
> all, and would unblock the support of features like Qbv for devices
> with a single clock.
> 
> Thanks,
> Sebastien
> 

  reply	other threads:[~2021-10-13 13:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27  9:32 [PATCH net-next] ptp: add vclock timestamp conversion IOCTL Sebastien Laveze
2021-09-27 14:59 ` Richard Cochran
2021-09-27 16:00   ` Sebastien Laveze
2021-09-27 20:23     ` Richard Cochran
2021-09-28 11:50       ` Sebastien Laveze
2021-09-28 13:31         ` Richard Cochran
2021-09-29 15:00           ` Sebastien Laveze
2021-09-30 14:35             ` Richard Cochran
2021-10-07 13:31               ` Sebastien Laveze
2021-10-07 20:19                 ` Richard Cochran
2021-10-08  7:13                   ` Sebastien Laveze
2021-10-09 18:24                     ` Richard Cochran
2021-10-09 18:25                       ` Richard Cochran
2021-10-11 12:58                     ` Richard Cochran
2021-10-12 16:14                       ` Richard Cochran
2021-10-13  9:56                       ` Sebastien Laveze
2021-10-13 13:10                         ` Richard Cochran [this message]
2021-10-13 13:28                           ` Sebastien Laveze
2021-10-13 17:54                             ` Richard Cochran
2021-10-14 13:27                               ` Sebastien Laveze
2021-09-27 18:28 ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211013131017.GA20400@hoboy.vegasvil.org \
    --to=richardcochran@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rui.sousa@oss.nxp.com \
    --cc=sebastien.laveze@oss.nxp.com \
    --cc=yangbo.lu@nxp.com \
    --cc=yannick.vignon@oss.nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.