From: GitHub pull_request - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: sof: hdmi: Add 5.1 and 7.1 variants of HDMI devices when using IPC4
Date: Fri, 31 Oct 2025 12:04:51 +0100 (CET) [thread overview]
Message-ID: <18738e9e3bb5d800-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/633@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #633 was edited from ujfalusi:
Systems using IPC4 can support up to 8 channels of audio (and passthrough) via HDMI.
In UCM the default PlaybackChannels is set to 2, which prevents users from selecting multichannel configurations.
When probing the card, Pipewire will drop configurations that are not supported either by the PCM device or based on ELD information.
This means that if the equipment supports only stereo then the 5.1 and 7.1 variants should not be visible, if the equipment is 5.1 capable, then only the 7.1 variant is removed.
The kernel will refine the PCM parameters based on the ELD information as wall when https://lore.kernel.org/linux-sound/20251029073600.13624-1-peter.ujfalusi@linux.intel.com/ is applied.
@perexg, @wtay, @ford-prefect, is this something which can help PW and user space to handle the HDMI a bit better with SOF?
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/633
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/633.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
prev parent reply other threads:[~2025-10-31 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alsa-project/alsa-ucm-conf/pr/633@alsa-project.org>
2025-10-31 11:04 ` ucm2: sof: hdmi: Add 5.1 and 7.1 varriants of HDMI devices when using IPC4 GitHub pull_request - opened
2025-10-31 11:04 ` GitHub pull_request - edited [this message]
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=18738e9e3bb5d800-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;
as well as URLs for NNTP newsgroup(s).