From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: codecs: add rt721+rt1320 companion init configuration
Date: Sun, 6 Sep 2026 12:48:34 +0200 (CEST) [thread overview]
Message-ID: <18d2b5a27bb7b100-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/852@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #852 was opened from sri-sandeep108:
Add `ucm2/codecs/rt721+rt1320/init.conf` to support machines using the Realtek RT721 + RT1320 companion amplifier combination on `sof-soundwire`.
### Problem
When the kernel SoundWire driver detects RT721 and RT1320, it emits the combined component token `spk:rt721+rt1320`.
In `sof-soundwire.conf`, `SpeakerCodecFile` remains `rt721+rt1320`. When attempting to include `/codecs/${var:SpeakerCodecFile}/init.conf`, UCM fails because `/usr/share/alsa/ucm2/codecs/rt721+rt1320/init.conf` does not exist, causing the entire soundcard use case configuration import to fail (`-2`).
### Solution
Provide `ucm2/codecs/rt721+rt1320/init.conf`. RT721 initialization is handled through `codecs/rt721/init.conf` (via the headset branch), and RT1320 mixer controls are managed directly by `sof-soundwire/rt721+rt1320.conf`.
### Verification
Tested on Lenovo Yoga Pro 7 15IPH11 (`83SN`, Intel Core Ultra Panther Lake with RT721 + RT1320). UCM imports successfully, exposing HiFi playback on speakers, headphones, and multi-channel DMIC capture.
Closes: https://github.com/alsa-project/alsa-ucm-conf/issues/851
Fixes: 196b79b04126 ("sof-soundwire: add companion amp config with rt721 and rt1320")
Signed-off-by: Sri Sandeep Sakthivel <sandyorton7@gmail.com>
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/852
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/852.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-09-06 10:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/852@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=18d2b5a27bb7b100-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