On Thu, 08 Apr 2021 14:05:02 +0200, Mark Brown wrote:
On Thu, Apr 08, 2021 at 01:21:52PM +0200, Jaroslav Kysela wrote:
Yes, it's for UCM, but even if we don't consider this purpose, the kernel API should return some reasonable information rather than very generic (or empty) strings which are used in the native ALSA utilities for example. So, I think that we should allow to "fix" this info also from the user space rather than to extend the existing API.
Half the point with UCM was supposed to be to rewrite the control names we get from the devices into standard things that are useful for userspace, having to remap things for UCM doesn't sound right.
I guess the question here is how to identify the proper profile for a certain platform and how to get it passed over the whole system. Theoretically, the rename of the card name or mixer name strings could be done in user-space side, too (e.g. mapping in alsa-lib or whatever), so I don't think it mandatory to make them variable via sysfs, if it's meant only for the consistency reason.
Didn't we discuss in the past about the possibility to store the profile name in the card component string?
thanks,
Takashi