Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Revert "ALSA: hda - Fix intermittent CORB/RIRB stall on Intel chips"
Date: Thu, 25 Jul 2019 10:16:07 +0200	[thread overview]
Message-ID: <s5h8ssmttq0.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190725080300.1913-1-chris@chris-wilson.co.uk>

On Thu, 25 Jul 2019 10:03:00 +0200,
Chris Wilson wrote:
> 
> Just a heads up that icl is consistently showing
> 
> <4> [315.478830] snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x202f8100
> <4> [316.482799] snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x202f8100
> <3> [508.412915] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -11
> 
> following commits 2756d9143aa5 ("ALSA: hda - Fix intermittent CORB/RIRB
> stall on Intel chips") and a30f1743e4f5 ("ALSA: line6: sizeof (byte) is
> always 1, use that fact.")

The verb that stalls (0x202f8100) is a read verb (0xf81, Intel
vendor-specific verb for HDMI), so it shouldn't matter whether with or
without write sync, because it needs to read the response in anyway.

If that patch broke anything, it means that something else was already
broken.  Oh well, that ICL crap...

Is it about the runtime PM, or S3 or S4?  The only case we need to
re-issue this verb is only S4, I suppose, so we may skip that in most
cases.


thanks,

Takashi

> 
> Cc: Takashi Iwai <tiwai@suse.de>
> ---
>  sound/pci/hda/hda_intel.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
> index 324a4b20fba9..fdde80d95966 100644
> --- a/sound/pci/hda/hda_intel.c
> +++ b/sound/pci/hda/hda_intel.c
> @@ -313,10 +313,11 @@ enum {
>  
>  #define AZX_DCAPS_INTEL_SKYLAKE \
>  	(AZX_DCAPS_INTEL_PCH_BASE | AZX_DCAPS_PM_RUNTIME |\
> -	 AZX_DCAPS_SYNC_WRITE |\
>  	 AZX_DCAPS_SEPARATE_STREAM_TAG | AZX_DCAPS_I915_COMPONENT)
>  
> -#define AZX_DCAPS_INTEL_BROXTON		AZX_DCAPS_INTEL_SKYLAKE
> +#define AZX_DCAPS_INTEL_BROXTON \
> +	(AZX_DCAPS_INTEL_PCH_BASE | AZX_DCAPS_PM_RUNTIME |\
> +	 AZX_DCAPS_SEPARATE_STREAM_TAG | AZX_DCAPS_I915_COMPONENT)
>  
>  /* quirks for ATI SB / AMD Hudson */
>  #define AZX_DCAPS_PRESET_ATI_SB \
> -- 
> 2.22.0
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-25  8:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25  8:03 [PATCH] Revert "ALSA: hda - Fix intermittent CORB/RIRB stall on Intel chips" Chris Wilson
2019-07-25  8:16 ` Takashi Iwai [this message]
2019-07-25  8:26   ` Takashi Iwai
2019-07-25  8:30     ` Chris Wilson
2019-07-25 10:21       ` Chris Wilson
2019-07-25 10:44         ` Takashi Iwai
2019-07-25 10:49           ` Chris Wilson
2019-07-25 13:45             ` Takashi Iwai
2019-07-25 13:57               ` Chris Wilson
2019-07-25 14:54                 ` Takashi Iwai
2019-07-25 12:50           ` Chris Wilson
2019-07-25 13:10             ` Takashi Iwai
2019-07-25  9:55 ` ✗ Fi.CI.CHECKPATCH: warning for Revert "ALSA: hda - Fix intermittent CORB/RIRB stall on Intel chips" (rev2) Patchwork
2019-07-25 10:17 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-25 12:11 ` ✗ Fi.CI.CHECKPATCH: warning for Revert "ALSA: hda - Fix intermittent CORB/RIRB stall on Intel chips" (rev3) Patchwork
2019-07-25 12:47 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-25 17:30 ` ✗ Fi.CI.CHECKPATCH: warning for Revert "ALSA: hda - Fix intermittent CORB/RIRB stall on Intel chips" (rev4) Patchwork
2019-07-25 17:56 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-07-25 20:49 ` ✓ Fi.CI.IGT: success for Revert "ALSA: hda - Fix intermittent CORB/RIRB stall on Intel chips" (rev3) Patchwork

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=s5h8ssmttq0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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