Reduce ST QSPI/OSPI trace verbosity to debug #13932
Merged
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.
Summary of changes
Replaces: #13804 (GitHub doesn't allow renaming a branch of an existing PR)
When mbed-trace is enabled, we may get traces from multiple software components. The chance that one needs to debug QSPI/OSPI is relatively low (compared to their own application/libraries), and those traces can significantly slow down QSPI/OSPI operations. Thus this PR reduces their verbosities from info to debug.
If a user wants to mute traces from those drivers completely, they can filter out specific trace groups in their application, e.g.
Impact of changes
Traces from ST's QSPI/OSPI will be printed only if the trace level is set to debug.
Migration actions required
None.
Documentation
None.
Pull request type
Test results
Reviewers
@evedon @ARMmbed/team-st-mcd