From: Mike Frysinger <vapier@gentoo.org>
To: alsa-devel@alsa-project.org
Subject: handling of dmix and non-dmix in the same configuration file
Date: Thu, 21 Feb 2008 18:04:39 -0500 [thread overview]
Message-ID: <200802211804.39684.vapier@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1327 bytes --]
on the Blackfin processor, we have an "almost-but-not-quite" AC97 interface
(called a "SPORT"). the trouble is that we can hook up AC97 codecs, but in
order to properly communicate with codecs, we need to repacketize the
communication between the higher alsa layers and the actual SPORT. great ...
but now we want to support dmix/dsnoop. the overhead for dmix vs non-dmix is
such that we make it optional. if the user does not need software mixing,
they can disable this overhead. this leads to two (incompatible) alsa config
files (in this case, for the AD1980 codec). we're wondering if it's possible
to have the right settings selected on the fly some how during runtime rather
than having to select one file or the other.
the dmix config:
AD1980.pcm.default {
@args [ CARD ]
@args.CARD {
type string
}
type asym
playback.pcm {
type plug
slave.pcm {
@func concat
strings [ "dmix:CARD=" $CARD ]
}
}
capture.pcm {
type plug
slave.pcm {
@func concat
strings [ "dsnoop:CARD=" $CARD ]
}
}
}
the non-dmix config:
AD1980.pcm.default {
type plug
slave {
pcm {
type mmap_emul
slave {
pcm {
type hw
card 0
format S16_LE
rate 48000
channels 2
sync_ptr_ioctl 1
}
}
}
}
}
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2008-02-21 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 23:04 Mike Frysinger [this message]
2008-02-22 13:50 ` handling of dmix and non-dmix in the same configuration file Clemens Ladisch
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=200802211804.39684.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).