On Sat, 12 May 2018 23:21:58 +0200, Pierre-Louis Bossart wrote: > > >> > >> splitting platform and codec sides is a good idea (and something > >> that was done by removing all platform mixer settings from the HiFi > >> files) > >> > >> the problem remains that we have all these cdev strings that are > >> hard-codec with a card name. Same when the match happens based on a > >> DMI string, how would I know which of the platform settings to > >> apply without querying what the platform driver is? > > > > Well the DMI string would uniquely identify a certain model device, > > when we write the UCM file we should know what the platform + codec > > for that device is and we can simply hardcode them, like in > > my example above. > > > > But maybe I'm misunderstanding you? > > For the same DMI device, you could either enable the existing > intel/sst or SOF drivers. How would we handle UCM configs then? The > DMI name would need to be augmented with a prefix, or we use > *something* to add the references to SOF in the platform include and > ALSA device string. You've already added the flavor suffix to snd_soc_set_dmi_name(), so they'll be unique, no? Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
