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? More crazy ideas welcome. Takashi > > - 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@xxxxxxxxxxxxxx > > > > > > > > > > _______________________________________________ > > Alsa-devel mailing list > > Alsa-devel@xxxxxxxxxxxxxxxx > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > > > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@xxxxxxxxxxxxxxxx > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
