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: Intel HDMI probe regression on IVB (and older?)
Date: Mon, 20 Jun 2022 09:27:39 +0200 [thread overview]
Message-ID: <87bkunztec.wl-tiwai@suse.de> (raw)
Hi,
we've got a regression report about Intel HDMI. It seems that the
recent change to skip the component binding (commit c9db8a30d9f0)
throws away the devices incorrectly on IvyBridge. I guess the similar
issue could happen on older chips. The bug report is found at
https://bugzilla.opensuse.org/show_bug.cgi?id=1200611
Judging from the logs there, on IvyBridge, the GPU is
00:02.0 0380: 8086:0162 (rev 09)
DeviceName: Onboard IGD
Subsystem: 1043:84ca
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
while HD-audio is
00:1b.0 0403: 8086:1e20 (rev 04)
Subsystem: 1043:84a8
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f7d10000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
Unlike Haswell, IVB has no dedicated HDMI audio controller, and it's
connected on HD-audio bus of 00:1b.0.
Kai, could you check this issue?
thanks,
Takashi
next reply other threads:[~2022-06-20 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 7:27 Takashi Iwai [this message]
2022-06-20 9:26 ` Intel HDMI probe regression on IVB (and older?) 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
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=87bkunztec.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