Add object array abstraction to ipc4_module_init_ext_init and use it to pass stack and heap size for DP modules#10064
Merged
lgirdwood merged 6 commits intothesofproject:mainfrom Jul 7, 2025
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extend the existing struct ipc4_module_init_ext_init payload with an abstract object array, and use the object array to pass DP module memory configuration e.g. stack and heap size. The PR contains decoding of the payload and extraction of stack and heap size properties, but no actual functionality for applying the memory configuration for the module. The decoding also lacks the decoding of rtos_domain and gna_used flags and payload.