From: Takashi Iwai <tiwai@suse.de>
To: Gunal Seenivasagan <gunal2002@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 v2] ALSA: hda/realtek: Add quirk for Infinix INBOOK X3 Slim
Date: Sun, 26 Jul 2026 16:11:32 +0200 [thread overview]
Message-ID: <87mrvdalij.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260726085715.229802-1-gunal2002@gmail.com>
On Sun, 26 Jul 2026 10:57:11 +0200,
Gunal Seenivasagan wrote:
>
> The Infinix INBOOK X3 Slim (ALC269VB, subsystem 0x2782:0250) has its
> internal speakers wired to pin 0x1b, but the BIOS pin configuration
> table declares 0x1b as "no physical connection" (0x411111f0). It instead
> declares pin 0x14 as the internal speaker, although nothing is connected
> to 0x14.
>
> As a result the internal speakers are silent under Linux while the
> headphone jack works correctly. The codec output path to 0x14 is fully
> open (DAC assigned and streaming, mixer and pin unmuted, EAPD asserted),
> so the failure is silent with no error reported. The speakers work under
> Windows, where the vendor driver supplies its own pin table.
>
> Add a fixup that disables the unconnected pin 0x14 and declares pin
> 0x1b as the internal speaker.
>
> Reusing the existing ALC269VC_FIXUP_INFINIX_Y4_MAX was tried first, since
> it also remaps 0x1b to an internal speaker. It is not sufficient here: it
> leaves 0x14 declared, so autoconfig finds two line_outs
>
> line_outs=2 (0x14/0x1b/0x0/0x0/0x0) type:speaker
>
> and binds the primary "Speaker" control to the unconnected pin 0x14 while
> demoting the working speaker at 0x1b to "Bass Speaker". Audio is audible
> that way, but the volume and mute controls a desktop actually uses end up
> attached to a pin that is not wired to anything. Disabling 0x14 is what
> produces a single correct Speaker output.
>
> Verified on the affected machine: with the corrected pin
> configuration the driver's autoconfig reports
>
> line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:speaker
>
> both channels play, headphone auto-mute switches correctly in both
> directions, and audio survives codec runtime suspend (D3) and resume.
>
> Signed-off-by: Gunal Seenivasagan <gunal2002@gmail.com>
> ---
> v2: No functional change. Corrected the author and Signed-off-by lines to
> my full name, as requested by Takashi.
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-07-26 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 14:02 [PATCH] ALSA: hda/realtek: Add quirk for Infinix INBOOK X3 Slim Gunal S
2026-07-26 7:54 ` Takashi Iwai
2026-07-26 8:57 ` [PATCH v2] " Gunal Seenivasagan
2026-07-26 14:11 ` 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=87mrvdalij.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gunal2002@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