From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Unable to attach an LED to headphones without HW mute ALSA Control
Date: Tue, 18 Mar 2025 15:56:39 +0100 (CET) [thread overview]
Message-ID: <182ded85b0661d00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <182ded85af275c00-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #527 was opened from stefdb:
I have a laptop with a CS42L43 Codec which supplies the Headphone Jack.
I'm trying to attach the mute state of the Headphones to the Speaker LED.
However, the issue is that the CS42L43 does not possess a Hardware Mute ALSA Control which could be attached to the Speaker LED.
I first tried to use the Volume Control to attach to the LED, however, that was a non-starter because the Mute is software controlled, and thus muting headphones did not touch the Volume Control.
I then tried to add a new control using cset-new, and link it to the Headphones device ([0001-sof-soundwire-Attach-cs42l43-Headphone-Switch-to-spe.patch](https://github.com/user-attachments/files/19321741/0001-sof-soundwire-Attach-cs42l43-Headphone-Switch-to-spe.patch)), and whilst that worked with the LED, the mute no longer actually muted the Headphone, since there was now a "real" control to set the mute which did not actually mute the Device.
Other things I have tried include mapping the Volume control as a Switch, but that does not work, I assume, because the switch control needs to be Boolean.
Is there a way to create a new control to track the LED status, whilst also ensuring that the Headphones still mute?
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/527
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2025-03-18 14:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <182ded85af275c00-webhooks-bot@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=182ded85b0661d00-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