Alsa-Devel Archive on 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: MediaTek: add mt8189-rt1019p-rt5682s (skywalker Chromebooks)
Date: Sun, 11 Oct 2026 00:15:21 +0200 (CEST)	[thread overview]
Message-ID: <18dd4ad75c479c00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/872@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #872 was opened from zoan37:

Adds a UCM profile for MT8189 (Kompanio 540) Chromebooks with RT1019P speaker amps and an RT5682S headset codec (card `mt8189_1019_rt5682s`, the "skywalker" family; tested on quigon, the Lenovo IdeaPad Slim 3 Chromebook).

- Speaker, headphones, internal DMIC and headset mic.
- All DPCM front ends are routed in the BootSequence: PipeWire's ACP opens every PCM while it probes the profile, and these front ends refuse hw_params until they're routed to a back end (routing them in the devices' EnableSequence made ACP drop the whole profile).
- HDMI (`hw:CardId,6`, through an HDMI bridge on PCM 0) and DisplayPort over USB-C (`hw:CardId,5`, via the `TDM Playback Route` demux) are only added when the machine driver created their jacks, the same pattern as the recent mt8391-evk DisplayPort change.

Tested with linux-next plus the posted MT8189 series (the board DTS isn't upstream yet): speaker, headphones, both mics, HDMI and USB-C DisplayPort audio, starting from cleared mixer routes and across reboots.

`alsa-info.sh` output for the UCM validator: https://gist.github.com/zoan37/b611da4f1e569613f176c33edbe34a01

The profile was written with help from an AI assistant (Claude); I tested it on the hardware and reviewed it.

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

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

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