From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: HDA: Fix internal mic availability for HDA codecs with phantom jack
Date: Tue, 16 Jun 2026 05:16:44 +0200 (CEST) [thread overview]
Message-ID: <18b97163ee0fbb00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/792@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #792 was opened from rwekyes:
## Problem
On HDA codecs that have both a `Mic Jack` (external, unplugged) and an
`Internal Mic Phantom Jack` (fixed, always-on) control, the internal
microphone gets assigned `Mic Jack` as its JackControl. PipeWire monitors
this control for availability and marks the internal mic as "not available"
since the external jack is unplugged, making it invisible to browsers and
applications.
Confirmed on: Lenovo IdeaPad Slim 5 16AKP10 with Conexant SN6140 codec
(PCI SSID 17aa:38b6).
## Fix
Add a block immediately before the `HDACaptureDevice` macro call that
overrides `DeviceMicJack` to use `Internal Mic Phantom Jack` when that
control exists. Since phantom jacks always report as connected, PipeWire
correctly marks the internal mic as available.
The condition is safe for other hardware — if no `Internal Mic Phantom Jack`
control exists, the block has no effect.
## Known limitation
This fix requires UCM to be loaded for the card. On non-ACP HDA cards,
`HDA-Intel.conf` does not currently activate UCM, requiring a
machine-specific workaround. A companion fix to `HDA-Intel.conf` is needed
but has not been tested broadly enough to include here — input from
maintainers on the right approach would be welcome.
## Related
A companion kernel patch adding a pin config quirk for the SN6140 on this
hardware has been submitted to alsa-devel@alsa-project.org.
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/792
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/792.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-06-16 3:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/792@alsa-project.org>]
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=18b97163ee0fbb00-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.