diff options
author | David Dillow <dave@thedillows.org> | 2010-06-27 00:13:20 +0200 |
---|---|---|
committer | Jaroslav Kysela <perex@perex.cz> | 2010-06-28 09:42:09 +0200 |
commit | 5daeba34d2aab669aea07abee13d53cd116578fb (patch) | |
tree | 4213fce45c60b6c16160fa9c777aa923ef562172 /block/Kconfig | |
parent | 8fc6d4186e0a60b3755a6b88bf67a3ac3214dcc3 (diff) | |
download | op-kernel-dev-5daeba34d2aab669aea07abee13d53cd116578fb.zip op-kernel-dev-5daeba34d2aab669aea07abee13d53cd116578fb.tar.gz |
ALSA: pcm_lib: avoid timing jitter in snd_pcm_read/write()
When using poll() to wait for the next period -- or avail_min samples --
one gets a consistent delay for each system call that is usually just a
little short of the selected period time. However, When using
snd_pcm_read/write(), one gets a jittery delay that alternates between
less than a millisecond and approximately two period times. This is
caused by snd_pcm_lib_{read,write}1() transferring any available samples
to the user's buffer and adjusting the application pointer prior to
sleeping to the end of the current period. When the next period
interrupt occurs, there is then less than avail_min samples remaining to
be transferred in the period, so we end up sleeping until a second
period occurs.
This is solved by using runtime->twake as the number of samples needed
for a wakeup in addition to selecting the proper wait queue to wake in
snd_pcm_update_state(). This requires twake to be non-zero when used
by snd_pcm_lib_{read,write}1() even if avail_min is zero.
Signed-off-by: Dave Dillow <dave@thedillows.org>
Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Diffstat (limited to 'block/Kconfig')
0 files changed, 0 insertions, 0 deletions