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: sof-rt5682: add support for SOF rt5682 Chromebooks
Date: Fri, 14 Aug 2026 22:38:15 +0200 (CEST)	[thread overview]
Message-ID: <18cbc67722d16d00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/832@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #832 was opened from samson1357924:

## Summary

Add UCM configuration for the `sof-rt5682` sound card used on ChromeOS devices (Dratini/hatch family and others).

The configuration includes:

- `ucm2/conf.d/sof-rt5682/` - card UCM with HiFi profile, rt5682 headset/init sequences
- `ucm2/platforms/intel-sof/` - platform detection (DMI-based, glk/cml/tgl/jsl/adl/mtl) and codec probing helpers
- `ucm2/codecs/` - speaker amp and headset codec support files (max98357a, max98360a, max98373, max98390, rt1011, rt1015, rt1015p, rt1019p, rt5682s)
- `ucm2/codecs/hda/hdmi234.conf` - HDMI device helpers (reuses the existing `hdmi.conf` macro)

## Why

ChromeOS Chromebooks using the SOF driver with the `sof-rt5682` machine driver currently have **no audio** on Linux distributions without a UCM configuration: ACP/PipeWire cannot build a usable profile (only the "off" profile is available) and the system ends up with a Dummy Output. This affects at minimum the HP Pro C640 (Dratini), the Acer Chromebook Spin 513 (Dalboz) and several other hatch-family devices.

This was previously reported at https://github.com/WeirdTreeThing/chromebook-linux-audio/issues/265 (dummy output on LTS userspace) and discussed in PipeWire MR !2946.

## Testing

Verified on an **HP Pro C640 Chromebook** (Dratini, `Google_Hatch`, Intel Comet Lake) running Ubuntu 26.04 LTS:

- alsa-lib 1.2.15.3 (UCM syntax 7)
- kernel 7.0.0-29-generic (Ubuntu official), SOF firmware 2:2:0-57864
- pipewire 1.6.2 / wireplumber 0.5.13

Result: HiFi profile available and active, internal speakers (PCM 5), headphone jack (PCM 0, auto-switch works), DMIC capture and HDMI 1/2/3 all working. No Dummy Output, no WirePlumber errors.

All files are byte-identical to the standalone branch of WeirdTreeThing/alsa-ucm-conf-cros (verified via md5).

The UCM validator CI should cover the syntax; no alsa-info hardware emulation was added since the current `ucm-validator2` used by CI performs static verification.

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

           reply	other threads:[~2026-08-14 20:39 UTC|newest]

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