From: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Handle large period size end-of-stream situation
Date: Wed, 03 Apr 2013 22:35:30 -0700 [thread overview]
Message-ID: <515D1122.9020502@gmail.com> (raw)
In-Reply-To: <515C459A.5070209@codeaurora.org>
On 04/03/2013 08:07 AM, Patrick Lai wrote:
> I am dealing with a use case requiring passing large buffer down to the
> DSP. Application in the user-space passes PCM through mmap interface.
> Per my understanding, ALSA is designed to work with DMA. Data is
> transferred in chunk equal to period size. At the end of playback,
> there may not be enough audio data left in the music stream to fill
> entire period. If remaining audio data only takes up very small chunk
> of period, playback takes longer to stop. Given that period size I have
> to deal with is quite large, this problem is observed easily. If my
> understanding is correct, what is the standard/recommended way of
> handling end of stream case?
In the typical end-of-stream case, you simply write the data that you
have. When the hw pointer catches up to the application pointer, you
get an XRUN and the stream stops immediately. There's no requirement
that streams have to stop on period boundaries.
-gabriel
next prev parent reply other threads:[~2013-04-04 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 15:07 Handle large period size end-of-stream situation Patrick Lai
2013-04-03 16:49 ` Clemens Ladisch
2013-04-03 22:22 ` Patrick Lai
2013-04-04 5:35 ` Gabriel M. Beddingfield [this message]
2013-04-04 9:27 ` Clemens Ladisch
2013-04-04 15:09 ` Gabriel M. Beddingfield
2013-04-04 17:08 ` Clemens Ladisch
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=515D1122.9020502@gmail.com \
--to=gabrbedd@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=plai@codeaurora.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 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.