All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Philip Spencer <pspencer@fields.utoronto.ca>
Cc: alsa-devel@alsa-project.org,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: [PATCH] Wrong latency in pulseaudio plugin breaks Adobe Flash Player
Date: Thu, 23 Feb 2012 10:01:09 +0100	[thread overview]
Message-ID: <4F460055.2010508@ladisch.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1202222059170.29627@fields.fields.utoronto.ca>

Philip Spencer wrote:
>     3. What should happen?
>
>            (a) The call returns immediately, since there's lots of room
>                in the buffer.
>
>            (b) The call returns after one I/O period's worth of data has
>                been drained from the buffer.

(a)

> If the correct answer is (a) (ALSA's current behaviour), then is there
> any mechanism for an app to achieve (b) -- get woken up after one I/O
> period's worth of data have been drained (other than just doing some
> infinite loop of sleeping then checking snd_pcm_avail periodically)?

Adjust avail_min (but note that wakeups happen only at period
boundaries).


Regards,
Clemens

  parent reply	other threads:[~2012-02-23  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 15:48 [PATCH] Wrong latency in pulseaudio plugin breaks Adobe Flash Player Philip Spencer
2012-02-17  1:24 ` David Henningsson
2012-02-17  4:25   ` Philip Spencer
2012-02-17  9:12     ` David Henningsson
2012-02-17 19:36       ` Philip Spencer
2012-02-17 21:15         ` Philip Spencer
2012-02-20 11:45         ` David Henningsson
2012-02-23  2:50           ` Philip Spencer
2012-02-23  8:24             ` David Henningsson
2012-02-23  9:01             ` Clemens Ladisch [this message]
2012-02-23 15:18               ` Philip Spencer

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=4F460055.2010508@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=pspencer@fields.utoronto.ca \
    /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.