From: Lennart Poettering <mznyfn@0pointer.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Disabling buffer fill level preprocessing by ALSA
Date: Sat, 12 Jan 2008 19:06:31 +0100 [thread overview]
Message-ID: <20080112180631.GA5994@tango.0pointer.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0801080833090.22730@tm8103.perex-int.cz>
On Tue, 08.01.08 09:00, Jaroslav Kysela (perex@perex.cz) wrote:
> > So, depending on what clients are connected, we dynamically change the
> > wakeups. Now, on ALSA (and with a lot of sound hw, as I understood
> > Takashi) you cannot reconfigure the period sizes dynamically without
> > interruptions of audio output. That's why I want to disable the whole
> > period/buffer fill level management of ALSA, and do all myself with
> > system timers, which I thankfully now can due to the advent of
> > hrtimers (at least on Linux/x86). System timers nowadays are a lot
> > more flexibe than the PCM timer, because they can be reconfigured all
> > the time without any drawbacks. They are not dependant on period sizes
> > or other stuff which may only be reconfigured by resetting the audio
> > devices. The only drawback is that we need to determinine how the
> > sound card clock and the system clock deviate.
> >
> > Does that make sense to you?
>
> Yes, but I don't see any problem to change avail_min dynamically
> (sw_params can be changed at any time), so each interrupt can be catched
> via poll(). But I really think that one timing source (system timers) is
> enough.
OK. I wasn't really aware that you could change sw params
dynamically. I will do this now. This should be sufficient for my needs.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2008-01-12 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 17:12 Disabling buffer fill level preprocessing by ALSA Lennart Poettering
2008-01-07 11:07 ` 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 [this message]
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=20080112180631.GA5994@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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.