mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Muhtasham Nawr al-Mahmud <muhtaseem2005@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Kailang Yang <kailang@realtek.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ALSA: hda/realtek: Fix speakers on ASUS PM3406CHA
Date: Tue, 29 Sep 2026 11:27:27 +0200	[thread overview]
Message-ID: <87fqys2yrk.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260924144512.3989-1-muhtaseem2005@gmail.com>

On Thu, 24 Sep 2026 16:45:12 +0200,
Muhtasham Nawr al-Mahmud wrote:
> 
> The ASUS ExpertBook PM3406CHA uses an ALC256 codec with subsystem
> ID 1043:1664. On Linux boot, the internal speakers are silent even
> though playback is routed to the codec and the speaker pin is
> configured for output.
> 
> The codec starts with coefficient 0x10 set to 0x1d20. Writing 0x7f20
> to coefficient 0x10 immediately restores internal speaker output.
> 
> This was reproduced on the affected hardware from a fresh boot using
> hda-verb. Reducing a larger initialization sequence showed that this
> coefficient write alone is sufficient; no GPIO, EAPD, pin-control, or
> other coefficient changes are required. After applying the coefficient
> in userspace, speaker output also remains functional across suspend
> and resume.
> 
> Add a machine-specific HDA fixup that writes the required coefficient.
> 
> The fixup has been compile-tested, but could not be boot-tested because
> the affected hardware is no longer available.
> 
> Closes: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2162718
> Signed-off-by: Muhtasham Nawr al-Mahmud <muhtaseem2005@gmail.com>

The code change looks OK, so I applied this now.  Thanks.


Takashi

      reply	other threads:[~2026-09-29  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 14:45 Muhtasham Nawr al-Mahmud
2026-09-29  9:27 ` 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=87fqys2yrk.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=muhtaseem2005@gmail.com \
    --cc=perex@perex.cz \
    --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

all inboxes | Powered by JetHome®