Conversation
When the firmware reports a capture sync frame drop (INSYS_MSG_ERR_GROUP_CAPTURE / INSYS_MSG_ERR_CAPTURE_SYNC_FRAME_DROP), the driver currently logs the event via dev_dbg(). Because dev_dbg() is compiled out unless CONFIG_DYNAMIC_DEBUG or DEBUG is enabled, real frame drops silently disappear from dmesg on production builds, making capture pipeline issues hard to diagnose from field logs. Promote the three FRAME DROP dev_dbg() calls to dev_warn_ratelimited() so that drops are always surfaced in dmesg while preventing log floods when many frames are dropped in a burst across pins or streams. Signed-off-by: Sodhi, Vunny <vunny.sodhi@intel.com>
This branch has not been deployed
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
1 participant
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.
When the firmware reports a capture sync frame drop (INSYS_MSG_ERR_GROUP_CAPTURE / INSYS_MSG_ERR_CAPTURE_SYNC_FRAME_DROP), the driver currently logs the event via dev_dbg(). Because dev_dbg() is compiled out unless CONFIG_DYNAMIC_DEBUG or DEBUG is enabled, real frame drops silently disappear from dmesg on production builds, making capture pipeline issues hard to diagnose from field logs.
Promote the three FRAME DROP dev_dbg() calls to dev_warn_ratelimited() so that drops are always surfaced in dmesg while preventing log floods when many frames are dropped in a burst across pins or streams.