From: eleeselees68@gmail.com
To: alsa-devel@alsa-project.org
Subject: Re: Raptor Lake external jack needs manual ALSA unmute and speakers don’t auto-mute
Date: Fri, 31 Oct 2025 03:11:06 -0000 [thread overview]
Message-ID: <176188026657.20.4961384896608372201@mailman-web.alsa-project.org> (raw)
In-Reply-To: <1872eb7cf6a44900-webhooks-bot@alsa-project.org>
This issue shows how fragile the interaction can be between the ALSA UCM layer, PipeWire/WirePlumber, and SOF firmware when hardware behavior diverges slightly from assumptions baked into existing configs. Even with modern audio stacks, if the UCM definitions don’t correctly represent headphone and speaker paths, desktop audio handling (auto-mute, port switching, jack detection) breaks down for end users.
https://geometrydashlite22.github.io
next prev parent reply other threads:[~2025-10-31 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1872eb7cf4f28300-webhooks-bot@alsa-project.org>
2025-10-29 9:15 ` Raptor Lake external jack needs manual ALSA unmute and speakers don’t auto-mute GitHub issues - opened
2025-10-31 3:11 ` eleeselees68 [this message]
2025-10-31 7:38 ` bexob46807
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=176188026657.20.4961384896608372201@mailman-web.alsa-project.org \
--to=eleeselees68@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).