From: Lennart Poettering <mznyfn@0pointer.de>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Disabling buffer fill level preprocessing by ALSA
Date: Mon, 31 Dec 2007 18:12:27 +0100 [thread overview]
Message-ID: <20071231171226.GA17953@tango.0pointer.de> (raw)
Hi!
In PulseAudio I want to schedule on my own when I need to write audio
data into the device and when not. To achieve that I want to be
notified via poll() whenever a period boundary is passed (i.e. when an
IRQ happens), but only then. That's different from the usual mode
where you are notified via poll() whether there is space in the
playback buffer that needs to be filled up.
On OSS the mmap() mode enables a mode like I described above. After
enabling mmap() the application can decide by itself what it considers
full and what empty in the dma buffer, and use GETOPTR to query the
playback position. poll() on the OSS fd will directly reflect the
sound card IRQs and is not influenced if you ever wrote data to device
or not.
I assume that I can enable a mode like that with one of the SW
params. But quite frankly the docs for it are not enlighening at all.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next reply other threads:[~2007-12-31 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 17:12 Lennart Poettering [this message]
2008-01-07 11:07 ` Disabling buffer fill level preprocessing by ALSA Takashi Iwai
2008-01-07 16:07 ` Lennart Poettering
2008-01-07 18:33 ` Jaroslav Kysela
2008-01-07 22:38 ` Lennart Poettering
2008-01-08 8:00 ` Jaroslav Kysela
2008-01-12 18:06 ` Lennart Poettering
2008-01-07 18:55 ` James Courtier-Dutton
2008-01-07 20:21 ` Lennart Poettering
2008-01-07 22:34 ` James Courtier-Dutton
2008-01-08 0:03 ` Lennart Poettering
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=20071231171226.GA17953@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.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.