All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Schmidt <mista.tapas@gmx.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Paul Davis <paul@linuxaudiosystems.com>,
	jackit-devel@lists.sourceforge.net,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [Jackit-devel] irq handler top half timestamps
Date: Fri, 10 Dec 2004 02:35:48 +0100	[thread overview]
Message-ID: <20041210023548.5042f406@mango.fruits.de> (raw)
In-Reply-To: <1102626628.21688.11.camel@krustophenia.net>

On Thu, 09 Dec 2004 16:10:28 -0500
Lee Revell <rlrevell@joe-job.com> wrote:

> On Thu, 2004-12-09 at 22:07 +0100, Florian Schmidt wrote:
> > On Thu, 9 Dec 2004 19:33:42 +0100
> > Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > cleanest would be to somehow make this part of ALSA, just like xrun info
> > > is part of ALSA (the two are related as well). But there are other
> > > details too i guess: a single audio device can have separate interrupts
> > > (for playback and capture?) - in that case which one should ALSA return?
> > 
> > Well, possibly ALSA could keep the timestamps for each substream around?
> > And the ioctl should get parametrized with the substream # so it returns
> > the most current irq timestamp for the selected substream.
> > 
> 
> Doesn't ALSA already do this?  IIRC when you call snd_pcm_period_elapsed
> in the ALSA irq handler the PCM stream is timestamped.

To what kind of timestamp do you refer here? We need a timestamp
relative to a clock that jackd can use, too. Like for example TSC or
RTC. 

Just to give a rundown on the subject to the alsa-devel people. On
jackit-devel we are currently faced with the problem of estimating the
times at which the irq's for the soundcard were actually raised [to be
able to map arbitrary other times to the framecount of the frame
actually sounding at that moment]. For this we timestamp the time that
jackd is actually woken and try to estimate the real irq time from that.

Of course a much better estimate can be achieved if the scheduling
latencies which might occur between raising the IRQ and waking jackd are
eliminated. The earliest place such a timestamp can be taken is in the
top half irq handler.

So it would be very useful, if, for example, the top half irq handler of
the alsa driver would timestamp each IRQ with i.e. a TSC timestamp and
expose this timestamp to the application in userspace.

Flo

-- 
Palimm Palimm!
http://affenbande.org/~tapas/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-10  1:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041209180706.GA11397@elte.hu>
     [not found] ` <200412091819.iB9IJiLX013123@localhost.localdomain>
     [not found]   ` <20041209183342.GB13132@elte.hu>
     [not found]     ` <20041209220741.7562b6a0@mango.fruits.de>
2004-12-09 21:10       ` irq handler top half timestamps Lee Revell
2004-12-10  1:35         ` Florian Schmidt [this message]
2004-12-10  7:52           ` [Alsa-devel] " Jaroslav Kysela
2004-12-10 17:23             ` Florian Schmidt
2004-12-10 17:17               ` Re: [Jackit-devel] " Paul Davis
2004-12-10 17:54                 ` [Alsa-devel] " Florian Schmidt
2004-12-10 19:00                   ` Re: [Jackit-devel] " Lee Revell
2004-12-10 20:51                     ` Paul Davis
2004-12-10 21:01                       ` Lee Revell
2004-12-11  0:56                         ` Florian Schmidt
2004-12-11  2:22                           ` Florian Schmidt
2004-12-15 23:32                             ` [Alsa-devel] " Florian Schmidt
2004-12-16  9:18                               ` Ingo Molnar
2004-12-16 16:33                                 ` tapas
2004-12-16 18:35                                   ` Re: [Jackit-devel] " Lee Revell
2004-12-19 23:45                                     ` Florian Schmidt
2004-12-19 23:38                                       ` [Alsa-devel] " Lee Revell
2004-12-20 15:08                                         ` Re: [Jackit-devel] " Florian Schmidt
2004-12-21  1:30                                           ` [Alsa-devel] " Florian Schmidt
2004-12-21  1:49                                             ` Re: [Jackit-devel] " Lee Revell
2004-12-11  3:17                           ` [Alsa-devel] " Lee Revell
2004-12-20 10:57                             ` Re: [Jackit-devel] " Martijn Sipkema
2004-12-20 11:10                               ` Clemens Ladisch
2004-12-20 11:50                                 ` Martijn Sipkema
2004-12-20 11:52                                 ` [Alsa-devel] " James Courtier-Dutton
2004-12-10  7:41         ` Jaroslav Kysela

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=20041210023548.5042f406@mango.fruits.de \
    --to=mista.tapas@gmx.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jackit-devel@lists.sourceforge.net \
    --cc=mingo@elte.hu \
    --cc=paul@linuxaudiosystems.com \
    --cc=rlrevell@joe-job.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.