On Mon, Aug 17, 2015 at 11:39:59AM +0100, Liam Girdwood wrote:
The intention is that the topology data for BE and codec style links is not to define the link (as this should come from DT or ACPI) but to define the links config/capabilities for a given FW. e.g. we have two different FWs that run BE0 (SSP0) with different number of channels (one is stereo, the other is 4 channel TDM). Currently the link definitions will be hard coded until the ACPI data is ready.
The FE uses the above too for config/capabilities but it can also be defined and created by the topology data (since it's a FW entity).
So this is actually for adding further constraints to the existing physical links, not just for defining new virtual links. That is definitely a reasonable application but it seems like what we should be doing here is adding constraints to a fully defined link rather than just having a dummy link. The link is real and there, it's just that we want to further restrict how it can be used. Something that says "this is a dummy link" definitely feels wrong.