From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: Qualcomm: add ASUS Vivobook 14 (X1407QA) to x1e80100 DMI match
Date: Wed, 18 Mar 2026 00:52:22 +0100 (CET) [thread overview]
Message-ID: <189dc602196b7000-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/725@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #725 was opened from pir0c0pter0:
The ASUS Vivobook 14 X1407QA (Snapdragon X X1-26-100, x1p42100 "Purwa" die)
reports `product_family` as `ASUS Vivobook 14` but was not matched by the
existing regex in `x1e80100.conf`, leaving audio non-functional on this device.
The audio hardware is identical to the other ASUS Snapdragon X devices already
matched by the `LENOVOT14s` block: WCD9385 codec + 2× WSA884x speakers via
SoundWire, driven by the ADSP Q6APM subsystem. The existing LENOVO-T14s.conf
configuration works correctly once the device is matched.
**DMI strings reported by the device:**
```
board_vendor: ASUSTeK COMPUTER INC.
board_name: X1407QA
product_family: ASUS Vivobook 14
product_name: ASUS Vivobook 14 X1407QA_X1407QA
```
**Change:** add `Vivobook 14` to the ASUS alternation group alongside
`Zenbook A14`, `Vivobook S 15`, and `Vivobook 16`.
Tested on Fedora 44 aarch64, kernel 6.12, alsa-lib 1.2.x.
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/725
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/725.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-03-17 23:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/725@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=189dc602196b7000-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.