mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, 07 Jun 2026 14:15:59 +0200	[thread overview]
Message-ID: <875x3usg00.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACYx1SqT5sL7MpsjnB16dPwhjyvhzjL3M0E6-ka0Rn-cSgqiqA@mail.gmail.com>

On Sat, 06 Jun 2026 16:19:26 +0200,
周Ocean wrote:
> 
> Hi Takashi,
> 
> To be honest, I'm not an expert on the low-level hardware design of
> this codec, but I can confirm that the internal microphone only works
> normally when we apply this patch.
> 
> I realized why the previous two dumps were identical: the user-space
> audio server (PipeWire) automatically restored the routing and
> switched NID 0x14 to NID 0x1e (index 3) at runtime, masking the actual
> boot defaults.
> 
> This time, I stopped PipeWire entirely, reloaded the stock driver, and
> captured the true hardware defaults. Please find the new logs
> attached:
> 
> 1. alsa-info-raw-defaults.txt.gz (Stock driver, pure hardware defaults):
> Here, NID 0x14 actually defaults to NID 0x1b (index 1, Rear Mic) on boot:
>    Connection: 4
>       0x1a 0x1b* 0x1d 0x1e
> 
> 2. alsa-info-with-patch.txt.gz (Patched driver):
> Here, the quirk forces it to NID 0x1e (index 3, Internal Mic) at initialization:
>    Connection: 4
>       0x1a 0x1b 0x1d 0x1e*
> 
> Without the patch, testing the microphone in the stock driver yields a
> loud buzzing/humming noise (typical of a floating/unconnected input
> pin on NID 0x1b) with only a very faint sound when tapping the chassis
> (due to signal crosstalk/leakage from NID 0x1e to NID 0x1b). Even if
> PipeWire switches the connection to 0x1e at runtime later, it fails to
> record normal sound.
> 
> Applying the quirk at ACT_INIT ensures NID 0x14 is correctly mapped to
> the physical internal mic pin (0x1e) from boot, resolving the floating
> pin noise and restoring mic capture to a normal level.

Looking at your alsa-info.sh outputs, it shows that the rear mic jack
is plugged:

        control.17 {
                iface CARD
                name 'Rear Mic Jack'
                value true
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }

so the driver makes ADC 0x14 connected to 0x1b, which is the pin
for the rear mic.

If you get a noise from it, it means that something wrong with that
route.


Takashi

  reply	other threads:[~2026-06-07 12:16 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
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 [this message]
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=875x3usg00.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