From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: dmummenschanz@web.de, alsa-devel@alsa-project.org
Subject: Re: Aw: Re: Cannon Lake PCH cAVS (ALC892) not detected by kernel driver
Date: Wed, 9 Feb 2022 09:51:34 -0600 [thread overview]
Message-ID: <c71dbf89-80a3-538e-6ebe-e1d1869183e8@linux.intel.com> (raw)
In-Reply-To: <trinity-c5ab92fd-fbab-4431-8579-f8576a9ba71e-1644390880605@3c-app-webde-bap12>
On 2/9/22 01:14, dmummenschanz@web.de wrote:
> The information about the codec is based on the string windows
> provides:
>
> HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_15580351&REV_1003\4&16AF2B56&&
> 0001
>
> Here is the alsa-info output for the 5.16 mainline kernel:
>
> http://alsa-project.org/db/?f=38c48cd24dc4ba9a9487dd96f857120cc9ce4367
The use of this option is not clear:
snd_intel_dspcfg: dsp_driver=1
This means you are trying to force the use of the legacy driver. is this
intentional? Can you remove it and see what happens?
The results show you don't have a driver bound to the PCI device, so
likely something goes boink in the probe.
It wouldn't hurt to enable dynamic debug as well.
options snd_hda_intel dyndbg=+p
options snd_intel_dspcfg dyndbg=+p
next prev parent reply other threads:[~2022-02-09 15:52 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 [this message]
2022-02-09 16:47 ` Aw: " dmummenschanz
2022-02-12 11:33 ` dmummenschanz
2022-02-12 19:42 ` Pierre-Louis Bossart
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=c71dbf89-80a3-538e-6ebe-e1d1869183e8@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmummenschanz@web.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