From: Lars-Peter Clausen <lars@metafoo.de>
To: Jeremy McDermond <mcdermj@xenotropic.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC: Machine Driver Interaction with Codec Drivers
Date: Tue, 14 Jun 2016 10:35:01 +0200 [thread overview]
Message-ID: <575FC1B5.6030106@metafoo.de> (raw)
In-Reply-To: <51C7B429-73B0-4CE1-A5D8-8BC2586E558C@xenotropic.com>
On 06/13/2016 11:37 PM, Jeremy McDermond wrote:
> Thanks to everyone for their responses on this. I’m glad I wasn’t missing
> anything stupid.
>
> Lars-Peter Clausen <lars@metafoo.de> wrote:
>
>> And today basically
>> everybody takes care of hiding the controls from userspace.
>
> What are people’s strategies for doing this from userspace? I’ve ingested
> all the docs I could about .asoundrc but wasn’t seeing anything obvious
> where I could hard wire controls. I could populate alsa.state, but that’s a
> really ugly solution.
There are different solutions used by different projects.
Some just hardcode the list of exposed controls in their sound daemon
(although that's not something I'd recommend).
There is ALSA UCM
(http://www.alsa-project.org/main/index.php/Use_Case_Manager
http://www.slimlogic.co.uk/2009/02/alsa-use-case-manager/) which allows you
to define groups of control settings as profiles and also define which
individual controls to expose.
And Android has something similar to UCM, but I can't remember the name
right now.
- Lars
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2016-06-14 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 3:13 ASoC: Machine Driver Interaction with Codec Drivers Jeremy McDermond
2016-06-08 19:14 ` Lars-Peter Clausen
2016-06-09 9:49 ` Takashi Iwai
2016-06-09 10:31 ` Lars-Peter Clausen
2016-06-10 4:07 ` Vinod Koul
2016-06-13 21:37 ` Jeremy McDermond
2016-06-14 8:35 ` Lars-Peter Clausen [this message]
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=575FC1B5.6030106@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=mcdermj@xenotropic.com \
/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).