Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Aaron Fan <aaronfan404@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for LG gram 16 (16Z90TR)
Date: Mon, 03 Aug 2026 09:06:13 +0200	[thread overview]
Message-ID: <8733wvbs4a.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260802055818.7389-1-aaronfan404@gmail.com>

On Sun, 02 Aug 2026 07:57:27 +0200,
Aaron Fan wrote:
> 
> The LG gram 16 (16Z90TR, SSID 1854:0554) drives its internal speakers
> through Samsung-style smart amplifiers on an ALC298. Nothing initialises
> them, so the internal speakers are silent after a cold boot, while
> headphones, HDMI and the microphones work.
> 
> A warm reset leaves the amps initialised, which masks the problem:
> rebooting gives working speakers, a cold boot does not, with a
> bit-identical kernel log in both cases. Dumping the codec's processing
> coefficients in the two states shows the difference confined to COEF
> 0x22/0x23/0x25/0x26. COEF 0x22, the amp select register written by
> alc298_samsung_v2_init_amps(), reads 0x39 when the speakers work and
> 0x00 after a cold boot. 0x39 is the second entry of
> alc298_samsung_v2_amp_desc_tbl[], so two amps are in use.
> 
> Verified with hda_model=alc298-samsung-amp-v2-2-amps, which selects the
> same fixup: the internal speakers work from a cold boot and COEF 0x22
> reads 0x39.
> 
> Signed-off-by: Aaron Fan <aaronfan404@gmail.com>

Applied to for-next branch now.  Thanks.


Takashi

      reply	other threads:[~2026-08-03  7:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02  5:57 [PATCH] ALSA: hda/realtek: Add quirk for LG gram 16 (16Z90TR) Aaron Fan
2026-08-03  7:06 ` 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=8733wvbs4a.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=aaronfan404@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --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