From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jeremy McDermond <mcdermj@xenotropic.com>,
alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: ASoC: Machine Driver Interaction with Codec Drivers
Date: Fri, 10 Jun 2016 09:37:10 +0530 [thread overview]
Message-ID: <20160610040709.GW16910@localhost> (raw)
In-Reply-To: <s5hinxihetz.wl-tiwai@suse.de>
On Thu, Jun 09, 2016 at 11:49:28AM +0200, Takashi Iwai wrote:
> On Wed, 08 Jun 2016 21:14:01 +0200,
> Lars-Peter Clausen wrote:
> >
> > 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.
>
> The devils live in details. Actually a primary question is in which
> level we should cover it. For example, can we disable DAPM pins from
> the machine driver? This will reduce not only kctls but DAPM paths.
> Or should we mark kctls just as invisible? Or, would it be suitable
> rather to hide such a thing in user-space?
Today codecs give DAPM graph but that is not linked in kctls. If we do that,
then DAPM can hide un-connected graphs!
For SKL DSP modules, we have modelled kctls in DAPM using PGA as we have to
enable/disable modules, so for DSP at least we can do this :)
So simpler might be to add dummy widgets to kctls by drivers and then hide.
Or we can have extended graph which has "extra" graph which show kctls to
graph links.
Thanks
--
~Vinod
next prev parent reply other threads:[~2016-06-10 4:00 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 [this message]
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=20160610040709.GW16910@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=mcdermj@xenotropic.com \
--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 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).