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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason why it ended up as dev_warn() + dev_warn_once() is to make sure it shows up in the logs and 'annoy' users that they will file a bug so the CPC value is fixed. Initially I had dev_dbg() as well.
Do we need to print it every time a stream starts? Would a dev_dbg_once() can suffice? Well, it is dev_dbg(), so only developers going to see it, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the original intent still has merit. It's just we need to scale back on the "annoy dose" given the fixes come via quarterly SOF releases (plus adoption to upstream). You can add or modify a tplg at any time, but you can't get rid of the warnings without a new (typically signed) image.