All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Saim Masood <s.m.saim074@gmail.com>
Cc: tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Fix speakers on ASUS ExpertBook PM3606CHA
Date: Mon, 28 Sep 2026 14:37:26 +0200	[thread overview]
Message-ID: <87a4p15z7d.wl-tiwai@suse.de> (raw)
In-Reply-To: <065927dd-cabf-449a-992d-64887eedda01@gmail.com>

On Sat, 19 Sep 2026 02:07:09 +0200,
Saim Masood wrote:
> 
> The internal speakers of the ASUS ExpertBook PM3606CHA (Realtek ALC256,
> PCI SSID 1043:3501) stay silent with the default codec setup, and the
> headphone jack is not detected either.  The codec needs COEF values that
> differ from its power-on defaults: COEF 0x10, 0x16, 0x35, 0x37 and 0x57
> on NID 0x20 have to be set to the values used by the Windows driver.
> Toggling the codec GPIOs, and the existing ALC256 fixups alone, make no
> difference.
> 
> Apply the COEFs from a new fixup at the INIT action, so that they are
> restored after resume as well.  Chain to ALC256_FIXUP_ASUS_MIC_NO_PRESENCE
> to keep the headset mic and the jack detection working, which the
> fallback pin quirk provided before for this machine.
> 
> The COEF values were found by the reporter of the Ubuntu bug below, who
> compared the codec state against the one under the Windows driver.
> 
> Tested on an ASUS ExpertBook PM3606CHA (BIOS PM3606CHA.304) with the
> change applied to v7.2.5: with this fixup alone, the speakers, the
> headphones with jack detection, and the headset mic all work, also
> after suspend and resume.
> 
> Link: https://bugs.launchpad.net/bugs/2167288
> Signed-off-by: Saim Masood <s.m.saim074@gmail.com>

Applied to for-next branch.  Thanks.


Takashi

      reply	other threads:[~2026-09-28 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  0:07 [PATCH] ALSA: hda/realtek: Fix speakers on ASUS ExpertBook PM3606CHA Saim Masood
2026-09-28 12:37 ` 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=87a4p15z7d.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=s.m.saim074@gmail.com \
    --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 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.