Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sean Rhodes <sean@starlabs.systems>
Cc: linux-kernel@vger.kernel.org, tiwai@suse.com,
	david.henningsson@canonical.com, perex@perex.cz,
	kailang@realtek.com, linux-sound@vger.kernel.org, edip@medip.dev,
	sbinding@opensource.cirrus.com, chris.chiu@canonical.com
Subject: Re: [PATCH] ALSA: hda/realtek: Fix speaker pop on Star Labs
Date: Wed, 18 Feb 2026 09:37:46 +0100	[thread overview]
Message-ID: <87seaya1lx.wl-tiwai@suse.de> (raw)
In-Reply-To: <CABtds-3QpFkofJydHXindqvABH8uT=t0p-vdMyfQDH04B4=cPQ@mail.gmail.com>

On Wed, 18 Feb 2026 09:18:42 +0100,
Sean Rhodes wrote:
> 
> From a673e45b345d494b7ec7143a8ace72faf6aa85f1 Mon Sep 17 00:00:00 2001
> From: Sean Rhodes <sean@starlabs.systems>
> Date: Tue, 17 Feb 2026 11:53:41 +0000
> Subject: [PATCH v2] ALSA: hda/realtek: Fix speaker pop on Star Labs
>  StarFighter
> To: linux-kernel@vger.kernel.org
> Cc: tiwai@suse.com,
>     perex@perex.cz,
>     sbinding@opensource.cirrus.com,
>     kailang@realtek.com,
>     chris.chiu@canonical.com,
>     edip@medip.dev,
>     david.henningsson@canonical.com,
>     linux-sound@vger.kernel.org

Those lines appear in the patch description by some reason.
I guess your mailer put it wrongly...

> On Star Labs StarFighter (Realtek ALC233/235), the internal speakers can
> emit an audible pop when entering or leaving runtime suspend.
> 
> The default Realtek shutup path powers down the codec by toggling EAPD and
> adjusting pin widget control. When the speaker path is still unmuted, this
> can lead to a pop.
> 
> Mute the speaker output paths via snd_hda_gen_shutup_speakers() before
> running the normal Realtek shutup path.

Actually, with this setup, any other shutup function is called.
That is, solely muting the outputs suffices for your machine.

> Test results: fixes the runtime PM suspend/resume speaker pop.
> Pops that can occur on cold boot (G3 exit) and around display manager
> start/shutdown are not addressed.

The cold boot might be harder to tackle, but I wonder how the display
manager start/shutdown causes the pop noise.  Does it mean a runtime
resume causes the pop noise, too?


Takashi

  reply	other threads:[~2026-02-18  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18  8:18 [PATCH] ALSA: hda/realtek: Fix speaker pop on Star Labs Sean Rhodes
2026-02-18  8:37 ` Takashi Iwai [this message]
2026-02-18  8:39   ` Takashi Iwai

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=87seaya1lx.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=chris.chiu@canonical.com \
    --cc=david.henningsson@canonical.com \
    --cc=edip@medip.dev \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sbinding@opensource.cirrus.com \
    --cc=sean@starlabs.systems \
    --cc=tiwai@suse.com \
    /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