sensors: lsm6dsv16x: fix get_frame_count API #82438
Merged
Conversation
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
zephyrbot
requested review from
MaureenHelm,
jeppenodgaard,
teburd,
tristan-google,
ubieda and
yperess
The get_frame_count() API must return the number of frames in FIFO for a given channel type, and not the total number of generic FIFO frames. This API may be also re-used in the decoder routine when the timestamp baseline is adjusted. Signed-off-by: Armando Visconti <[email protected]>
avisconti
force-pushed
the
lsm6dsv16x-change-get-frame-count
branch
from
777d230 to
8ce277d
Compare
XenuIsWatching
approved these changes
Jan 1, 2025
teburd
approved these changes
Jan 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 get_frame_count() API must return the number of frames in FIFO for a given channel type, and not the total number of generic FIFO frames. This API may be also re-used in the decoder routine when the timestamp baseline is adjusted.
Taken from #82342 and submitted as a separate PR.