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

ipc4: dai: update wallclock for position update #5568

Merged
merged 1 commit into from Mar 21, 2022

Conversation

RanderWang
Copy link
Collaborator

The original code was copied from ipc3 path but the wallclock usage
is different. In ipc4 path fw needs update it for each position update.

Signed-off-by: Rander Wang rander.wang@intel.com

The original code was copied from ipc3 path but the wallclock usage
is different. In ipc4 path fw needs update it for each position update.

Signed-off-by: Rander Wang <rander.wang@intel.com>
@@ -308,6 +308,8 @@ void dai_dma_position_update(struct comp_dev *dev)
status.ipc_posn_data = llp_data;
dma_status(dd->chan, &status, dev->direction);

platform_dai_wallclock(dev, &dd->wallclock);

Copy link
Member

Choose a reason for hiding this comment

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

@RanderWang @mmaka1 can you confirm when this dma_position_update happens? it's my understanding that it must happen on a 1ms basis, not just when there a DMA event.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@plbossart yes, it is called by each dai_copy which is scheduled 1ms basis

Copy link
Member

@lgirdwood lgirdwood left a comment

Choose a reason for hiding this comment

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

@lgirdwood lgirdwood merged commit 9e15ef8 into thesofproject:main Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants