From: Takashi Iwai <tiwai@suse.de>
To: Aleksandrs Vinarskis <alex@vinarskis.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Asus Zephyrus G14 2025 using CS35L56, fix speakers
Date: Mon, 19 Jan 2026 09:09:17 +0100 [thread overview]
Message-ID: <87sec281n6.wl-tiwai@suse.de> (raw)
In-Reply-To: <XqnvvlnwyZf0b1xnGu9hIpjn5vpqNYWkSLQA06lEc0AI2Qp04CY9TfAy72LA_L4ONvU9ZkYSKWiTPx0xhpxkqRtx9gQRDwz9F-tX_22jspQ=@vinarskis.com>
On Sun, 18 Jan 2026 18:07:17 +0100,
Aleksandrs Vinarskis wrote:
>
>
>
>
>
>
> On Tuesday, January 13th, 2026 at 13:24, Takashi Iwai <tiwai@suse.de> wrote:
>
> >
> >
> > On Mon, 12 Jan 2026 01:06:37 +0100,
> > Aleksandrs Vinarskis wrote:
> >
> > > Just like GA403U, this GA403W needs to remap woofers to DAC1. Similarly to
> > > other Asus devices, headphones/headset MIC is not working, however the pin
> > > config alone is not enough to fix it.
> > >
> > > From Windows dump of GA403W:
> > > 0x12, 0x90a60140 # Correctly set by codec out of the box
> > > 0x13, 0x90a60550
> > > 0x14, 0x90170510
> > > 0x17, 0x90170120 # Correctly set by codec out of the box
> > > 0x19, 0x03a11050 # Set by ALC285_FIXUP_ASUS_GA403U_HEADSET_MIC
> > > 0x1a, 0x411115F0
> > > 0x1b, 0x03a11c30 # Set by ALC285_FIXUP_ASUS_GA403U_HEADSET_MIC
> > > 0x1d, 0x40663A45 # Correctly set by codec out of the box
> > > 0x21, 0x03211430
> > >
> > > Even with all the values set, MIC of the jack is not detected. Until a
> > > complete solution is found, set ALC285_FIXUP_ASUS_GA403U_HEADSET_MIC
> > > for GA403W which fixes audio volume control for woofers. No need to
> > > create new quirk with missing pin config just yet, since its not
> > > making the situation better.
> > >
> > > Signed-off-by: Aleksandrs Vinarskis alex@vinarskis.com
> > > ---
> > > As per commit description, enable quirk to fix woofers.
> >
> >
> > Thanks, applied now.
>
> Thanks, I see it now landed in linux master. If possible, it would be nice to have it in 6.18, 6.17 stable as well - would you like me to submit backport separately, or would you be able to pick it directly?
I hope AUTOSEL would pick it up, but if you want to be sure, just ask
Greg & co (via stable ML) to suggest the upstream (Linus tree) commit
id to cherry-pick and tell which stable kernels to be backported.
And, if the fix is intended for stable kernels, at the next time, just
put "Cc: <stable@vger.kernel.org>" line around your Signed-off-by
line in the patch.
thanks,
Takashi
prev parent reply other threads:[~2026-01-19 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 0:06 [PATCH] ALSA: hda/realtek: Add quirk for Asus Zephyrus G14 2025 using CS35L56, fix speakers Aleksandrs Vinarskis
2026-01-13 12:24 ` Takashi Iwai
2026-01-18 17:07 ` Aleksandrs Vinarskis
2026-01-19 8:09 ` 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=87sec281n6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alex@vinarskis.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 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.