On Wed, Nov 20, 2019 at 11:04:38AM +0100, Jaroslav Kysela wrote:
I would like to discuss the way we use DMI information for the board identification in ASoC for the user space (long card name). It's a bit redundant information, because DMI is already exposed through /sys/class/dmi/id/ to the user space nowadays.
My idea is to add 'DMI:sysfs' ctl info component string for the appropriate ASoC driver to detect the existence of this dmi interface. Then I can add the sysfs support to the ucm2 conditions.
I'm not clear what adding the component string does here - is the intention just to say that the card is built in to the machine and hence DMI can be used? If that is the case something more generic that'd also work with other firmware interfaces might be good.