From: Takashi Iwai <tiwai@suse.de>
To: Alex James <igotmysoul@gmail.com>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>,
Jaroslav Kysela <perex@perex.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Fix internal mic capture on ASUS ROG Flow Z13 GZ302EA
Date: Sat, 10 Oct 2026 10:03:40 +0200 [thread overview]
Message-ID: <87mrsmj82r.wl-tiwai@suse.de> (raw)
In-Reply-To: <CA+YQcmcUKi98dKYRWjg8MR6hQoxoOEvXAuSDLgUUVK-L=ge7JA@mail.gmail.com>
On Fri, 09 Oct 2026 23:19:39 +0200,
Alex James wrote:
>
> The ASUS ROG Flow Z13 GZ302EA (Realtek ALC294, SSID 1043:1fb3) exposes
> two fixed internal mic pins, 0x12 (0x90a60140) and 0x13 (0x90a60130), as
> capture sources "Internal Mic" and "Internal Mic 1". The input mux
> defaults to 0x12, but on this model 0x12 is defective: its right channel
> rails to -32768 and the left channel carries heavy noise, so out of the
> box the internal microphone records loud noise/hum.
> Pin 0x13 captures clean audio on both channels (at lower level). The
> mic array is not reachable through the AMD ACP70/PDM path either: forcing
> it on via ACPI _WOV=1 creates the dmic-codec device but all samples rail
> at -32768, so HDA is the only usable capture path.
> The existing quirk for this SSID only initializes the two CS35L41 I2C
> smart amps (speakers). Disable the broken 0x12 pin via pincfg so that
> 0x13 becomes the sole "Internal Mic" capture source, and keep the CS35L41
> initialization by chaining it in a new fixup.
> Measured on a GZ302EA (arecord, 48 kHz S16LE, identical gain):
> pin 0x12: L 47% clipped samples, R 15% clipped (railed noise)
> pin 0x13: <0.3% clipped, hum components below -65 dBFS
> The fix was validated on the target hardware without building a kernel
> by applying the same pincfg override (0x12 -> 0x40000000) through a
> boot-time HDA patch firmware (snd-hda-intel patch=). With the override
> the codec parser drops pin 0x12 entirely: the card comes up with a single
> "Internal Mic" (0x13), the Capture Source mux control disappears (single
> input is hardwired), and capture is clean and stable across boot,
> suspend/resume, and PipeWire/WirePlumber route re-applies. Note that a
> runtime hda-verb override alone is not sufficient because the bus driver
> builds its pin cache at codec registration.
> Also observed on this SSID while testing: repeated
> "ALC294: Invalid fixup type 2016568172" messages in dmesg during probe
> with the current quirk; likely unrelated but worth a look.
> Link: https://github.com/CachyOS/linux-cachyos/issues/880
> Tested-by: aic0d3r <funforfreeapps@gmail.com>
> Signed-off-by: aic0d3r <funforfreeapps@gmail.com>
The blank lines and the white spaces seem broken, possibly due to your
mailer, so the patch can't be applied correctly. Also, the
Signed-off-by tag has to be a real name (or a known identity) as it's
a legal requirement. Yet better would be to align From tag with
Signed-off-by, too.
Could you resubmit with proper blank lines and keeping the tabs/spaces
as well as Signed-off-by/From tag corrections?
thanks,
Takashi
prev parent reply other threads:[~2026-10-10 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 21:19 Alex James
2026-10-10 8:03 ` 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=87mrsmj82r.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=igotmysoul@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®