All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: codecs: tas2783: use the real speaker switch names
Date: Sat, 17 Oct 2026 12:09:28 +0200 (CEST)	[thread overview]
Message-ID: <18df494b8c89ce00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/886@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #886 was opened from gjouret:

The tas2783-sdw driver registers its per-amp speaker switches as
'Left Spk Switch', 'Right Spk Switch', 'Left Spk2 Switch' and
'Right Spk2 Switch' (amixer shows them as the simple controls
'Left Spk' ... with the 'Switch' suffix stripped). The BootSequence
uses the simple names, which match no control element, so the
csets fail and the amps keep whatever state they had:

  $ amixer -c sofsoundwire cget name='Left Spk'
  amixer: Cannot find the given element from control sysdefault:0
  $ amixer -c sofsoundwire cget name='Left Spk Switch'
  numid=18,iface=MIXER,name='Left Spk Switch'
    ...
    : values=on   (output trimmed)

Tested on an HP OmniBook Ultra 14 (board 8EB4, four TAS2783 on two
SoundWire links), kernel 7.2.5: with the full names all four
speakers are switched on at card init.

Fixes: 182d0122a7d9 ("ucm2: sof-soundwire: Add tas2783 support")
Signed-off-by: Guido Jouret <gjouret@gmail.com>

Request URL   : https://github.com/alsa-project/alsa-ucm-conf/pull/886
Patch URL     : https://github.com/alsa-project/alsa-ucm-conf/pull/886.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

           reply	other threads:[~2026-10-17 10:10 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alsa-project/alsa-ucm-conf/pr/886@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=18df494b8c89ce00-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.