public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: "Kristian Høgsberg" <krh@bitplanet.net>
Cc: "Pieter Palmers" <pieterp@joow.be>,
	"Kristian Høgsberg" <krh@redhat.com>,
	"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: adopt read cycle timer ABI from raw1394
Date: Tue, 02 Oct 2007 08:45:22 +0200	[thread overview]
Message-ID: <4701E902.3070104@monom.org> (raw)
In-Reply-To: <59ad55d30710010903y76330624ka45747c0b5983cfd@mail.gmail.com>

>>> Pieter, do applications like yours need the cycle counter only for a few
>>> predetermined packets or for each and every packet?
>> We need it for every packet for two reasons:
>> 1) it's the only way to determine how many packets were dropped when
>> packet drops are flagged in the callback
> 
> Your application should know what the timestamp should be for each iso
> receive callback and if you see a larger value than expected you can
> use that to calculate how many cycles were lost.

That might not work if the device is synchronized to SPDIF for example. 
In this case it is possible (and very likely) that the two clock domains 
(SPDIF and the firewire bus) drift. The time difference between two 
timestamps do not have to be the same all the time. So it can be hard 
(possible?) to predict the next timestamp correctly.

daniel

  reply	other threads:[~2007-10-02  7:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-29  8:41 [PATCH] firewire: adopt read cycle timer ABI from raw1394 Stefan Richter
2007-09-29  9:01 ` Stefan Richter
2007-10-01  9:31   ` Pieter Palmers
2007-10-01 16:03     ` Kristian Høgsberg
2007-10-02  6:45       ` Daniel Wagner [this message]
2007-10-05  8:31       ` Pieter Palmers

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=4701E902.3070104@monom.org \
    --to=wagi@monom.org \
    --cc=krh@bitplanet.net \
    --cc=krh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=pieterp@joow.be \
    --cc=stefanr@s5r6.in-berlin.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