From: Antheas Kapenekakis <lkml@antheas.dev>
To: linux-sound@vger.kernel.org, kailang@realtek.com
Cc: linux-kernel@vger.kernel.org, perex@perex.cz, tiwai@suse.com,
baojun.xu@ti.com, simont@opensource.cirrus.com,
Antheas Kapenekakis <lkml@antheas.dev>
Subject: [PATCH 0/2] ALSA: hda/realtek: Sort Ally X properly, fix Asus Z13 2025 audio
Date: Mon, 24 Feb 2025 17:10:14 +0100 [thread overview]
Message-ID: <20250224161016.439696-1-lkml@antheas.dev> (raw)
The Ally X has two quirks in the kernel currently. This is due to the
previous quirk not being sorted properly, whoopsies. Therefore, only one
has to stay. During AB testing, I found that the Lenovo quirk makes a
popping sound during boot. Therefore the better quirk is the previous one.
This also mirrors our initial testing last August, where creating that
custom quirk fixed the popping sound over re-using the existing
Lenovo TAS quirk.
Then, add the Asus Z13 2025 quirk to the list. When looking into its dsdt
file, it was found to be identical to the original Ally. Therefore, borrow
its quirk. After using the quirk, sound works properly. However, the kernel
loads the default firmware for it, resulting in subpar sound quality.
After looking into the Windows driver files, the following files were
identified to be the correct ones for it:
Playback_6.83.0/Firmware/CS35L41/RevB2/halo_cspl_RAM_revB2_29.85.0.wmfw
tunings/ASUS_GZ302EA_10431FB3_241018/10431FB3_241018_V01_A0.bin
tunings/ASUS_GZ302EA_10431FB3_241018/10431FB3_241018_V01_A0_cal.bin
tunings/ASUS_GZ302EA_10431FB3_241018/10431FB3_241018_V01_A1.bin
tunings/ASUS_GZ302EA_10431FB3_241018/10431FB3_241018_V01_A1_cal.bin
Which the kernel expects to be named as:
cirrus/cs35l41-dsp1-spk-prot-10431fb3.wmfw
cirrus/cs35l41-dsp1-spk-prot-10431fb3-r0.bin
cirrus/cs35l41-dsp1-spk-prot-10431fb3-l0.bin
cirrus/cs35l41-dsp1-spk-cali-10431fb3-r0.bin
cirrus/cs35l41-dsp1-spk-cali-10431fb3-l0.bin
where A0 corresponds to r0.
Therefore, +cc Simon Trimmer who often uploads firmware for these devices.
Antheas Kapenekakis (2):
ALSA: hda/realtek: Remove dup Ally X config
ALSA: hda/realtek: Fix Asus Z13 2025 audio
sound/pci/hda/patch_realtek.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-24 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 16:10 Antheas Kapenekakis [this message]
2025-02-24 16:10 ` [PATCH 1/2] ALSA: hda/realtek: Remove dup Ally X config Antheas Kapenekakis
2025-02-24 16:10 ` [PATCH 2/2] ALSA: hda/realtek: Fix Asus Z13 2025 audio Antheas Kapenekakis
2025-02-24 16:53 ` Stefan Binding (Opensource)
2025-02-24 17:02 ` Antheas Kapenekakis
2025-02-24 17:05 ` Antheas Kapenekakis
2025-02-24 17:38 ` Antheas Kapenekakis
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=20250224161016.439696-1-lkml@antheas.dev \
--to=lkml@antheas.dev \
--cc=baojun.xu@ti.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=simont@opensource.cirrus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox