Repository navigation
hda-dma: change preload from blocking to repeating - #1546
Merged
lgirdwood merged 1 commit intoJun 11, 2019
Merged
Conversation
Changes preload flow for host component using HDA-DMA. Instead of waiting for DMA status for a limited amount of time, it's better to just reschedule the pipeline and check again. At least this time if the status won't be set, we will know it's rather HW issue than too small delay. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
tlauda
requested review from
lbetlej,
lgirdwood,
mmaka1 and
plbossart
as code owners
June 11, 2019 13:12
jajanusz
approved these changes
Jun 11, 2019
lgirdwood
approved these changes
Jun 11, 2019
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
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.
Changes preload flow for host component using HDA-DMA.
Instead of waiting for DMA status for a limited amount
of time, it's better to just reschedule the pipeline
and check again. At least this time if the status
won't be set, we will know it's rather HW issue than
too small delay.
Signed-off-by: Tomasz Lauda tomasz.lauda@linux.intel.com