From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: MediaTek: mt8391-evk: Set the DP audio muxes in the verb
Date: Tue, 3 Nov 2026 05:55:37 +0100 (CET) [thread overview]
Message-ID: <18e470088db49f00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/902@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #902 was opened from tzuhsien-kao:
The DP output device added in 8048d93 needs DPTX_OUT_MUX at Connect and HDMI_CH1_MUX at CH1, but these controls are only set in the BootSequence. The BootSequence runs from alsactl init and its values are saved in the ALSA state file. On later boots alsa-restore replays the saved state, so the controls keep their stale values.
A stale DPTX_OUT_MUX (Disconnect) makes the PCM hw:CardId,5 fail to open. The whole HiFi profile then fails to probe and PipeWire exposes only a dummy output and no inputs. A stale HDMI_CH1_MUX (CH0) makes the right DP channel take its data from CH0, so Front Right is silent.
Set HDMI_CH0_MUX, HDMI_CH1_MUX and DPTX_OUT_MUX from the verb EnableSequence so they are applied each time the profile is activated, as mt8195_demo does since 445c079.
Fixes: 8048d93 ("ucm2: MediaTek: mt8391-evk: Add DisplayPort output audio support")
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/902
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/902.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-11-03 4:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/902@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=18e470088db49f00-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.