Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: " (alsa-devel@alsa-project.org)" <alsa-devel@alsa-project.org>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Subject: Re: Fixed Headphone noise issue for Dell QCM1255
Date: Thu, 09 Jul 2026 11:13:24 +0200	[thread overview]
Message-ID: <875x2o4jbf.wl-tiwai@suse.de> (raw)
In-Reply-To: <34b990cb56914148ba02fa8e9d176479@realtek.com>

On Thu, 09 Jul 2026 09:27:14 +0200,
Kailang wrote:
> 
> Hi Takashi,
> 
> This platform booted with Ubuntu 24.04 with Pipewire audio server. So, it has pop
> noise with headphone. But it's normal with Pulseaudio server.
> This patch was the workaround. Connect the headphones to DAC 0x2.
> The popping sound will disappear.
> 
> This solution was approved by Dell.
> 
> Thanks.
> Kailang

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-07-09  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  7:27 Fixed Headphone noise issue for Dell QCM1255 Kailang
2026-07-09  9:13 ` Takashi Iwai [this message]

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=875x2o4jbf.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kailang@realtek.com \
    --cc=linux-sound@vger.kernel.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