On Wed, 2019-09-18 at 14:55 +0000, Mark Pearson wrote:

Hi SOF folks,

I've been able to address the issue I was seeing with 5.2.9 kernel and the SOF driver on our whiskeylake based system but would really appreciate a quick review from the experts to confirm that I've not missed anything important or add any extra insight.

The problem was seen on boot - the driver suspends and resumes a couple of times during boot and during the second resume failed to load the firmware (err -110). After that point the driver, and hence the audio, isn't useable.

I backported these commits to address the problem:

https://github.com/thesofproject/linux/commit/bf705eaa7ce07f9c132f8e367fc2fc...

https://github.com/thesofproject/linux/commit/64632de9140e52b72781fefe542314...

https://github.com/thesofproject/linux/commit/7623ae793c28cc0928c5d1292542db...

https://github.com/thesofproject/linux/commit/f5dbba9fee801f4678a50d92c785f7...

https://github.com/thesofproject/linux/commit/bb1ea3b31c28a131a5f5a50dd32519...

We're still doing some testing to get confidence the fix is correct and stable but so far it looks good - everything is working.

Hi Mark, All of the above changes are related to the HDA Link DMA programming changes that were made a few months ago. These changes work only with FW ABI version 3.8+.

I'd also take these as they were part of the original series and a couple of bug fixes later on:

ASoC: SOF: hda: reserve host DMA channel for hostless streams ASoC: SOF: hda: couple host and link DMA during FE hw_free ASoC: SOF: hda: fix link DMA config ASoC: SOF: hda: fix stream id setting

Thanks, Ranjani

Thanks Mark _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware