ipc4: mixin/mixout: Remove redundant source_info stuff

[serhiy-katsyuba-intel]

Mutex protected module_source_info was an old failed attempt to support cross-core connection of mixin and mixout. That functionality was never properly tested as FW did not support cross-core connections there.

For connected mixin and mixout located on same core, that functionality is not needed. For cross-core connection, that functionality creates dead-lock.

[lyakh]

this not only removes source_info from mixin-mixout, but also removes generic module binding and unbinding and moves it to mixin-mixout only. This might be valid, but it's certainly more than what the commit description is saying

[serhiy-katsyuba-intel]

this not only removes source_info from mixin-mixout, but also removes generic module binding and unbinding and moves it to mixin-mixout only. This might be valid, but it's certainly more than what the commit description is saying

No, module_adpter_bind() and unbind() are still there. They are just stripped from the stuff that was only needed for mixin/mixout. Previously that was implemented in mixout_bind() and unbind() and were moved to module_adapter after mixin/mixout was modified to use it. That module_adapter_source_info is (1) not needed at all, (2) does not work: does nothing on single core and creates dead-lock on cross-core.

[lgirdwood]

@serhiy-katsyuba-intel there were also some recent MCPS optimisations for local core 1:1 copying. Can you confirm there is no MCPS impact for this use case. Thanks

[serhiy-katsyuba-intel]

@serhiy-katsyuba-intel there were also some recent MCPS optimisations for local core 1:1 copying. Can you confirm there is no MCPS impact for this use case. Thanks

The PR does not add new code to execution flow, it just removes module_source_info stuff which is not needed. The performance might become a little bit better or at least the same, not worse.

[lgirdwood]

Rerun the actions and Zephyr issues are known and unrelated..