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

sof-glk-nocodec: disable pipelines when disabling SSPs #8175

Merged
merged 1 commit into from
Sep 11, 2023

Conversation

marc-hb
Copy link
Collaborator

@marc-hb marc-hb commented Sep 7, 2023

When we added the flags to disable SSP0 and SSP1 on the UP2, we took the shortcut of just removing the PCMs in topology but left the pipelines and widgets in the topology in. While this works in practice to prevent us from testing those SSPs, the right way is to also remove those pipelines also when the SSPs are disabled.

This stops tplgtool2.py from complaining constantly about this inconsistency since thesofproject/sof-test#1079 which made the sof-test verify-tplg-binary.sh fail every time:

tplgtool2.py sof-glk-nocodec.tplg

ERROR: No pcm id=0 for widget=PCM0C
ERROR: No pcm id=1 for widget=PCM1C
ERROR: No pcm id=0 for widget=PCM0P
ERROR: No pcm id=1 for widget=PCM1P
ERROR: tplgtool2.py returned 4

This change affects only sof-apl-nocodec and sof-glk-nocodec.

Copy link
Member

@plbossart plbossart left a comment

Choose a reason for hiding this comment

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

looks ok but @ranj063 needs to review this

@ranj063
Copy link
Collaborator

ranj063 commented Sep 7, 2023

looks ok but @ranj063 needs to review this

approved :). @plbossart this is my patch

@plbossart plbossart marked this pull request as ready for review September 7, 2023 13:15
@plbossart plbossart requested a review from ranj063 as a code owner September 7, 2023 13:15
@marc-hb marc-hb marked this pull request as draft September 8, 2023 13:56
@marc-hb
Copy link
Collaborator Author

marc-hb commented Sep 8, 2023

Wait, we looked at the graph and found a problem. @ranj063 gave me a new patch.

PS: please don't promote others' drafts.

When we added the flags to disable SSP0 and SSP1 on the UP2, we took the
shortcut of just removing the PCMs in topology but left the pipelines
and widgets in the topology in. While this works in practice to prevent
us from testing those SSPs, the right way is to also remove those
pipelines also when the SSPs are disabled.

This stops tplgtool2.py from complaining constantly about this
inconsistency since thesofproject/sof-test#1079
which made the sof-test verify-tplg-binary.sh fail every time:

```
tplgtool2.py sof-glk-nocodec.tplg

ERROR: No pcm id=0 for widget=PCM0C
ERROR: No pcm id=1 for widget=PCM1C
ERROR: No pcm id=0 for widget=PCM0P
ERROR: No pcm id=1 for widget=PCM1P
ERROR: tplgtool2.py returned 4
```

This change affects only sof-apl-nocodec and sof-glk-nocodec.

Signed-off-by: Marc Herbert <[email protected]>
Signed-off-by: Ranjani Sridharan <[email protected]>
@marc-hb marc-hb marked this pull request as ready for review September 8, 2023 22:39
@marc-hb
Copy link
Collaborator Author

marc-hb commented Sep 8, 2023

New version from @ranj063 force-pushed, this time it's ready. See new, smaller graph and test results in stable-v2.2 TEST PR #8173.

This patch has no effect on the main branch, I will cherry-pick -x after merge to stable-v2.2 (sticking to the normal flow)

EDIT: tl;dr: all failures are unrelated, this can be merged.

https://sof-ci.01.org/sofpr/PR8175/build12732/devicetest is all green and the MTL test failures are obviously totally irrelevant.

QB has been out of order for the days but again it's not affected by topologies at all.

I bisected the recent and irrelevant ZRESTRICT warning regression and filed bug

@kv2019i kv2019i merged commit 9ccfbc4 into thesofproject:main Sep 11, 2023
@marc-hb marc-hb deleted the fix-glk-nocodec branch September 11, 2023 15:43
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.

6 participants