From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: sof-soundwire: support dual-codec cs42l43-spk + cs35l56 speakers
Date: Thu, 16 Apr 2026 06:29:23 +0200 (CEST) [thread overview]
Message-ID: <18a6bbf401b00100-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/747@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #747 was opened from pma1:
Some machines have both cs42l43 and cs35l56 speaker amps on SoundWire. Only the first spk: tag in CardComponents was handled, leaving the second codec without init, control remap, or mute LED.
Detect cs35l56 directly in CardComponents instead of SpeakerCodec1, and when cs42l43-spk is also present, initialise both codecs and extend the mute LED remap to cover all amp channels.
Toggle Speaker Switch in both device confs and set up cross-codec routing and mute tracking as needed.
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/747
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/747.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-04-16 4:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/747@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=18a6bbf401b00100-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.