From: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>
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 08:09:42 -0700 [thread overview]
Message-ID: <515D97B6.1080701@gmail.com> (raw)
In-Reply-To: <515D477F.9010406@ladisch.de>
On 04/04/2013 02:27 AM, Clemens Ladisch wrote:
> 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.
I stand corrected. (Thanks also to Peter Ujfalusi for setting me straight.)
So, if the hardware can detect it then the hardware needs to signal an
interrupt for the XRUN.
Another option... from userspace you can call SYNC_PTR (e.g.
pcm_get_htimestamp() in tinyalsa) to update the hw and application
pointers, then inspect them to detect when all the data is transferred.
When you see all is played, immediately stop the stream. Again, this
presumes that the "hw" side is able to query the state of the pointer.
-gabriel
next prev parent reply other threads:[~2013-04-04 15:09 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
2013-04-04 15:09 ` Gabriel M. Beddingfield [this message]
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=515D97B6.1080701@gmail.com \
--to=gabrbedd@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--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.