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

[Backport v3.7-branch] sensor: shell: Allow individual axis data to be processed #83723

Merged
merged 4 commits into from
Jan 23, 2025

Conversation

zephyrbot
Copy link
Collaborator

@zephyrbot zephyrbot commented Jan 9, 2025

Backport 1e64d7b~4..1e64d7b from #83474.

Fixes #72840

ubieda added 4 commits January 9, 2025 07:21
For the supported channels, instead of just allowing 3-axis data being
printed out, allow individual channels to be processed (e.g: accel_x,
gyro_y, etc).

Signed-off-by: Luis Ubieda <[email protected]>
(cherry picked from commit 36dfea1)
Instead of assuming that an individual axis must contain all
data-values. Additionally, for determining that there's XYZ data, all
three channels must be present in the header.

Signed-off-by: Luis Ubieda <[email protected]>
(cherry picked from commit 5a1dfc8)
Since now they're treated as q31 values when individually queried, as
opposed to lump them in a triplet.

Signed-off-by: Luis Ubieda <[email protected]>
(cherry picked from commit 19a4261)
Loop through all of the channels and make sure that each
channel has an output.

Changes in patch originally present in #72972.

Signed-off-by: Yong Cong Sin <[email protected]>
Signed-off-by: Luis Ubieda <[email protected]>
(cherry picked from commit 1e64d7b)
@nashif nashif merged commit 2aee9e3 into v3.7-branch Jan 23, 2025
28 of 29 checks passed
@nashif nashif deleted the backport-83474-to-v3.7-branch branch January 23, 2025 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Samples Samples area: Sensors Sensors Backport Backport PR and backport failure issues
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants