public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Marios Levogiannis <marios.levogiannis@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek - Fix microphone noise on ASUS TUF B550M-PLUS
Date: Mon, 30 May 2022 08:22:49 +0200	[thread overview]
Message-ID: <87r14by1xi.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220529223524.9057-1-marios.levogiannis@gmail.com>

On Mon, 30 May 2022 00:35:24 +0200,
Marios Levogiannis wrote:
> 
> Set microphone pins 0x18 (rear) and 0x19 (front) to VREF_50 to fix the
> microphone noise on ASUS TUF B550M-PLUS which uses the ALCS1200A codec.
> The initial value was VREF_80.
> 
> The same issue is also present on Windows using both the default Windows
> driver and all tested Realtek drivers before version 6.0.9049.1. Comparing
> Realtek driver 6.0.9049.1 (the first one without the microphone noise) to
> Realtek driver 6.0.9047.1 (the last one with the microphone noise)
> revealed that the fix is the result of setting pins 0x18 and 0x19 to
> VREF_50.
> 
> This fix may also work for other boards that have been reported to have
> the same microphone issue and use the ALC1150 and ALCS1200A codecs, since
> these codecs are similar and the fix in the Realtek driver on Windows is
> common for both. However, it is currently enabled only for ASUS TUF
> B550M-PLUS as this is the only board that could be tested.

Could you resubmit with your Signed-off-by tag?  It's mandatory.


thanks,

Takashi

  reply	other threads:[~2022-05-30  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 22:35 [PATCH] ALSA: hda/realtek - Fix microphone noise on ASUS TUF B550M-PLUS Marios Levogiannis
2022-05-30  6:22 ` Takashi Iwai [this message]
2022-05-30  7:41   ` Marios Levogiannis
2022-05-30 12:10     ` Takashi Iwai

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=87r14by1xi.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marios.levogiannis@gmail.com \
    --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