From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: dmummenschanz@web.de, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>, "Vehmanen, Kai" <kai.vehmanen@intel.com>
Subject: Re: Cannon Lake PCH cAVS (ALC892) not detected by kernel driver
Date: Sat, 12 Feb 2022 13:42:28 -0600 [thread overview]
Message-ID: <2db61794-d772-8df6-a843-fd1512cfaa57@linux.intel.com> (raw)
In-Reply-To: <trinity-7e2e8baa-0f43-4b12-902d-a907bd7efb79-1644665613748@3c-app-webde-bs56>
On 2/12/22 05:33, dmummenschanz@web.de wrote:
> I did some more digging into the code to find out what goes boink.
> For comparison I took my wife's desktop wich has a Cannon Lake chipset
> as well along with a working a ALC892 AVS device.
>
> It seems there is a codec mask issue selected in the chip->bus struct.
> Inside the function
>
> static int azx_probe_continue(struct azx *chip)
>
> of hda_intel.c the bus->codec_mask on my wife's pc contains the integer
> value "5" and both ALC892 and the HDMI is found. On my device it is "4"
> and only the HDMI is found.
>
> /* create codec instances */
> if (bus->codec_mask) {
> err = azx_probe_codecs(chip, azx_max_codecs[chip->driver_type]);
> if (err < 0)
> goto out_free;
> }
>
> After forcing the falue before probing: "bus->codec_mask = 5;" the
> ALC892 is finally detected on my system and I have sound! alsa-info
> below: Please pardon the trash printk's in the log ;-)
>
> http://alsa-project.org/db/?f=057aac1a0e9591de3847dca5ebc424dd65c8a221
>
> I'll do some more digging into it next week but it would probably
> save tons of time if someone could point me is the right direction
> where to look further?
Adding Kai and Takashi, in case they haven't see this codec_mask issue.
I personally don't recall having seen this before.
next prev parent reply other threads:[~2022-02-12 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 18:46 Cannon Lake PCH cAVS (ALC892) not detected by kernel driver dmummenschanz
2022-02-08 21:55 ` Pierre-Louis Bossart
2022-02-09 7:14 ` Aw: " dmummenschanz
2022-02-09 15:51 ` Pierre-Louis Bossart
2022-02-09 16:47 ` Aw: " dmummenschanz
2022-02-12 11:33 ` dmummenschanz
2022-02-12 19:42 ` Pierre-Louis Bossart [this message]
2022-02-13 9:08 ` Takashi Iwai
2022-02-14 6:49 ` dmummenschanz
2022-02-14 7:08 ` Takashi Iwai
2022-02-14 7:38 ` dmummenschanz
2022-02-14 8:42 ` Takashi Iwai
2022-02-14 9:23 ` Aw: " dmummenschanz
2022-02-14 9:54 ` 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=2db61794-d772-8df6-a843-fd1512cfaa57@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmummenschanz@web.de \
--cc=kai.vehmanen@intel.com \
--cc=tiwai@suse.de \
/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