[BUG] Zephyr ignores the topology setting for pipeline scheduling period

[ranj063]

Describe the bug
Pipeline tasks are always scheduled every ms irrespective of what the topology requests.

To Reproduce
Use #5958 for setting the pipeline period in topology

Reproduction Rate
100%

Expected behavior
Pipelines must be scheduled based on the period set in topology

Impact
We cannot enable multi-stream feature with pipelines with variable period sizes

Environment

1. Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
   • Kernel: topic/sof-dev
   • SOF: Use SOF PR: topology: sof-cavs-nocodec: Change the scheduling period for the deep… #5958
2. Name of the topology file
   • Topology: sof-tgl-nocodec.tplg with PR: topology: sof-cavs-nocodec: Change the scheduling period for the deep… #5958
3. Name of the platform(s) on which the bug is observed.
   • Platform: TGL, ADL

[ranj063]

@lyakh @kv2019i @lgirdwood FYI

[kv2019i]

I don't think this blocks larger period multiple streams -> #5958 (comment)
Still a missing bit in the scheduler.

[hongshui3000]

I think this PR should also be related to this issue:#5912

[lgirdwood]

@lyakh can you take care of this ?

[plbossart]

Is this issue still relevant @lyakh @ranj063 ? Or do we need to wait for IPC4 + DP processing to be available before the deep-buffer is used?

[ranj063]

This issue is only relevant with IPC3+zephyr+topology1. Not sure if this will ever be fixed though

[lyakh]

This issue is only relevant with IPC3+zephyr+topology1. Not sure if this will ever be fixed though

@ranj063 why is this irrelevant for IPC4? IPC4 doesn't provide a scheduling period?

[ranj063]

@ranj063 why is this irrelevant for IPC4? IPC4 doesn't provide a scheduling period?

@lyakh the scheduling period is relevant of course, its just not set in topology as we do with IPC3+topology1. Im not sure how this should be done for IPC4

[lgirdwood]

@mwasko how is LL scheduling period configured via IPC4 ?