All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: sof-soundwire: cs42l45 silent on boot when headphones already plugged in
Date: Mon, 17 Aug 2026 03:15:20 +0200 (CEST)	[thread overview]
Message-ID: <18cc72bf13901100-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18cc72bf135d9a00-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #833 was opened from kafatekactual:

# sof-soundwire: cs42l45 silent on boot when headphones already plugged in

## Describe the bug

On Dell XPS 16 DA16260 (`sof-soundwire`, headset codec `cs42l45`), rebooting **with headphones already plugged in** yields no sound from headphones or speakers. The desktop correctly shows headphones as plugged in and selected. Unplugging and replugging the jack immediately restores headphone audio.

This matches the class of bug in https://github.com/alsa-project/alsa-ucm-conf/issues/804 (`cs42l43` missing Headphone Switch in UCM EnableSequence). The shipped `cs42l45` device section has **no EnableSequence / DisableSequence** at all — only jack + mixer element names — so a boot with the jack already inserted never runs a path-enable sequence.

Current `/usr/share/alsa/ucm2/sof-soundwire/cs42l45.conf` (alsa-ucm-conf 1.2.16.1):

```
SectionDevice."Headphones" {
	Comment "Headphones"

	Value {
		PlaybackPriority 200
		PlaybackPCM "hw:${CardId},0"
		PlaybackMixer "default:${CardId}"
		PlaybackMixerElem "cs42l45 Headphone"
		JackControl "cs42l45 OT 43 Headphone Jack"
	}
}
```

`alsa.components` on this machine:

```
HDA:80862822,80860101,00100000  cfg-amp:4 iec61937-pcm:7,6,5 hs:cs42l45 mic:cs42l45-dmic spk:cs35l56
```

PipeWire selects `HiFi__Headphones__sink` and the Headphones port is `available`. After a replug, `cs42l45 Headphone Playback Switch` is `on,on`. We did not capture mixer state during the silent boot (reporting after recovery).

## Steps to reproduce

1. Plug in 3.5 mm headphones.
2. Reboot.
3. Play audio. UI shows headphones selected; no sound on headphones or speakers.
4. Unplug and replug headphones → sound returns on headphones.

## Hardware / software

| Item | Value |
|------|--------|
| Machine | Dell Inc. XPS 16 DA16260 (board 0H2HX9) |
| Card | sof-soundwire / `snd_soc_sof_sdw` |
| Codec | cs42l45 + cs35l56 amps + cs42l45-dmic |
| Kernel | linux 7.1.8.arch1-3 |
| alsa-ucm-conf | 1.2.16.1-1 |
| PipeWire | 1.6.8 |
| WirePlumber | 0.5.15 |
| Distro | Omarchy 4.0.0-1 (Arch) |

## Expected

Boot with headphones inserted should enable the headphone analog path (same as a jack-insert event) so playback is audible without unplug/replug.

## Suggested direction

Add Enable/Disable sequences (and `PlaybackSwitch` if appropriate) for `cs42l45 Headphone Playback Switch` / related FU/OT controls, analogous to the `cs42l43` fix discussed in #804, so UCM applies the path when the Headphones device is enabled at session start — not only on a hotplug edge.

Issue URL     : https://github.com/alsa-project/alsa-ucm-conf/issues/833
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

           reply	other threads:[~2026-08-17  1:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <18cc72bf135d9a00-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=18cc72bf13901100-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.