From: Lars-Peter Clausen <lars@metafoo.de>
To: Jeremy McDermond <mcdermj@xenotropic.com>, alsa-devel@alsa-project.org
Subject: Re: ASoC: Machine Driver Interaction with Codec Drivers
Date: Wed, 8 Jun 2016 21:14:01 +0200 [thread overview]
Message-ID: <57586E79.4010309@metafoo.de> (raw)
In-Reply-To: <0BE0E679-A120-4330-8291-315750457145@xenotropic.com>
Hi,
No this is currently not really supported. There were some ideas for this a
long long time ago, but it never got implemented. And today basically
everybody takes care of hiding the controls from userspace.
That does not mean it does not make sense to have such a feature, but it
needs somebody with a motivation to implement it.
- Lars
On 06/08/2016 05:13 AM, Jeremy McDermond wrote:
> I apologize in advance for the probably idiotic question.
>
> I’m working with writing a machine driver for our product and dealing with some potential user interface issues surrounding the number of controls being presented by the codec driver in the mixer.
>
> Is there a way to “hard-wire” kcontrols in the codec from the machine driver and hide them in the mixer? For example, our hardware doesn’t wire the IN2_L and IN2_R pins to anywhere, so the codec controls that determine their connections into the input mixer do nothing on our hardware and I’d like to hide them from the user in the mixer.
>
> Am I missing something or is there just no way to get there from here?
>
> --
> Jeremy McDermond (NH6Z)
> Xenotropic Systems
> mcdermj@xenotropic.com
>
>
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-06-08 19:14 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 [this message]
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
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=57586E79.4010309@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).