* ucm2: MediaTek: add mt8189-rt1019p-rt5682s (skywalker Chromebooks)
[not found] <alsa-project/alsa-ucm-conf/pr/872@alsa-project.org>
@ 2026-10-10 22:15 ` GitHub pull_request - opened
0 siblings, 0 replies; only message in thread
From: GitHub pull_request - opened @ 2026-10-10 22:15 UTC (permalink / raw)
To: alsa-devel
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
^ permalink raw reply [flat|nested] only message in thread