From: Takashi Iwai <tiwai@suse.de>
To: 周Ocean <zhouoceanhy@gmail.com>
Cc: perex@perex.cz, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
Ocean Zhou <51983215+ocean-sudo@users.noreply.github.com>
Subject: Re: [PATCH v2] ALSA: hda/conexant: fix FEVM FA880 PRO internal mic mux
Date: Sun, 31 May 2026 15:26:37 +0200 [thread overview]
Message-ID: <8733z7pv5e.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACYx1SrnTfg6GKK2S1Vb13f9OWOq1x=VUDA=AFWs1CALsC_B2g@mail.gmail.com>
On Sun, 31 May 2026 04:52:03 +0200,
周Ocean wrote:
>
>
> Hi Takashi,
>
> Thanks for your quick reply and professional guidance!
>
> Here is the original topology of Conexant CX20632 (SSID 2014:8004) on FEVM
> FA880 PRO:
>
> - Node 0x14 [Audio Input] (Analog Capture)
> Connection: 4
> 0x1a 0x1b 0x1d 0x1e* (Note: 0x1e is selected by default)
>
> - Node 0x1e [Pin Complex] (Internal Mic)
> Pin Default 0x95a60120: [Fixed] Mic at Int Top
> Connection: None (It's a digital/fixed mic pin)
>
> - Node 0x1a [Pin Complex] (Front Mic): Pin Default 0x02a1103e
> - Node 0x1b [Pin Complex] (Rear Mic): Pin Default 0x01a13030
>
> Regarding the kernel crash, I encountered a kernel Oops in try_assign_dacs()
> during the auto-config stage on the newer 7.0.10-cachyos kernel. I suspect it
> might be triggered when loading my out-of-tree custom DKMS module, or due to
> changes in how try_assign_dacs() interacts with this specific topology on the
> new kernel. (Fortunately, the system works perfectly fine on the 6.18-lts
> kernel with my custom module).
>
> In the older kernel (like 6.18), the auto-parser didn't crash but would
> incorrectly route Node 0x14 away from Node 0x1e after probing, disabling the
> internal microphone. That was why my previous patch forced index 0x03 on Node
> 0x14 in HDA_FIXUP_ACT_INIT.
>
> Since you mentioned correcting the routes before parsing, should we override
> the connection list of Node 0x14 to restrict it during
> HDA_FIXUP_ACT_PRE_PROBE, or override the pin default configuration via
> HDA_FIXUP_PINS to fix this properly?
>
> I would really appreciate your advice on how we should construct the fixup
> gracefully!
For better understanding your system, could you give alsa-info.sh
outputs (at best both with and without your patch)? Run the script
with --no-upload option and attach the outputs.
thanks,
next prev parent reply other threads:[~2026-05-31 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 4:11 ocean
2026-05-29 9:05 ` Takashi Iwai
2026-05-31 4:02 ` 周Ocean
[not found] ` <CACYx1SrnTfg6GKK2S1Vb13f9OWOq1x=VUDA=AFWs1CALsC_B2g@mail.gmail.com>
2026-05-31 13:26 ` Takashi Iwai [this message]
2026-06-03 2:06 ` 周Ocean
2026-06-03 15:08 ` 周Ocean
2026-06-04 8:12 ` Takashi Iwai
2026-06-06 14:19 ` 周Ocean
2026-06-07 12:15 ` Takashi Iwai
2026-06-07 16:48 ` 周Ocean
2026-06-07 17:40 ` 周Ocean
2026-06-08 7:28 ` Takashi Iwai
2026-06-10 15:19 ` 周Ocean
2026-06-10 17:53 ` 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=8733z7pv5e.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=51983215+ocean-sudo@users.noreply.github.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=zhouoceanhy@gmail.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