On Fri, 2019-08-02 at 21:01 +0200, Jaroslav Kysela wrote:
> > How would we get topology or FW version from the above
> > identification ?
>
> It was just an example. We can compose the UCM filename from any
> other
> additional information passed from the kernel. Example component
> strings for
> USB and legacy HDA:
>
>
> Mixer name : 'USB Mixer'
> Components : 'USB0bda:58fe'
>
> Mixer name : 'Realtek ALC298'
> Components : 'HDA:10ec0298,17aa222e,00100103'
>
> So we should consider what to export for SOF. Perhaps string like:
>
> 'SOFP01234567:45670123,1:1:0-6cc8d,???TPLGVER???,3:7:0'
> 'SOFP{PCIID}:{PCISUBSYS},FW-VER,TPLG-VER,TPLG-ABI-VER'
>
> It's just a proposal for the discussion.
Ok, we will probably need TPLG-NAME in here so that we load the correct
UCM based on TPLG NAME + HW.
>
> By the way:
>
>
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-May/149409.html
>
> The component string extensions should be also considered for other
> Intel SOC
> drivers. It seems that the long_name is misused as the UCM
> configuration
> selector for other drivers like bytcr_rt5651.c etc. The long_name for
> the
> soundcard like 'bytcht-es8316-mono-spk-in2-mic' is not really fancy.
> This
> string is used in GUI.
Sorry, do you mean it would be better to include some more encoding
into the name to make them more unique and so that UI tools and users
can better understand the UCM file features without reading the UCM
file source ?
Thanks
Liam
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
