mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: fixca <jaehoon1744@dankook.ac.kr>
To: shumingf@realtek.com
Cc: broonie@kernel.org, Vijendar.Mukunda@amd.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	JaeHoon Kim <jaehoon1744@dankook.ac.kr>
Subject: Re: [PATCH RFC 0/1] ASoC: rt1320: LG gram 16Z95U speaker works with the BIOS init values
Date: Thu, 12 Nov 2026 13:46:24 +0900	[thread overview]
Message-ID: <20261112044624.4395-1-jaehoon1744@gmail.com> (raw)
In-Reply-To: <20261112040143.6945-1-jaehoon1744@gmail.com>

From: JaeHoon Kim <jaehoon1744@dankook.ac.kr>

Hi Shuming,

Please disregard this RFC. The BIOS init values are not needed: the
stock rt1320 driver works on this machine.

While narrowing the register groups down (after the Sashiko review,
which correctly pointed out that my table dropped the two PDE23 entries
and that 0x1000db15-0x1000db23 is the same command list in a different
order, not an L/R swap), the baseline with no BIOS values also played
sound. I then retested the unmodified v7.2.15 rt1320 driver, with only
the two ACP patches Mark applied, in three boot scenarios:

  boot                                   amp func_status   speaker
  cold boot (power fully removed)        0x61              works
  warm reboot Linux -> Linux             0x41              works
  Windows (speaker used) -> warm reboot  0x43              works

v7.2.15 has no audio related changes compared to v7.2.14, so I cannot
explain the silence I saw earlier on v7.2.14. It is no longer
reproducible; it may have been a stale amplifier state left over from
my earlier experiments. Once (also no longer reproducible) the RT1320
read back 0x81 for every register after a warm reboot, which only a
full power removal cleared. I will report back if either problem shows
up again.

The remaining open point is the one from before: no DSP firmware / RAE
files are loaded for this machine, so the speaker protection set up on
Windows is not active on Linux. If Realtek can provide those files for
the LG gram 16Z95U (SSID 1854:056c), I am happy to test them.

Sorry for the noise.

Thanks,
JaeHoon Kim

      parent reply	other threads:[~2026-11-12  4:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  1:39 [PATCH RFC v2 0/2] ASoC: amd: SoundWire audio for LG gram 16Z95U (rt713 + rt1320), speaker still silent fixca
2026-11-11  1:39 ` [PATCH RFC v2 1/2] ASoC: amd: acp: Add ACP70 ACPI flag override for LG gram 16Z95U fixca
2026-11-11  1:57   ` Mukunda,Vijendar
2026-11-11  1:39 ` [PATCH RFC v2 2/2] ASoC: amd: acp70: Add rt713 + rt1320 SoundWire machine " fixca
2026-11-11  2:05   ` Mukunda,Vijendar
2026-11-11  1:55 ` [PATCH RFC v2 0/2] ASoC: amd: SoundWire audio for LG gram 16Z95U (rt713 + rt1320), speaker still silent Mukunda,Vijendar
2026-11-11  2:20 ` Mark Brown
2026-11-12  4:01 ` [PATCH RFC 0/1] ASoC: rt1320: LG gram 16Z95U speaker works with the BIOS init values fixca
2026-11-12  4:01   ` [PATCH RFC 1/1] ASoC: rt1320: Use the BIOS init values on LG gram 16Z95U fixca
2026-11-12  4:46   ` fixca [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=20261112044624.4395-1-jaehoon1744@gmail.com \
    --to=jaehoon1744@dankook.ac.kr \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=shumingf@realtek.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®