From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Add UCM2 profile for Lenovo Yoga Slim 7 15ITL05 (ALC287, subsystem 17aa:380a)
Date: Mon, 8 Jun 2026 14:22:35 +0200 (CEST) [thread overview]
Message-ID: <18b71a88e7163000-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18b71a88e6e8ce00-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #782 was opened from Ab0lish:
Lenovo Yoga Slim 7 15ITL05, sof-hda-dsp, dual-DAC issue (node 0x17 receiving both DAC1+DAC2 with no crossover)
Hardware: Lenovo Yoga Slim 7 15ITL05
Codec: Realtek ALC287, subsystem ID 0x17aa380a
Driver: sof-hda-dsp (sof-firmware)
Kernel: 6.12 (Debian 13)
Problem:
Speakers sound hollow and metallic. No UCM2 profile exists for this hardware so the generic HDA profile is used.
Root cause identified:
The codec has two DACs and two speaker pin groups (quad-speaker, Dolby Atmos):
- Node 0x14 (bass/woofers): connected to DAC2 (0x02) only ✓
- Node 0x17 (tweeters): connected to BOTH DAC1 (0x03) and DAC2 (0x02) ✗
Both DACs receive the same full-range signal with no crossover filtering, causing acoustic phase interference between the tweeter and woofer pairs. On Windows, the Dolby Atmos driver applies a crossover inside the SOF DSP.
Expected behaviour:
- Node 0x17 (tweeters, DefAssociation=0x1 Sequence=0x0) → DAC1 only
- Node 0x14 (woofers, DefAssociation=0x1 Sequence=0x1) → DAC2 only
Codec dump attached.
[alc287-yoga-slim7-codec-dump.txt](https://github.com/user-attachments/files/28707118/alc287-yoga-slim7-codec-dump.txt)
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/782
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-06-08 12:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18b71a88e6e8ce00-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=18b71a88e7163000-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.