From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>, alsa-devel@alsa-project.org
Cc: tiwai@suse.de, broonie@kernel.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [RFC TEST] ASoC: soc-dai: revert all changes to DAI startup/shutdown sequence
Date: Wed, 15 Apr 2020 16:56:26 -0500 [thread overview]
Message-ID: <fd1a219b-28b4-e324-6657-9fb4a65ec640@linux.intel.com> (raw)
In-Reply-To: <9bbb1e49-6542-b1a3-d9e6-8dd30b79d07f@redhat.com>
On 4/15/20 4:26 PM, Hans de Goede wrote:
> Hi,
>
> On 4/15/20 5:04 AM, Pierre-Louis Bossart wrote:
>> On Baytrail/Cherrytrail, the Atom/SST driver fails miserably:
>>
>> [ 9.741953] intel_sst_acpi 80860F28:00: FW Version 01.0c.00.01
>> [ 9.832992] intel_sst_acpi 80860F28:00: FW sent error response 0x40034
>> [ 9.833019] intel_sst_acpi 80860F28:00: FW alloc failed ret -4
>> [ 9.833028] intel_sst_acpi 80860F28:00: sst_get_stream returned err -5
>> [ 9.833033] sst-mfld-platform sst-mfld-platform: ASoC: DAI prepare
>> error: -5
>> [ 9.833037] Baytrail Audio Port: ASoC: prepare FE Baytrail Audio
>> Port failed
>> [ 9.853942] intel_sst_acpi 80860F28:00: FW sent error response 0x40034
>> [ 9.853974] intel_sst_acpi 80860F28:00: FW alloc failed ret -4
>> [ 9.853984] intel_sst_acpi 80860F28:00: sst_get_stream returned err -5
>> [ 9.853990] sst-mfld-platform sst-mfld-platform: ASoC: DAI prepare
>> error: -5
>> [ 9.853994] Baytrail Audio Port: ASoC: prepare FE Baytrail Audio
>> Port failed
>>
>> Commit b56be800f1292 ("ASoC: soc-pcm: call
>> snd_soc_dai_startup()/shutdown() once") was the initial problematic
>> commit.
>>
>> Commit 1ba616bd1a6d5e ("ASoC: soc-dai: fix DAI startup/shutdown
>> sequence")
>> was an attempt to fix things but it does not work on Baytrail,
>> reverting all changes seems necessary for now.
>>
>> Fixes: 1ba616bd1a6d5e ("ASoC: soc-dai: fix DAI startup/shutdown
>> sequence")
>> Signed-off-by: Pierre-Louis Bossart
>> <pierre-louis.bossart@linux.intel.com>
>
> Thank you for figuring this out!
>
> I've tested this on the 2 devices where I have seen the problem
> (the only 2 devices on which I've tested 5.7-rc1 so far):
>
> One Cherry Trail device with a RT5645 codec and another
> Cherry Trail device with an ES8316 and I can confirm that this
> fixes the issue on both devices:
>
> Tested-by: Hans de Goede <hdegoede@redhat.com>
Thanks Hans for checking.
I must admit it was one of the more complicated bisects I've ever done,
we had 3 different regressions so I end-up merging sound-v5.7-rc1 on top
of v5.7-rc1, then do a manual rebase to create a linear branch, then
squash fixes with the original problematic commits, and then bisecting
once I had a single issue left.
I'll see if we can retask some of the SOF CI Baytrail/Cherrytrail
machines to run regressions on the legacy driver on a periodic basis,
e.g. during week-ends when no one is around.
next prev parent reply other threads:[~2020-04-15 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 3:04 [RFC TEST] ASoC: soc-dai: revert all changes to DAI startup/shutdown sequence Pierre-Louis Bossart
2020-04-15 17:28 ` Mark Brown
2020-04-15 19:05 ` Pierre-Louis Bossart
2020-04-15 21:26 ` Hans de Goede
2020-04-15 21:56 ` Pierre-Louis Bossart [this message]
2020-04-16 8:46 ` Hans de Goede
2020-04-15 23:36 ` Mark Brown
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=fd1a219b-28b4-e324-6657-9fb4a65ec640@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=kuninori.morimoto.gx@renesas.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.