Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mtl: lnl: Kd topology failure fix #8382

Merged
merged 2 commits into from
Oct 25, 2023

Conversation

jxstelter
Copy link
Contributor

KD topology tests fail on MTL and LNL due to insufficient size of
heap memory. During creation of KD topologies with
4ch audio format, FW fails on memory allocation.
The patch increases HEAPMEM size.

Signed-off-by: Jaroslaw Stelter [email protected]

KD topology tests fail on LNL due to insufficient size of
heap memory. During creation of KD topologies with
4ch audio format, FW fails on memory allocation.
The patch increases HEAPMEM size.

Signed-off-by: Jaroslaw Stelter <[email protected]>
KD topology tests fail on MTL due to insufficient size of
heap memory. During creation of KD topologies with
4ch audio format, FW fails on memory allocation.
The patch increases HEAPMEM size.

Signed-off-by: Jaroslaw Stelter <[email protected]>
@jxstelter jxstelter marked this pull request as ready for review October 24, 2023 12:43
Copy link
Contributor

@marcinszkudlinski marcinszkudlinski left a comment

Choose a reason for hiding this comment

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

as for now looks like we do have enough memory...

Copy link
Member

@lgirdwood lgirdwood left a comment

Choose a reason for hiding this comment

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

@jxstelter @marcinszkudlinski @kv2019i btw, whats the plan to remove this hard coding as I assume Zephyr heap should be able to be set to max SRAM size (and dynamically power on/off memory banks).

@lgirdwood lgirdwood merged commit 338e87f into thesofproject:main Oct 25, 2023
38 checks passed
@jxstelter
Copy link
Contributor Author

@jxstelter @marcinszkudlinski @kv2019i btw, whats the plan to remove this hard coding as I assume Zephyr heap should be able to be set to max SRAM size (and dynamically power on/off memory banks).
I don't think that heap should be set to max SRAM. Large part of memory will be used by loadable libraries and this is not heap allocated space but space mapped from unused SRAM and mapped to particular virtual space. The space is then assigned to module memory domain.

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.

4 participants