From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
Christian Bundy <christianbundy@fraction.io>,
yang.jie@linux.intel.com, zwisler@google.com,
pierre-louis.bossart@linux.intel.com, broonie@kernel.org
Subject: Re: [bug report] 'ASoC: Intel: haswell: Power transition refactor' and PulseAudio
Date: Tue, 1 Sep 2020 17:37:06 +0200 [thread overview]
Message-ID: <c93c0522-d8b7-e4c4-b11b-80646cfd0432@intel.com> (raw)
In-Reply-To: <026aa0fd558b8b91a67a868a25eb84d8749101b7.camel@linux.intel.com>
On 2020-09-01 5:23 PM, Liam Girdwood wrote:
> On Tue, 2020-09-01 at 13:33 +0200, Cezary Rojewski wrote:
...
>>
>> Hello Christian,
>>
>> Thank you for report! Issue is a known one to us and has already
>> been
>> addressed by:
>>
>> [PATCH v4 00/13] ASoC: Intel: Catpt - Lynx and Wildcat point
>> https://www.spinics.net/lists/alsa-devel/msg113762.html
>>
>> waiting for final dependency to be merged (Andy's resource-API
>> changes,
>> as Mark already added the SPI ones) so v5 with review changes can be
>> provided. Shouldn't be long before this gets merged. As consequence,
>> /haswell/ ceases to exist.
>>
>
> Please also don't forget that the new BDW HW register programming flows
> need to be shared as common code with the SOF BDW driver.
>
> Thanks
>
> Liam
>
I don't believe this is related to Christian's report.
Anyway, revert-patch for sound/soc/intel/haswell/ solution has been
provided so it can be later propagated to v5.8 and v5.9 -stable with
matching upstream commit's sha-id.
Czarek
next prev parent reply other threads:[~2020-09-01 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 21:55 [bug report] 'ASoC: Intel: haswell: Power transition refactor' and PulseAudio Christian Bundy
2020-09-01 11:33 ` Cezary Rojewski
2020-09-01 13:38 ` Pierre-Louis Bossart
2020-09-01 14:11 ` Cezary Rojewski
2020-09-01 15:23 ` Liam Girdwood
2020-09-01 15:37 ` Cezary Rojewski [this message]
2020-09-01 17:25 ` Christian Bundy
2020-09-01 20:31 ` Liam Girdwood
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=c93c0522-d8b7-e4c4-b11b-80646cfd0432@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=christianbundy@fraction.io \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yang.jie@linux.intel.com \
--cc=zwisler@google.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