From: Takashi Iwai <tiwai@suse.de>
To: brian-welch@cox.net
Cc: alsa-devel@alsa-project.org
Subject: Re: Monitoring ALSA's write pointer (appl_ptr)?
Date: Tue, 04 Nov 2008 17:33:42 +0100 [thread overview]
Message-ID: <s5hprlbqwm1.wl%tiwai@suse.de> (raw)
In-Reply-To: <20081103234028.PAVUM.84220.imail@fed1rmwml28>
At Mon, 3 Nov 2008 23:40:28 -0500,
<brian-welch@cox.net> wrote:
>
> Hello List,
>
> My first post, so excuse any ignorance.
>
> Is there a definitive/safe way to monitor ALSA's write pointer in the
> dma_area? It seems like the ack callback and the appl_ptr is the
> correct way, but I was told by another developer that appl_ptr doesn't
> work in all cases.
>
> As a future optimization for my hardware, I may want to tell ALSA to use
> a specific area of physical memory for it's dma_area, what is the best
> way to do that?
A good question. The ack callback is called only when the explicit
read/write method is used. When mmap access is used, it won't be
called.
One hack would be to check appl_ptr in the pointer callback. This
callback is called in snd_pcm_hwsync(), too. So, if you watch the
appl_ptr change as frequently as possible, it'd be a good place for
that.
Takashi
next parent reply other threads:[~2008-11-04 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081103234028.PAVUM.84220.imail@fed1rmwml28>
2008-11-04 16:33 ` Takashi Iwai [this message]
2008-11-05 3:10 ` Monitoring ALSA's write pointer (appl_ptr)? Brian Welch
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=s5hprlbqwm1.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=brian-welch@cox.net \
/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.