From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: Intel: avs_rt5663 - Fix headset mic JackControl name
Date: Sat, 3 Oct 2026 01:41:33 +0200 (CEST) [thread overview]
Message-ID: <18dadae7c21b6b00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/866@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #866 was opened from Sha01in:
The avs rt5663 board driver registers its headset mic jack pin as
"Headset Mic", so the jack control is "Headset Mic Jack". The profiles
named "Headset Mic", which doesn't exist: PipeWire logs
'Invalid JackControl value: "Headset Mic"' and headset mic detection
can't work.
Same fix as 02f4fb7 for avs_nau8825.
Tested on a Google Pixelbook (Eve) with snd_soc_avs.obsolete_card_names=1:
the warning is gone and the Headphones, Headset Microphone and Digital
Microphone devices still come up. HP Soraka uses the same board driver.
Found and tested with help from Claude Code.
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/866
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/866.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-10-02 23:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/866@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=18dadae7c21b6b00-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.