From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: SOF: Fix "no reply expected" error during firmware-boot
Date: Thu, 2 Apr 2020 14:15:11 -0500 [thread overview]
Message-ID: <1ecf6c31-4eb1-0288-2353-7a7a421fe5e7@linux.intel.com> (raw)
In-Reply-To: <20200402184948.3014-1-hdegoede@redhat.com>
On 4/2/20 1:49 PM, Hans de Goede wrote:
> At least on Canon Lake each time the SOF firmware is booted,
> the following error is logged in dmesg:
>
> [ 36.711803] sof-audio-pci 0000:00:1f.3: error: no reply expected, received 0x0
>
> Since the DSP is powered down when not in used this happens everytime
> e.g. a notification plays, polluting dmesg with these false-positive
> errors.
What kernel are you using Hans? I thought this was solved with
8354d9b44530b ("ASoC: SOF: Intel: hda-loader: clear the IPC ack bit
after FW_PURGE done")
Set DONE bit after the FW_PURGE IPC is polled successfully, to clear the
interrupt and avoid the arrival of the confusing unexpected ipc.
> Add a check to snd_sof_ipc_reply() which makes it return success when
> receiving an unexpected msg_id 0 during fw-boot, fixing these
> false-positive errors being logged.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> sound/soc/sof/ipc.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/sound/soc/sof/ipc.c b/sound/soc/sof/ipc.c
> index 78aa1da7c7a9..7303b3d42f12 100644
> --- a/sound/soc/sof/ipc.c
> +++ b/sound/soc/sof/ipc.c
> @@ -312,6 +312,11 @@ int snd_sof_ipc_reply(struct snd_sof_dev *sdev, u32 msg_id)
> {
> struct snd_sof_ipc_msg *msg = &sdev->ipc->msg;
>
> + /* Ignore msg_id 0 being send during fw-boot */
> + if (msg->ipc_complete && sdev->fw_state == SOF_FW_BOOT_IN_PROGRESS &&
> + msg_id == 0)
> + return 0;
> +
> if (msg->ipc_complete) {
> dev_err(sdev->dev, "error: no reply expected, received 0x%x",
> msg_id);
>
next prev parent reply other threads:[~2020-04-02 19:16 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 ` Pierre-Louis Bossart [this message]
2020-04-03 8:01 ` [PATCH 1/2] ASoC: SOF: Fix "no reply expected" error during firmware-boot 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
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=1ecf6c31-4eb1-0288-2353-7a7a421fe5e7@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=perex@perex.cz \
--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).