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: Wed, 10 Jun 2026 19:53:07 +0200	[thread overview]
Message-ID: <87y0gmjn98.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACYx1Soy=oqaZfX9A2NuvOdoghxPPyviFekk5giMMCJ5N+2NUQ@mail.gmail.com>

On Wed, 10 Jun 2026 17:19:01 +0200,
周Ocean wrote:
> 
> Hi Takashi,
> 
> Thank you for the suggestions. I have tested the stock driver as requested.
> 
> Here are the results:
> 
> 1. Does the jack detection work for the rear jack? Yes, the jack
> detection works properly for the rear jack.
> 
> 2. Does the output from the rear work as-is? Yes, the output works
> normally. I primarily use this jack for an external TRS speaker.
> 
> 3. Changing the pin control of 0x1c: I plugged a TRRS headset (with a
> microphone) into the rear jack. Both the audio output and the headset
> microphone worked properly without any modifications. When I ran sudo
> hda-verb /dev/snd/hwC1D0 0x1c SET_PIN_WIDGET_CONTROL 0x00, the
> headphone output stopped as expected, and the microphone continued to
> work normally.
> 
> Based on these tests, the rear jack is a fully functional TRRS combo
> jack, and there is no hardware interference between the output (0x1c)
> and input (0x1b) pins.
> 
> The loud buzzing noise I reported earlier occurs only when a 3-pole
> TRS plug (like my external speaker or a standard headphone without a
> mic) is connected to the rear jack. It appears the hardware lacks
> proper impedance sensing to distinguish between TRS and TRRS plugs,
> and blindly leaves the mic input pin (0x1b) active. Since the TRS plug
> shorts the mic ring to ground, the active 0x1b pin captures ground
> loop noise.
> 
> This behavior is consistent with what I observe on Windows on the same
> machine: when a TRS speaker is plugged in, Windows shows a microphone
> device that captures no sound, likely because the pin is shorted to
> ground.
> 
> Given that this machine is a Mini-PC and the rear jack is mostly used
> for TRS external speakers, would applying a pin quirk to disable 0x1b
> (setting it to 0x40000000) be the most appropriate upstream fix?

Have you tried ctx_fixup_headset_mic, BTW?  I'm not sure whether this
is applicable to your model, but worth for a try.

If this doesn't work, then disabling the mic would be the simplest
solution.


thanks,

Takashi

      reply	other threads:[~2026-06-10 17:53 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
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 [this message]

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=87y0gmjn98.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

powered by JetHome