[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2006121325470.3186@eliteleevi.tm.intel.com>
Date: Fri, 12 Jun 2020 13:29:52 +0300 (EEST)
From: Kai Vehmanen <kai.vehmanen@...ux.intel.com>
To: Brent Lu <brent.lu@...el.com>
cc: alsa-devel@...a-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Liam Girdwood <lgirdwood@...il.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Daniel Baluta <daniel.baluta@....com>,
Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Zhu Yingjiang <yingjiang.zhu@...ux.intel.com>,
Keyon Jie <yang.jie@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
sound-open-firmware@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ASoC: SOF: Intel: hda: unsolicited RIRB response
Hi Brent,
On Fri, 12 Jun 2020, Brent Lu wrote:
> Port commit 6d011d5057ff ("ALSA: hda: Clear RIRB status before reading
> WP") from legacy HDA driver to fix the get response timeout issue.
> Current SOF driver does not suffer from this issue because sync write
> is enabled in hda_init. The issue will come back if the sync write is
> disabled for some reason.
better to align the logic, so I'm ok to take this patch to SOF.
Can you fix the summary though:
- ASoC: SOF: Intel: hda: unsolicited RIRB response
+ ASoC: SOF: Intel: hda: Clear RIRB status before reading WP
Br, Kai
Powered by blists - more mailing lists