Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>,
	Christian Bundy <christianbundy@fraction.io>
Cc: zwisler@google.com, alsa-devel@alsa-project.org,
	broonie@kernel.org, yang.jie@linux.intel.com,
	pierre-louis.bossart@linux.intel.com
Subject: Re: [bug report] 'ASoC: Intel: haswell: Power transition refactor' and PulseAudio
Date: Tue, 01 Sep 2020 16:23:58 +0100	[thread overview]
Message-ID: <026aa0fd558b8b91a67a868a25eb84d8749101b7.camel@linux.intel.com> (raw)
In-Reply-To: <28ee99bc-fe27-9111-893b-1cb000067a7c@intel.com>

On Tue, 2020-09-01 at 13:33 +0200, Cezary Rojewski wrote:
> On 2020-08-31 11:55 PM, Christian Bundy wrote:
> > After upgrading to Linux 5.8 I discovered an audio issue on my
> > device that was introduced in
> > 8ec7d6043263ecf250b9b7c0dd8ade899487538a [0]. I used 'git bisect'
> > to identify the commit that introduced the bug and have confirmed
> > that reverting the commit resolves the problem
> > 
> > Reproduction:
> > 
> > 1. Play any audio via PulseAudio.
> > 2. Observe that the audio output is fuzzy and choppy.
> > 
> > I can use programs like mpv to play audio without PulseAudio, and
> > the audio is fine, but as soon as I open a process that uses
> > PulseAudio it will ruin the audio output for all processes
> > (including mpv) until I reboot.
> > 
> > I'm using a 2015 Chromebook Pixel ("Samus") and have confirmed this
> > problem with a friend who has the same device.
> > 
> > Is there anything I can do to help debug this instead of sending a
> > patch to revert the commit?
> > 
> 
> 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


  parent reply	other threads:[~2020-09-01 15:25 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 [this message]
2020-09-01 15:37     ` Cezary Rojewski
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=026aa0fd558b8b91a67a868a25eb84d8749101b7.camel@linux.intel.com \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=christianbundy@fraction.io \
    --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