From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>,
Dominik Brodowski <linux@dominikbrodowski.net>
Cc: alsa-devel@alsa-project.org, kuninori.morimoto.gx@renesas.com,
curtis@malainey.com, tiwai@suse.com,
Keyon Jie <yang.jie@linux.intel.com>,
linux-kernel@vger.kernel.org, liam.r.girdwood@linux.intel.com,
Mark Brown <broonie@kernel.org>
Subject: Re: snd_hda_intel/sst-acpi sound breakage on suspend/resume since 5.6-rc1
Date: Thu, 19 Mar 2020 14:05:56 -0500 [thread overview]
Message-ID: <f6b7c60a-d99e-c140-31d0-0b56960c3ec9@linux.intel.com> (raw)
In-Reply-To: <750f7841-0b95-9fa8-d858-e0bff4d834d5@intel.com>
On 3/19/20 1:35 PM, Cezary Rojewski wrote:
> On 2020-03-19 19:24, Dominik Brodowski wrote:
>> On Thu, Mar 19, 2020 at 06:33:50PM +0100, Cezary Rojewski wrote:
>>>
>>> Could you confirm the same happens on your machine when revert of
>>> mentioned
>>> patch is not applied ("stream is NULL" messages occur)? Issue may be
>>> harmless but explained sequence does not look right.
>>
>> Indeed, I still see
>>
>> haswell-pcm-audio haswell-pcm-audio: warning: stream is NULL, no
>> stream to reset, ignore it.
>> haswell-pcm-audio haswell-pcm-audio: warning: stream is NULL, no
>> stream to free, ignore it.
>> haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW
>> info: type 01, - version: 00.00, build 77, source commit id:
>> 876ac6906f31a43b6772b23c7c983ce9dcb18a19
>> haswell-pcm-audio haswell-pcm-audio: warning: stream is NULL, no
>> stream to reset, ignore it.
>> haswell-pcm-audio haswell-pcm-audio: warning: stream is NULL, no
>> stream to free, ignore it.
>>
>> though sounds continues to work.
>>
>
> Thanks once again for your input and time!
>
> I'll prepare patches for both issues. My guess is haswell-pcm could be
> updated to handle 'platform' component param just fine, but it is
> probably a change of more than few lines. I'd rather revert non-SOF
> broadwell to its previous behavior and start a separate task from there.
It'd be good to know why a dummy platform component is required though.
next prev parent reply other threads:[~2020-03-19 19:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 6:30 snd_hda_intel/sst-acpi sound breakage on suspend/resume since 5.6-rc1 Dominik Brodowski
2020-03-18 9:41 ` Cezary Rojewski
2020-03-18 9:57 ` Dominik Brodowski
2020-03-18 10:05 ` Cezary Rojewski
2020-03-18 10:19 ` Dominik Brodowski
2020-03-18 10:49 ` Keyon Jie
2020-03-18 12:39 ` Dominik Brodowski
2020-03-18 15:13 ` Pierre-Louis Bossart
2020-03-18 16:20 ` Dominik Brodowski
2020-03-18 17:08 ` Pierre-Louis Bossart
2020-03-18 17:19 ` Dominik Brodowski
2020-03-18 17:29 ` Pierre-Louis Bossart
2020-03-18 17:35 ` Cezary Rojewski
[not found] ` <CAOReqxjmUCGX18y_XW_sjcU2xWha_+wJ7L+SuzJ5ZrOddCfZkw@mail.gmail.com>
2020-03-18 19:13 ` Ross Zwisler
2020-03-18 18:27 ` Cezary Rojewski
2020-03-18 19:22 ` Dominik Brodowski
2020-03-18 20:43 ` Cezary Rojewski
2020-03-18 21:52 ` Dominik Brodowski
2020-03-18 22:20 ` Cezary Rojewski
2020-03-19 13:00 ` Dominik Brodowski
2020-03-19 13:17 ` Cezary Rojewski
2020-03-19 13:41 ` Mark Brown
2020-03-19 15:48 ` Cezary Rojewski
2020-03-19 16:51 ` Dominik Brodowski
2020-03-19 17:21 ` Pierre-Louis Bossart
2020-03-19 17:35 ` Mark Brown
2020-03-20 3:21 ` Keyon Jie
2020-03-19 17:41 ` Cezary Rojewski
2020-03-19 17:33 ` Cezary Rojewski
2020-03-19 17:45 ` Cezary Rojewski
2020-03-19 18:24 ` Dominik Brodowski
2020-03-19 18:35 ` Cezary Rojewski
2020-03-19 19:05 ` Pierre-Louis Bossart [this message]
2020-03-30 10:23 ` Dominik Brodowski
2020-03-30 11:10 ` Cezary Rojewski
2020-03-30 11:39 ` Mark Brown
2020-03-30 15:37 ` 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=f6b7c60a-d99e-c140-31d0-0b56960c3ec9@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=curtis@malainey.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=tiwai@suse.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