From: Takashi Iwai <tiwai@suse.de>
To: chester.a.unal@arinc9.com,
"Chester A. Unal via B4 Relay"
<devnull+chester.a.unal.arinc9.com@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kailang Yang <kailang@realtek.com>,
Stefan Binding <sbinding@opensource.cirrus.com>,
Simon Trimmer <simont@opensource.cirrus.com>,
Joshua Grisham <josh@joshuagrisham.com>,
alexander.scholten@xpedite-tech.com,
dwayne.dupreez@xpedite-tech.com, zenon@xpedite-tech.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Limit Internal Microphone boost for ALC3246
Date: Tue, 11 Mar 2025 11:39:52 +0100 [thread overview]
Message-ID: <87tt7zyhon.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250309-for-sound-alc256-dell-v1-1-aacd84853907@arinc9.com>
On Sun, 09 Mar 2025 13:39:36 +0100,
Chester A. Unal via B4 Relay wrote:
>
> From: "Chester A. Unal" <chester.a.unal@arinc9.com>
>
> Internal Microphone is too loud on Dell Latitude 5490, Dell Device
> [1028:0816], which has got ALC3246. I suppose this is the case for all
> devices with ALC3246 which is ALC256 for Dell devices. Therefore, limit the
> Internal Microphone boost for ALC3246. Change
> ALC255_FIXUP_DELL1_MIC_NO_PRESENCE to
> ALC255_FIXUP_DELL1_LIMIT_INT_MIC_BOOST which includes the former fixup.
>
> Signed-off-by: Chester A. Unal <chester.a.unal@arinc9.com>
Thanks for the patch.
The code replaces the quirk entry for a pin-quirk table, and it
implies that this change will influence on all models that have this
pin table pattern, which is a bit risky to change.
IMO, a safer option would be to add an explicit PCI SSID quirk entry
for your device pointing to ALC255_FIXUP_DELL1_LIMIT_INT_MIC_BOOST.
> ---
> I don't know ALSA or the Intel HDA specification very well so feel free to
> correct any incorrect information in the patch log.
>
> I experience another issue with this laptop that is also there on ALC3204.
> Headphones output loops back to Headset Microphone. So if I record with
> this microphone, sysystem audio is recorded as well. I have tried a fair
> share of fixups by compiling snd-hda-codec-realtek.ko with different fixups
> applied for "0x10ec0256, 0x1028", replacing the existing module in
> /lib/modules, and then rebooting.
The "headphone" mic means to use the pin used for the headphone output
as the mic input. If turned on, the pin usage is switched from the
output to the input, hence no playback from there any longer.
And, a headphone can be indeed used physically as a mic (although the
tone is very soft) -- so it's the expected behavior.
OTOH, "headset" mic is different; it has both the headset output pin
and the headset mic pin that work individually.
> ALC2XX_FIXUP_HEADSET_MIC makes Headset Microphone appear unplugged. But I
> can see on the OS that it detects voice, so, it works. When it appears
> unplugged, Headphones output won't loop back to it. This fixup also makes
> Speakers appear unavailable and makes Microphone disappear, as
> ALC255_FIXUP_DELL1_MIC_NO_PRESENCE won't apply anymore.
If the headset isn't detected by plugging to the headset jack, that's
a bug to be fixed. Please elaborate the behavior.
thanks,
Takashi
prev parent reply other threads:[~2025-03-11 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 12:39 [PATCH] ALSA: hda/realtek: Limit Internal Microphone boost for ALC3246 Chester A. Unal via B4 Relay
2025-03-09 12:41 ` Chester A. Unal
2025-03-11 10:39 ` 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=87tt7zyhon.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alexander.scholten@xpedite-tech.com \
--cc=chester.a.unal@arinc9.com \
--cc=devnull+chester.a.unal.arinc9.com@kernel.org \
--cc=dwayne.dupreez@xpedite-tech.com \
--cc=josh@joshuagrisham.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sbinding@opensource.cirrus.com \
--cc=simont@opensource.cirrus.com \
--cc=tiwai@suse.com \
--cc=zenon@xpedite-tech.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