From: "Pascal Noël" <pascal@pascalcompiles.com>
To: perex@perex.cz, tiwai@suse.com
Cc: kailang@realtek.com, sbinding@opensource.cirrus.com,
luke@ljones.dev, andy.chi@canonical.com, shenghao-ding@ti.com,
l.guzenko@web.de, ruinairas1992@gmail.com, yangyuchi66@gmail.com,
vitalyr@opensource.cirrus.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, pascal@pascalcompiles.com
Subject: [PATCH] ALSA: hda/realtek: Apply quirk for ASUS UM3504DA
Date: Fri, 1 Dec 2023 17:37:44 -0800 [thread overview]
Message-ID: <20231202013744.12369-1-pascal@pascalcompiles.com> (raw)
The ASUS UM3504DA uses a Realtek HDA codec and two CS35L41 amplifiers via I2C.
Apply existing quirk to model.
Signed-off-by: Pascal Noël <pascal@pascalcompiles.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 f9ddacfd9..ddd74f5d3 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -9963,6 +9963,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1043, 0x17f3, "ROG Ally RC71L_RC71L", ALC294_FIXUP_ASUS_ALLY),
SND_PCI_QUIRK(0x1043, 0x1881, "ASUS Zephyrus S/M", ALC294_FIXUP_ASUS_GX502_PINS),
SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA", ALC256_FIXUP_ASUS_HEADSET_MIC),
+ SND_PCI_QUIRK(0x1043, 0x18d3, "ASUS UM3504DA", ALC294_FIXUP_CS35L41_I2C_2),
SND_PCI_QUIRK(0x1043, 0x18f1, "Asus FX505DT", ALC256_FIXUP_ASUS_HEADSET_MIC),
SND_PCI_QUIRK(0x1043, 0x194e, "ASUS UX563FD", ALC294_FIXUP_ASUS_HPE),
SND_PCI_QUIRK(0x1043, 0x1970, "ASUS UX550VE", ALC289_FIXUP_ASUS_GA401),
--
2.43.0
next reply other threads:[~2023-12-04 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 1:37 Pascal Noël [this message]
2023-12-03 9:05 ` [PATCH] ALSA: hda/realtek: Apply quirk for ASUS UM3504DA 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=20231202013744.12369-1-pascal@pascalcompiles.com \
--to=pascal@pascalcompiles.com \
--cc=alsa-devel@alsa-project.org \
--cc=andy.chi@canonical.com \
--cc=kailang@realtek.com \
--cc=l.guzenko@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=perex@perex.cz \
--cc=ruinairas1992@gmail.com \
--cc=sbinding@opensource.cirrus.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.com \
--cc=vitalyr@opensource.cirrus.com \
--cc=yangyuchi66@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.