From: Christian Lachner <gladiac@gmail.com>
To: perex@perex.cz, tiwai@suse.com, kailang@realtek.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Christian Lachner <gladiac@gmail.com>
Subject: [PATCH 1/3] hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220 quirks
Date: Sat, 29 Jan 2022 12:32:41 +0100 [thread overview]
Message-ID: <20220129113243.93068-2-gladiac@gmail.com> (raw)
In-Reply-To: <20220129113243.93068-1-gladiac@gmail.com>
The initial commit of the new Gigabyte X570 ALC1220 quirks lacked the
fixup-model entry in alc882_fixup_models[]. It seemed not to cause any ill
effects but for completeness sake this commit makes up for that.
Signed-off-by: Christian Lachner <gladiac@gmail.com>
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 668274e52674..48af182f87e4 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -2626,6 +2626,7 @@ static const struct hda_model_fixup alc882_fixup_models[] = {
{.id = ALC882_FIXUP_NO_PRIMARY_HP, .name = "no-primary-hp"},
{.id = ALC887_FIXUP_ASUS_BASS, .name = "asus-bass"},
{.id = ALC1220_FIXUP_GB_DUAL_CODECS, .name = "dual-codecs"},
+ {.id = ALC1220_FIXUP_GB_X570, .name = "gb-x570"},
{.id = ALC1220_FIXUP_CLEVO_P950, .name = "clevo-p950"},
{}
};
--
2.34.1
next prev parent reply other threads:[~2022-01-29 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 11:32 [PATCH 0/3] hda/realtek: Add/Improve several Gigabyte X570(S) audio quirks Christian Lachner
2022-01-29 11:32 ` Christian Lachner [this message]
2022-01-29 11:32 ` [PATCH 2/3] hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer chipset) Christian Lachner
2022-01-29 11:32 ` [PATCH 3/3] hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after reboot from Windows Christian Lachner
2022-01-31 8:01 ` [PATCH 0/3] hda/realtek: Add/Improve several Gigabyte X570(S) audio quirks 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=20220129113243.93068-2-gladiac@gmail.com \
--to=gladiac@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=kailang@realtek.com \
--cc=linux-kernel@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