netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Christian Riesch <christian.riesch@omicron.at>
Cc: "Daniel Glöckner" <dg@emlix.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: PTP_PEROUT_REQUEST and clock stepping
Date: Fri, 12 Sep 2014 08:33:10 +0200	[thread overview]
Message-ID: <20140912063310.GA6198@netboy> (raw)
In-Reply-To: <CABkLOboeo_+37rE84gPTEKnmXD+599fRtnBZSR465y9aZeOdrw@mail.gmail.com>

On Fri, Sep 12, 2014 at 08:24:49AM +0200, Christian Riesch wrote:
> On Thu, Sep 11, 2014 at 11:52 AM, Daniel Glöckner <dg@emlix.com> wrote:
> > Only a small fraction of people
> > using periodic outputs will want to schedule the start of the signal at
> > a specific time in the future and only a fraction of those will use a
> > .period value that is so small that they can't use a timer to configure
> > the periodic output within .period/2 before the desired start time.
> 
> Ok, I got it now. So you are suggesting to change the behavior of
> PTP_PEROUT_REQUEST, aren't you? And break existing applications?
> Christian

I think he wants the periodic output to continue at the same phase and
frequency, even when you reset the clock time.

However, this is impossible to acheive because the hardware does not
support it.

Thanks,
Richard

  reply	other threads:[~2014-09-12  6:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 16:16 PTP_PEROUT_REQUEST and clock stepping Daniel Glöckner
2014-09-10 17:26 ` Richard Cochran
2014-09-11  9:52   ` Daniel Glöckner
2014-09-12  6:17     ` Christian Riesch
2014-09-12  6:24     ` Christian Riesch
2014-09-12  6:33       ` Richard Cochran [this message]
2014-09-12 11:40         ` Daniel Glöckner
2014-09-12 14:40           ` Richard Cochran
2014-09-12 15:19             ` Daniel Glöckner
2014-09-13  9:19               ` Richard Cochran

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=20140912063310.GA6198@netboy \
    --to=richardcochran@gmail.com \
    --cc=christian.riesch@omicron.at \
    --cc=dg@emlix.com \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).