From: Hans de Goede <hdegoede@redhat.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Asoc: Intel: SST (CHT) regression in asoc/for-5.11
Date: Sun, 29 Nov 2020 13:24:19 +0100 [thread overview]
Message-ID: <93cc93a1-82bd-f5a3-4e19-4cfc65c868e7@redhat.com> (raw)
Hi All,
To test the code to dynamically switch between SST/SOF support on BYT/CHT
from the kernel commandline I merged:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/log/?h=for-5.11
Into my personal tree (mostly Linus' master + some pending patches from
myself).
After this I was getting the following errors in dmesg when using sound on
a Medion E2228T laptop with a CHT SoC + NAU8824 codec:
[ 53.805205] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0
[ 53.805479] intel_sst_acpi 808622A8:00: fw returned err -16
[ 53.806281] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMD: pcm0_in event failed: -16
[ 54.829548] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0
[ 54.829596] intel_sst_acpi 808622A8:00: fw returned err -16
[ 54.829668] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMD: media0_out event failed: -
[ 55.853230] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0
[ 55.853244] intel_sst_acpi 808622A8:00: fw returned err -16
[ 55.853269] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMD: codec_out0 mix 0 event fai
[ 56.876435] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0
[ 56.876481] intel_sst_acpi 808622A8:00: fw returned err -16
[ 56.876563] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMD: media0_out mix 0 event fai
[ 61.847455] intel_sst_acpi 808622A8:00: FW sent error response 0x40015
[ 61.847564] intel_sst_acpi 808622A8:00: fw returned err -1
[ 61.847659] sst-mfld-platform sst-mfld-platform: ASoC: error at snd_soc_dai_startup on ssp2
[ 61.847722] SSP2-Codec: ASoC: BE open failed -1
[ 61.847754] Audio Port: ASoC: failed to start some BEs -1
[ 61.847786] intel_sst_acpi 808622A8:00: FW sent error response 0x40006
[ 64.301284] intel_sst_acpi 808622A8:00: FW sent error response 0x90001
[ 64.301545] intel_sst_acpi 808622A8:00: not suspending FW!!, Err: -2
Dropping the asoc/for-5.11 merge and just cherry-picking Pierre-Louis' changes
for the dynamic switching makes these go away. So this seems to be caused by
other changes in asoc/for-5.11.
So any clues where to start looking for this, or should I just bisect this?
Regards,
Hans
next reply other threads:[~2020-11-29 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 12:24 Hans de Goede [this message]
2020-11-30 16:15 ` Asoc: Intel: SST (CHT) regression in asoc/for-5.11 Pierre-Louis Bossart
2020-12-01 3:24 ` Pierre-Louis Bossart
2020-12-01 14:46 ` Takashi Iwai
2020-12-01 15:37 ` Hans de Goede
2020-12-01 16:15 ` Ranjani Sridharan
2020-12-01 16:23 ` Takashi Iwai
2020-12-01 23:52 ` Ranjani Sridharan
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=93cc93a1-82bd-f5a3-4e19-4cfc65c868e7@redhat.com \
--to=hdegoede@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yang.jie@linux.intel.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).