From: Florian Schmidt <mista.tapas@gmx.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: tapas <tapas@affenbande.org>, Ingo Molnar <mingo@elte.hu>,
Paul Davis <paul@linuxaudiosystems.com>,
Jaroslav Kysela <perex@suse.cz>,
jackit-devel@lists.sourceforge.net,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [Jackit-devel] irq handler top half timestamps
Date: Mon, 20 Dec 2004 00:45:11 +0100 [thread overview]
Message-ID: <20041220004511.579be209@mango.fruits.de> (raw)
In-Reply-To: <1103222119.23735.2.camel@krustophenia.net>
On Thu, 16 Dec 2004 13:35:18 -0500
Lee Revell <rlrevell@joe-job.com> wrote:
> On Thu, 2004-12-16 at 17:33 +0100, tapas wrote:
> > Fons Adriaenssen wrote to me that he tried snd_pcm_get_trigger_tstamp(),
> > but he always got the same value back. Since the docs are rather sparse
> > i want to ask the alsa-devs about exactly how to use the
> > snd_pcm_get_trigger_tstamp() call.
>
> Because trigger_tstamp only gets updated in the trigger callback, when
> the PCM is stopped, started, or paused. I will have to check the code
> to see what you use for the irq timestamp.
Hi,
did you find something? Or does the api not have any provisions for this
yet?
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/
next prev parent reply other threads:[~2004-12-19 23:45 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 ` Re: [Jackit-devel] " Florian Schmidt
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 [this message]
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=20041220004511.579be209@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=perex@suse.cz \
--cc=rlrevell@joe-job.com \
--cc=tapas@affenbande.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