From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: sof-soundwire: rt711-sdca: fix silent headphones and headset mic
Date: Thu, 9 Apr 2026 03:34:24 +0200 (CEST) [thread overview]
Message-ID: <18a48c576f585e00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/740@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #740 was opened from dankovacek:
Two related UCM fixes for rt711-sdca on sof-soundwire platforms.
**Fix 1: Headphones produce no audio**
PGA30.0 30 Playback Volume (the SOF pipeline 30 gain stage for PCM device 0)
defaults to 0 at boot, which the dBscale treats as a hardware mute. The DAPM
chain is active and audio flows on the SoundWire bus, but the pipeline passes
silence into the codec. Added to Headphones EnableSequence with value 32,32 (0 dB).
**Fix 2: Headset microphone produces no audio**
Headset Mic Switch is a DAPM gate controlling the codec mic input path. UCM never
enabled it, so the capture path was powered down regardless of the FU0F Capture
Switch state. Added on/off to Headset Enable/DisableSequence, matching the existing
pattern for Headphone Switch.
Both bugs affect any sof-soundwire platform using rt711-sdca.
Tested on Dell Precision 5480 (Intel Raptor Lake-P, sof-audio-pci-intel-tgl,
rt711-sdca on SoundWire master-0-2).
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/740
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/740.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-04-09 1:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/740@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=18a48c576f585e00-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