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 15:10:39 +0200 [thread overview]
Message-ID: <s5hef2e1cq8.wl-tiwai@suse.de> (raw)
In-Reply-To: <156405901806.31349.18306052136503918886@skylake-alporthouse-com>
On Thu, 25 Jul 2019 14:50:18 +0200,
Chris Wilson wrote:
>
> Quoting Takashi Iwai (2019-07-25 11:44:08)
> > On Thu, 25 Jul 2019 12:21:11 +0200,
> > Chris Wilson wrote:
> > >
> > > Quoting Chris Wilson (2019-07-25 09:30:25)
> > > > Quoting Takashi Iwai (2019-07-25 09:26:56)
> > > > > On Thu, 25 Jul 2019 10:16:07 +0200,
> > > > > Takashi Iwai wrote:
> > > > > >
> > > > > > 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.
> > > > >
> > > > > Now checking the code, and I believe the workaround applied there can
> > > > > be skipped for non-Haswell chips. Could you try the patch below in
> > > > > addition?
> > > >
> > > > Due to the way patchwork works, this patch will now be tested instead of
> > > > the revert. So watch this space.
> > >
> > > Sadly, no change. Patchwork definitely lists this patch as being the one
> > > tested, but maybe send it separately just in case.
> >
> > Hm, does the error indicate the same message ("last cmd=0x202f8100")?
> > If yes, we might need another workaround. This is a special verb for
> > Intel with some black magic to communicate with GPU. The tweak via
> > this verb is needed for other platforms to assure the enablement of
> > all pins and DP 1.2, but it might be incorrect for ICL.
> >
> > Can anyone at Intel check whether the verb (0x781/0xf81) is still
> > valid for ICL?
> >
> > Anyways below is a patch to leave the verb access for ICL.
> > Let's see...
> >
> >
> > thanks,
> >
> > Takashi
> >
> > -- 8< --
> > From: Takashi Iwai <tiwai@suse.de>
> > Subject: [PATCH] ALSA: hda/hdmi - Don't apply black magic to Icelake HDMI
> > codecs
> >
> > The Intel-specific verb to enable all pins and DP 1.2 seems causing a
> > problem on ICL by some reason. Skip applying the verb for ICL as a
> > workaround.
>
> Hmm. Nothing with icl-hda managed to boot. Coincidence?
No idea, honestly speaking, but it's a bad sign. Let's scratch.
Takashi
>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> > sound/pci/hda/patch_hdmi.c | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
> > index 2096993eaf28..7e8236e5eac0 100644
> > --- a/sound/pci/hda/patch_hdmi.c
> > +++ b/sound/pci/hda/patch_hdmi.c
> > @@ -2804,12 +2804,15 @@ static int intel_hsw_common_init(struct hda_codec *codec, hda_nid_t vendor_nid,
> > spec->port_map = port_map;
> > spec->port_num = port_num;
> >
> > - intel_haswell_enable_all_pins(codec, true);
> > - intel_haswell_fixup_enable_dp12(codec);
> > + if (!is_icelake(codec)) {
> > + intel_haswell_enable_all_pins(codec, true);
> > + intel_haswell_fixup_enable_dp12(codec);
> > + }
> >
> > codec->display_power_control = 1;
> >
> > - codec->patch_ops.set_power_state = haswell_set_power_state;
> > + if (!is_icelake(codec))
> > + codec->patch_ops.set_power_state = haswell_set_power_state;
> > codec->depop_delay = 0;
> > codec->auto_runtime_pm = 1;
> >
> > --
> > 2.16.4
> >
> >
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-25 13:10 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
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 [this message]
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=s5hef2e1cq8.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