From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: rt721: capture switches (FU0F/FU1E) default to OFF on AMD SoundWire
Date: Mon, 6 Jul 2026 15:46:11 +0200 (CEST) [thread overview]
Message-ID: <18bfb75896a98300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18bfb758969b4d00-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #805 was edited from BenSharir:
The RT721 codec capture switches for ASUS ProArt PX13 (AMD SoundWire) default to OFF, which mutes the DMIC microphone.
**Symptom**: Microphone records silence despite being selected in system settings.
**Cause**: The following ALSA mixer controls are off by default:
- `rt721 FU0F Capture Switch`: off,off
- `rt721 FU1E Capture Switch`: off,off,off,off
**Proposed Fix**: The UCM profile should enable these switches by default in the HiFi verb.
**Hardware**:
- Laptop: ASUS ProArt PX13 HN7306EAC
- Chipset: AMD ACP70 SoundWire
- Codec: Realtek RT721
- Card components: `cfg-amp:2 mic:acp-dmic cfg-mics:1 hs:rt721`
**System Info**:
- OS: Fedora 44
- Kernel: 7.0.13-200.fc44.x86_64
- alsa-ucm: 1.2.16.1-1.fc44
**Workaround**:
```bash
amixer -c 1 cset name='rt721 FU0F Capture Switch' on,on
amixer -c 1 cset name='rt721 FU1E Capture Switch' on,on,on,on
```
**Verification**:
```bash
# Record 5 seconds of audio
timeout 5 arecord -D hw:amdsoundwire,4 -f S32_LE -r 48000 -c 2 /tmp/mic-test.wav
# Play back
aplay /tmp/mic-test.wav
```
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/805
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2026-07-06 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18bfb758969b4d00-webhooks-bot@alsa-project.org>
2026-07-06 13:46 ` GitHub issues - edited [this message]
[not found] <18bfb79a0ba56500-webhooks-bot@alsa-project.org>
2026-07-06 13:50 ` rt721: capture switches (FU0F/FU1E) default to OFF on AMD SoundWire GitHub issues - edited
[not found] <18bfb6a4d2407600-webhooks-bot@alsa-project.org>
2026-07-06 13:33 ` GitHub issues - opened
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=18bfb75896a98300-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