On Thu, 2017-06-15 at 11:01 +0100, Mark Brown wrote:
On Wed, Jun 14, 2017 at 12:28:55PM +0100, Liam Girdwood wrote:
On Fri, 2017-06-09 at 18:53 +0100, Mark Brown wrote:
I'm still a bit unclear about how a pipeline and effect are different from an ASoC point of view - it matters on the DSP but from the kernel's point of view a pipeline just an effect that happens to have a more complicated implementation on the DSP?
Yes, that's true, some of the objects will most likely be treated the same by the kernel core but for the DSP and driver they will different. i.e. they create different objects with different topology private data (using the widget ID to differentiate).
Shouldn't that just be handled in the driver though? Nothing outside the driver cares. We're going to need to differentiate between different effects and pipelines in the driver anyway.
It can be, just a little more code in the driver that's all. I'll remove the pipeline widget and resend.
Thanks
Liam