ASoC: SOF: ipc4-topology: Correct the process module's output lookup#5442
Open
ujfalusi wants to merge 2 commits intothesofproject:topic/sof-devfrom
Open
ASoC: SOF: ipc4-topology: Correct the process module's output lookup#5442ujfalusi wants to merge 2 commits intothesofproject:topic/sof-devfrom
ujfalusi wants to merge 2 commits intothesofproject:topic/sof-devfrom
Conversation
This was referenced Jun 3, 2025
lgirdwood
reviewed
Jun 18, 2025
Member
lgirdwood
left a comment
There was a problem hiding this comment.
LGTM, just 1 question for reuse.
| } | ||
|
|
||
| static void | ||
| sof_ipc4_evaluate_params_change(struct sof_ipc4_available_audio_format *available_fmt) |
Member
Collaborator
Author
There was a problem hiding this comment.
I'm not familiar with what the module creation IPC update does, but this is stored at widget creation time and can be used later when we create the messages.
ea4f69e to
791b32e
Compare
Collaborator
Author
|
Changes since v1:
|
bardliao
previously approved these changes
Jun 23, 2025
…t of a module Based on the input and output formats we can evaluate what param might be changed by the module instance. If there is a difference between the input rate/channels/format and the output rate/channels/format it means that the module can change one or multiple of the params. Store this information during init for later use. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
The process module can change different parameters in the audio path and this change has to be properly evaluated and applied. In case of playback we are converting from multiple input formats to a single format (or just passing through without change), the output format lookup must be based on the input format. In case of capture, we are converting from a single input format to a format which is to be passed to the FE, we need to use the input parameters and the FE parameters to be able to find the correct format: for those parameters that are modified by the module instance we need to use the FE parameter while for the rest we use the input parameters. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
791b32e to
796efb2
Compare
Collaborator
Author
|
Changes since v2:
|
bardliao
approved these changes
Oct 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
The process module can change different parameters in the audio path and
this change has to be properly evaluated and applied.
In case of playback we are converting from multiple input formats to a
single format (or just passing through without change), the output format
lookup must be based on the input format.
In case of capture, we are converting from a single input format to a
format which is to be passed to the FE, we need to use the input parameters
and the FE parameters to be able to find the correct format:
for those parameters that are modified by the module instance we need to
use the FE parameter while for the rest we use the input parameters.
Signed-off-by: Peter Ujfalusi peter.ujfalusi@linux.intel.com