From: Clemens Ladisch <clemens@ladisch.de>
To: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
Cc: Patrick Lai <plai@codeaurora.org>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Handle large period size end-of-stream situation
Date: Thu, 04 Apr 2013 11:27:27 +0200 [thread overview]
Message-ID: <515D477F.9010406@ladisch.de> (raw)
In-Reply-To: <515D1122.9020502@gmail.com>
Gabriel M. Beddingfield wrote:
> 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.
But that happens only when ALSA actually reads the hardware pointer.
The application could ask for the pointer position for some reason, but
when it is blocked, only the end-of-period interrupt will cause that.
Regards,
Clemens
next prev parent reply other threads:[~2013-04-04 9:27 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
2013-04-04 9:27 ` Clemens Ladisch [this message]
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=515D477F.9010406@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=gabrbedd@gmail.com \
--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.