From: Kailang <kailang@realtek.com>
To: "Takashi Iwai (tiwai@suse.de)" <tiwai@suse.de>
Cc: " (alsa-devel@alsa-project.org)" <alsa-devel@alsa-project.org>
Subject: Set pcbeep to default value
Date: Fri, 22 Nov 2024 07:29:56 +0000 [thread overview]
Message-ID: <a76a10fc88e740f2b157375d44f167c7@realtek.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 90 bytes --]
Hi Takashi,
Attach patch will set pcbeep to default value for ALC274.
BR,
Kailang
[-- Attachment #2: 0000-dell-alc274-beep-default.patch --]
[-- Type: application/octet-stream, Size: 745 bytes --]
From 590987836f5f8e565e7fed37256185f5504d6da6 Mon Sep 17 00:00:00 2001
From: Kailang Yang <kailang@realtek.com>
Date: Thu, 21 Nov 2024 16:16:26 +0800
Subject: [PATCH] Set PCBeep to default value for ALC274
Enable PC beep path cause pop noise via speaker during boot time.
Set to default value will solve the issue.
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 56a3622ca2c1..67036fe6c6cc 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -473,6 +473,8 @@ static void alc_fill_eapd_coef(struct hda_codec *codec)
break;
case 0x10ec0234:
case 0x10ec0274:
+ alc_write_coef_idx(codec, 0x6e, 0x0c25);
+ fallthrough;
case 0x10ec0294:
case 0x10ec0700:
case 0x10ec0701:
next reply other threads:[~2024-11-22 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 7:29 Kailang [this message]
2024-11-22 9:34 ` Set pcbeep to default value Takashi Iwai
[not found] ` <cb9caa0e01f34e3b881bad24701c741f@realtek.com>
[not found] ` <87v7wbxti2.wl-tiwai@suse.de>
2024-11-26 2:35 ` Kailang
2024-11-26 8:05 ` Kailang
2024-11-26 14:09 ` 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=a76a10fc88e740f2b157375d44f167c7@realtek.com \
--to=kailang@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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