On Sat, Feb 20, 2021 at 06:55:06PM +0100, Jaroslav Kysela wrote:
The problem with ASoC tree is that many of those controls are not supposed to be configured/used by the end user, but in UCM or other higher level layer configuration, because they're a part of the hw/driver setup.
I think that we should classify those controls so the standard user space tools can hide them, but it's another problem.
Well, as has been discussed in the past ideally ALSA would have a mechanism for exposing topology information and userspace would have some chance of picking which controls make sense for use on non-trivial hardware. The particular set of controls that it makes sense to adjust from userspace is going to vary depending on the use case, it's not something that can be decided in the kernel.