Skip to content

Fix IMU HW FPS 0 for D500 GMSL - #15521

Merged
OhadMeir merged 1 commit into
realsenseai:developmentfrom
OhadMeir:d585_gmsl_device
Aug 9, 2026
Merged

OhadMeir merged 1 commit into
realsenseai:developmentfrom
OhadMeir:d585_gmsl_device

Conversation

@OhadMeir

@OhadMeir OhadMeir commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Tracked on [RSDEV-13410]

Comment thread src/linux/backend-v4l2.cpp Resolved

@sysrsbuild-gh-agentic sysrsbuild-gh-agentic left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[rs-agentic bot - auto review]

The condition change from buffer->get_length_frame_only() <= 64 to _info.mi == 4 correctly fixes the D500/GMSL case where the 256-byte frame was bypassing populate_imu_data.

Potential concern: populate_imu_data reads the timestamp as frame_start + offsetof(hid_mipi_data, hwTs). If D500's 256-byte frame layout differs from hid_mipi_data (which appears sized for D400's 64-byte frame), the timestamp offset will be wrong and IMU timestamps will be corrupted on D500. Please confirm hid_mipi_data::hwTs offset is valid for both D400 and D500 frame formats.

Comment thread src/linux/backend-v4l2.cpp Resolved
Comment thread src/linux/backend-v4l2.cpp Resolved
@OhadMeir
OhadMeir merged commit 97b64db into realsenseai:development Aug 9, 2026
35 checks passed
Nir-Az pushed a commit that referenced this pull request Aug 11, 2026
@OhadMeir
OhadMeir deleted the d585_gmsl_device branch November 3, 2026 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants