From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Subject: Re: Device creation order
Date: Fri, 3 Apr 2009 13:58:26 +0200 [thread overview]
Message-ID: <20090403115826.GE15646@tango.0pointer.de> (raw)
In-Reply-To: <alpine.LNX.2.00.0904030945380.17368@eeebox2.perex-int.cz>
On Fri, 03.04.09 09:50, Jaroslav Kysela (perex@perex.cz) wrote:
> >> - dynamic device creation at runtime - for example we have an
> >> experimental HDA driver configuration code which might change
> >> the arrangement of PCM devices on request from the user space
> >>
> >> I would suggest to wait awhile with some small timeout (0.5 sec?) for all
> >> devices to get the usual static arrangement working and handle extra
> >> dynamic cases, too.
> >
> > The current implementation of the ALSA framework guarantees that the
> > control device file is that latest one to be created for all the devices
> > created at initialization. Any devices created later depend on some
> > userspace action, so a small timeout won't help in this case.
>
> The timeout might help to let alsactl utility to initialize the
> soundcard's mixer. But I agree that alsactl should send a HAL message that
> initial setting was done instead.
This is not an issue AFAICS. udev will run alsactl and only *after* that
finished forward the device creation events to HAL and then PA.
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:[~2009-04-03 11:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 1:54 Device creation order Lennart Poettering
2009-04-03 7:12 ` Jaroslav Kysela
2009-04-03 7:20 ` Daniel Mack
2009-04-03 7:31 ` Jaroslav Kysela
2009-04-03 7:40 ` Daniel Mack
2009-04-03 10:34 ` Colin Guthrie
2009-04-03 11:51 ` Lennart Poettering
2009-04-03 11:43 ` Lennart Poettering
2009-04-03 7:38 ` Clemens Ladisch
2009-04-03 7:50 ` Jaroslav Kysela
2009-04-03 11:58 ` Lennart Poettering [this message]
2009-04-03 11:56 ` Lennart Poettering
2009-04-05 13:16 ` Wu Fengguang
2009-04-05 14:40 ` Lennart Poettering
2009-04-05 20:29 ` Mark Brown
2009-04-03 11:42 ` 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=20090403115826.GE15646@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.