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

[stable-v2.9] west.yml: update Zephyr with backported fixes #8899

Closed

Conversation

kv2019i
Copy link
Collaborator

@kv2019i kv2019i commented Mar 4, 2024

Point Zephyr to https://github.com/thesofproject/zephyr and pull request to bring in set of upstream Zephyr bugfixes.

@kv2019i kv2019i added the DNM Do Not Merge tag label Mar 4, 2024
@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 4, 2024

Test with fixes at thesofproject/zephyr#77

@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 5, 2024

Update Zephyr with backported fixed from Zephyr upstream including
the following patches:

337b518c3311 dai: intel: dmic: demote spurious LOG_ERR in dai_nhlt_get_clock_div()
802baf38426b soc: xtensa: intel_adsp: restore bootctl with per-core state
576924d5f201 drivers: dma: intel-adsp-hda: modify stop dma logic
369241d7bf7d drivers: dma: intel-adsp-hda: add delay to stop host dma

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
@kv2019i kv2019i force-pushed the 202403-sof29-zephyr-backports branch from dfbba24 to 6dc2005 Compare March 5, 2024 18:26
@kv2019i kv2019i changed the title [stable-v2.9][DNM] west.yml: update Zephyr with backported fixes [stable-v2.9] west.yml: update Zephyr with backported fixes Mar 5, 2024
@kv2019i kv2019i removed the DNM Do Not Merge tag label Mar 5, 2024
@kv2019i kv2019i marked this pull request as ready for review March 5, 2024 18:27
@marc-hb
Copy link
Collaborator

marc-hb commented Mar 5, 2024

Did you really mean to target the main branch? The PR title says "[stable-v2.9]"

@kv2019i
Copy link
Collaborator Author

kv2019i commented Mar 6, 2024

@marc-hb wrote:

Did you really mean to target the main branch? The PR title says "[stable-v2.9]"

No, definitely not, thanks for noticing, closing this.

@kv2019i kv2019i closed this Mar 6, 2024
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.

2 participants