Hi Pierre-Louis, Mark > > Is it possible to *real* fixup in the future, some day ? > > Quite unlikely I am afraid. This is a mismatch between topology and > machine driver, and there are no planned updates of those topologies > (which were never released for upstream use). > > In this case I guess the topology file was taken from a ChromeOS > distribution (based on v4.4 IIRC), so there's really no guarantee that > a fix would ever reach the user without a convoluted set of manual > updates. (snip) > Maybe we could have some sort of boolean flag in the component->driver > definition and explicitly request a backwards-compatible behavior > (e.g. for all SKL/KBL machine drivers) when that driver is known to be > flaky. There's already things like 'fully_routed', maybe we can add > something such as 'disable_route_check'? Hmm... I have no idea, but have no objection about this. Thank you for your help !! Best regards --- Kuninori Morimoto _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
