Skip to content

topology2: Update memory requirements to what the our current FW expects#10903

Open
jsarha wants to merge 3 commits into
thesofproject:mainfrom
jsarha:topology_memory_data_update
Open

topology2: Update memory requirements to what the our current FW expects#10903
jsarha wants to merge 3 commits into
thesofproject:mainfrom
jsarha:topology_memory_data_update

Conversation

@jsarha

@jsarha jsarha commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

These updates should go in before we make a SOF release since, #10842 is now in.

Jyri Sarha added 3 commits June 12, 2026 17:34
The widget specific stack requirement works in such a way that all
components in a pipeline have their stack requirements, and the
pipeline stack size will be the highest of those values.

I am not sure if this is actually the best method. I am not sure what
factors affect the required stack size for a pipeline, but for now
this will have to do.

So 4k is not enough for all pipelines, and these generic numbers are
here to guarantee that everything works until we have fine tuned
values for all the modules. So increase the number to 8k to guarantee
functionality.

Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com>
…butes

Remove tokens lifetime_heap_bytes_requirement and shared_bytes_requirement
and turn interim_bytes_requirement back into heap_bytes_requirement.

These new types are not after all needed. The vregions code can handle
the division between lifetime linear allocs and traditional interim
heap autonomously. And shared memory does not need to be separately
configured, vregion_alloc_coherent_align() can allocate shared memory
from the same heap.

Fixes: 83390bd ("topology2: Add lifetime and shared -bytes_requirement widget attributes")

Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com>
Fine tune SRC DP memory requirements to values that should satisfy all
use-cases, without using too much memory.

Signed-off-by: Jyri Sarha <jyri.sarha@linux.intel.com>
Copilot AI review requested due to automatic review settings June 12, 2026 14:41
@jsarha jsarha requested a review from ranj063 as a code owner June 12, 2026 14:41

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates topology2 memory requirement tokens/config to match current SOF firmware expectations ahead of the next SOF release (per #10842).

Changes:

  • Replaces interim/lifetime/shared heap requirement attributes with a single heap_bytes_requirement.
  • Updates vendor token mappings to expose only heap_bytes_requirement.
  • Adjusts SRC domain memory values in cavs-nocodec.conf (stack/heap/domain_id).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File Description
tools/topology/topology2/include/components/widget-common.conf Consolidates heap requirement attributes and updates default heap requirement value.
tools/topology/topology2/include/common/tokens.conf Updates vendor token list to use heap_bytes_requirement instead of 3 separate heap tokens.
tools/topology/topology2/cavs-nocodec.conf Updates DP SRC domain memory requirements (stack/heap) and domain id.

Comment on lines 28 to 32
scheduler_domain 418
domain_id 419
stack_bytes_requirement 420
interim_heap_bytes_requirement 421
lifetime_heap_bytes_requirement 422
shared_bytes_requirement 423
heap_bytes_requirement 421
}
Comment on lines +701 to +703
domain_id 0
stack_bytes_requirement 2048
heap_bytes_requirement "$[(24 * 1024)]"
Comment on lines +152 to 156
## Heap size requirement in bytes for this component.
DefineAttribute."heap_bytes_requirement" {
# Token set reference name and type
token_ref "comp.word"
}
interim_heap_bytes_requirement 4096
lifetime_heap_bytes_requirement 16384
shared_bytes_requirement 4096 No newline at end of file
heap_bytes_requirement 24576
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants