public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Chavent <Paul.Chavent@onera.fr>
To: linux-usb@vger.kernel.org, gregkh@linuxfoundation.org,
	jhovold@gmail.com, fschaefer.oss@googlemail.com, jslaby@suse.cz,
	max@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Enable PPS reporting for USB serial devices
Date: Tue, 10 Sep 2013 10:00:38 +0200	[thread overview]
Message-ID: <522ED1A6.9020000@onera.fr> (raw)
In-Reply-To: <20130910073105.GB5030@enneenne.com>

Hi.

At the bottom of the  description of the patch set, i warn about the 
latencies and jitter.

I did "real" test with a pps generated by a workstation (i haven't 
tested with a precise pps yet), so the the jitter don't mean anything. 
But the magnitude of difference between uart and usb pps isn't 
negligible (~400µs with uart compared to ~1ms with usb).

Do you think that, depending on the application, such clock instability 
is a flaw ?

I will run new tests with a precise pps source later.

I will also try to measure the latency of the pss signal through the 
usb, and see if it is constant. Perhaps we could introduce parameters to 
add offset to the pps signal used by the kernel consumer (the same way 
we can add the offset with PPS_FETCH ioctl) later.

Regards.

Paul.

On 09/10/2013 09:31 AM, Rodolfo Giometti wrote:
> On Mon, Sep 09, 2013 at 06:01:15PM +0200, Paul Chavent wrote:
>> Hi.
>>
>> This series enable the PPS reporting for USB serial devices.
>
> I have nothing against with this solution but consider that reporting
> a PPS signal through USB bus may add unknown delays that may vanish
> clock stability... as far as I know you should not use USB serial port
> with PPS. Have you some statistics about clock stability in a real
> implementation?
>
> Ciao,
>
> Rodolfo
>

  reply	other threads:[~2013-09-10  8:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 16:01 [PATCH 0/5] Enable PPS reporting for USB serial devices Paul Chavent
2013-09-09 16:01 ` [PATCH 1/5] USB : serial : remove tty arg of handle_dcd_change Paul Chavent
2013-09-09 17:45   ` Johan Hovold
2013-09-09 17:48     ` Johan Hovold
2013-09-10  8:09     ` Paul Chavent
2013-09-09 16:01 ` [PATCH 2/5] USB : serial : get protected tty in handle_dcd_change Paul Chavent
2013-09-09 18:03   ` Sergei Shtylyov
2013-09-09 16:01 ` [PATCH 3/5] USB : serial : call handle_dcd_change in ftdi driver Paul Chavent
2013-09-09 16:01 ` [PATCH 4/5] USB : serial : invoke dcd_change ldisc's handler Paul Chavent
2013-09-09 16:36   ` Greg KH
2013-09-09 16:01 ` [PATCH 5/5] USB : serial : pl2303 wake up after dcd status check Paul Chavent
2013-09-10  7:31 ` [PATCH 0/5] Enable PPS reporting for USB serial devices Rodolfo Giometti
2013-09-10  8:00   ` Paul Chavent [this message]
2013-09-10 20:02   ` Gary E. Miller
2013-09-12  7:53     ` Rodolfo Giometti

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=522ED1A6.9020000@onera.fr \
    --to=paul.chavent@onera.fr \
    --cc=fschaefer.oss@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhovold@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=max@suse.de \
    /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