alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH 1/2] ASoC: SOF: Fix "no reply expected" error during firmware-boot
Date: Tue, 21 Apr 2020 15:22:42 +0200	[thread overview]
Message-ID: <ed11f532-432e-cc4c-160e-31b0ec427b82@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2004202320370.2957@eliteleevi.tm.intel.com>

Hi,

On 4/20/20 10:28 PM, Kai Vehmanen wrote:
> Hey,
> 
> On Mon, 20 Apr 2020, Pierre-Louis Bossart wrote:
> 
>>>> On 4/3/20 3:01 AM, Hans de Goede wrote:
>>>>> Unfortunately even with that patch cherry picked the errors my
>>>>> patch silences still happen.
>>
>> Sorry about the delay, on my side I don't see this anymore in my ApolloLake or
>> CML tests. Kai, can you confirm for HDaudio platforms?
> 
> I tested on a set of HDA platforms and I could not trigger the "no reply
> expected" errors. Tested with sof-dev (Mark's latest tree but staged SOF
> patches) that has the "ASoC: SOF: Intel: hda-loader: clear the IPC ack bit
> after FW_PURGE" patch.
> 
> If I revert this patch, the error trace comes back immediately, so this
> definitely helps to the trace spam at least in these cases.
> 
> There could of course be some relation to FW version. So if someone can
> still get the error trace, the FW version and platform used would be
> interesting information.

I've retested with 5.7-rc2 (previous testing was on 5.6-rc# + the
"ASoC: SOF: Intel: hda-loader: clear the IPC ack bit after FW_PURGE" patch)
and I'm no longer seeing this. So I guess fixing this also needed some other
patches which have now landed in 5.7.

So this is resolved now and my patch for this can be dropped.

Regards,

Hans


  reply	other threads:[~2020-04-21 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 18:49 [PATCH 1/2] ASoC: SOF: Fix "no reply expected" error during firmware-boot Hans de Goede
2020-04-02 18:49 ` [PATCH 2/2] ASoC: SOF: Turn "firmware boot complete" message into a dbg message Hans de Goede
2020-04-02 19:18   ` Pierre-Louis Bossart
2020-04-03 13:40   ` Applied "ASoC: SOF: Turn "firmware boot complete" message into a dbg message" to the asoc tree Mark Brown
2020-04-02 19:15 ` [PATCH 1/2] ASoC: SOF: Fix "no reply expected" error during firmware-boot Pierre-Louis Bossart
2020-04-03  8:01   ` Hans de Goede
2020-04-03 13:17     ` Pierre-Louis Bossart
2020-04-20 12:48       ` Mark Brown
2020-04-20 15:17         ` Pierre-Louis Bossart
2020-04-20 20:28           ` Kai Vehmanen
2020-04-21 13:22             ` Hans de Goede [this message]
2020-04-21 13:36               ` Pierre-Louis Bossart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed11f532-432e-cc4c-160e-31b0ec427b82@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).