From: Lennart Poettering <mznyfn@0pointer.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Rationale behind snd_pcm_htimestamp()
Date: Wed, 25 Feb 2009 22:42:23 +0100 [thread overview]
Message-ID: <20090225214222.GC27632@tango.0pointer.de> (raw)
In-Reply-To: <s5heixmo8ht.wl%tiwai@suse.de>
On Wed, 25.02.09 16:13, Takashi Iwai (tiwai@suse.de) wrote:
> > Hmm, so I understood you correctly then the API would need changing to
> > get the timestamp, the delay and the avail value that belong together?
>
> Yes, if you stick with snd_pcm_htimetamp(), snd_pcm_avil() and co.
>
> But basically snd_pcm_status() does sync and fetch all status data.
> Shouldn't calling this suffice for your purpose?
Hmm, so snd_pcm_status() does sync? Good to know. I'll then use that.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
prev parent reply other threads:[~2009-02-25 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 2:35 Rationale behind snd_pcm_htimestamp() Lennart Poettering
2009-02-16 16:08 ` Takashi Iwai
2009-02-18 21:51 ` Lennart Poettering
2009-02-25 15:13 ` Takashi Iwai
2009-02-25 21:42 ` Lennart Poettering [this message]
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=20090225214222.GC27632@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@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