From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2/HDA/HiFi-mic.conf: hardcoded "Mic Jack" breaks mic capture on HDA devices without that control
Date: Fri, 5 Jun 2026 05:05:22 +0200 (CEST) [thread overview]
Message-ID: <18b6106320458c00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18b61063201a0f00-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #777 was opened from qaqland:
On Acer S40-54, there is no "Input Source" enum control, so `If.micsetup` falls through to the `True` branch. However, the actual jack detection control is `Headset Mic Jack` not `Mic Jack`. As a result, the microphone is registered with no valid JackControl.
I applied this [change](https://github.com/deepin-community/alsa-ucm-conf/pull/9) on deepin and it works correctly on this Acer S40-54. But I'm not sure if this change is correct, and don't have other HDA devices to verify.
To avoid interference from the distribution, I confirm the above issue with the Fedora live system and generated alsa-info.
[alsa-info.txt](https://github.com/user-attachments/files/28621633/alsa-info.txt)
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/777
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-06-05 3:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18b61063201a0f00-webhooks-bot@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=18b6106320458c00-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox