Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: Intel HDMI probe regression on IVB (and older?)
Date: Tue, 21 Jun 2022 14:01:23 +0200	[thread overview]
Message-ID: <8735fyb4z0.wl-tiwai@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2206211427200.1532214@eliteleevi.tm.intel.com>

On Tue, 21 Jun 2022 13:36:04 +0200,
Kai Vehmanen wrote:
> 
> Hi,
> 
> On Mon, 20 Jun 2022, Kai Vehmanen wrote:
> 
> > On Mon, 20 Jun 2022, Takashi Iwai wrote:
> > 
> > > > But it's a marginal difference, so for your version:
> > > > 
> > > > Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> > > 
> > > OK, could you throw the patch to CI for verification?
> > > I can merge it for the next pull request (probably in this week) once
> > > after confirmation. 
> > 
> > sure thing, I'll confirm later this week.
> 
> tests are clean for the patch so
> 
> Tested-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> 
> Did a bit of analysis why this was not caught in testing earlier. IVB (and 
> older) systems are covered in the intel-gfx CI, but it turns out PCI class 
> is 0300 (VGA compatible adapter) on all of these. But alas on the 
> reporter's system, PCI_CLASS_DISPLAY_OTHER was used, so the problem is 
> definitely there and the fix is needed.

Great, thanks for the update.  I submitted the proper patch now.


Takashi

      reply	other threads:[~2022-06-21 12:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  7:27 Intel HDMI probe regression on IVB (and older?) Takashi Iwai
2022-06-20  9:26 ` Kai Vehmanen
2022-06-20 15:03   ` Takashi Iwai
2022-06-20 15:31     ` Kai Vehmanen
2022-06-20 15:49       ` Takashi Iwai
2022-06-20 16:18         ` Kai Vehmanen
2022-06-21 11:36           ` Kai Vehmanen
2022-06-21 12:01             ` Takashi Iwai [this message]

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=8735fyb4z0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lucas.demarchi@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