From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: Qualcomm: x1e80100: Surface11-HiFi: disable DP RX mixer routes by default
Date: Fri, 23 Oct 2026 19:30:47 +0200 (CEST) [thread overview]
Message-ID: <18e138dc03d66500-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/889@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #889 was opened from ramonjesusmiranda-debug:
SectionVerb in `Surface11-HiFi.conf` unconditionally enables the `DISPLAY_PORT_RX_0` and `DISPLAY_PORT_RX_1` Audio Mixer routes (`MultiMedia3` and `MultiMedia4`), and `SectionDevice."HDMI0"` / `"HDMI1"` lack a `DisableSequence`.
When PipeWire / WirePlumber starts or probes the card with no external DisplayPort monitor attached, opening `MultiMedia3` / `MultiMedia4` triggers 44 to 54 errors in `dmesg` on every start/restart:
```
hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22
```
Keep the DisplayPort mixer routes disabled (`0`) in `SectionVerb` and add the matching `DisableSequence` to `HDMI0` and `HDMI1` so they are only enabled when an external DisplayPort audio sink is actually selected.
Tested on a Microsoft Surface Pro 11 OLED (X1E80100).
Signed-off-by: Ramón Jesús Miranda <ramonjesusmiranda@gmail.com>
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/889
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/889.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-10-23 17:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/889@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=18e138dc03d66500-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.