On 2022-03-07 5:39 PM, Ranjani Sridharan wrote:
On Fri, 2022-03-04 at 18:21 +0100, Cezary Rojewski wrote:
Are there any rules for unbinding? For example if you have 2
modules
connected to a mixer? Can you unbind the module belonging to the
host
pipeline that is getting stopped while the mixer is still active?
Here we have just a delegate. All the rules are defined and enforced
by
the firmware.
I'm not following this, Czarek. If there are rules defined by the FW,
the driver has to follow it isnt it? What I am asking is how and where
do you enforce this in the AVS driver?
How the stream looks is defined by the topology. Code that translates
such patterns into runtime being is not part of this patchset. It's part
of avs_path and its collaterals instead.
How come you dont have a loop here? What if the rec'd data size if
larger than the max size of IP payload?
That's not how LARGE_CONFIG_GET message works. There is no looping
involved or expected by the firmware and so we don't have it here.
So, are you saying that when retrieving data from the FW, the size of
the retrieved data can never exceed max IPC payload size?
Precisely.
Regards,
Czarek
