From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: sof-soundwire: add ES9356 device files
Date: Thu, 8 Oct 2026 19:23:06 +0200 (CEST) [thread overview]
Message-ID: <18dc9dbc857add00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/869@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #869 was opened from kannoy2024:
Boards using the Everest Semiconductor ES9356 SDCA codec (for example the MECHREVO WUJIE 14SAH with AMD ACP6.3) report the component string
cfg-amp:1 hs:es9356 mic:es9356-dmic spk:es9356-spk spk:es9356
so sof-soundwire resolves the device files to es9356-spk, es9356-dmic and es9356. Those files do not exist, UCM loading fails, and WirePlumber falls back to the "stereo-fallback" profile, which only exposes the first PCM of the card (device 0, the headset output). Desktop audio is silent even though the kernel side works.
Add the three device files, using the PCM layout of these boards: device 0 headset playback, device 1 headset capture, device 2 speaker playback, device 4 internal DMIC capture.
Tested on a MECHREVO WUJIE 14SAH (Ryzen 7 H 255, ACP6.3 rev 63, ES9356 on SoundWire link 0) with mainline 7.2.9: with these files Speaker, Headphones, Internal Microphone and Headset Mic all appear in PipeWire and playback plus recording work.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=222092
Link: https://lore.kernel.org/linux-sound/20261007193038.2473068-1-mario.limonciello@amd.com/
Link: https://lore.kernel.org/linux-sound/179145019931.16888.9682263186729943710@gmail.com/
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/869
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/869.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-10-08 17:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/869@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=18dc9dbc857add00-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.