Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Oliver Freyermuth <o.freyermuth@googlemail.com>
To: tiwai@suse.de
Cc: linux-sound@vger.kernel.org,
	Oliver Freyermuth <o.freyermuth@googlemail.com>
Subject: [PATCH v2] ASoC: Intel: sof_sdw: Add quirk for Alienware Area 51 (2025) 0CCD SKU
Date: Fri, 16 Jan 2026 20:46:04 +0100	[thread overview]
Message-ID: <20260116194604.21099-1-o.freyermuth@googlemail.com> (raw)
In-Reply-To: <3da4b3e6-1c4b-44d3-91da-640d34d22236@googlemail.com>

This adds the necessary quirk for the Alienware 18 Area 51 (2025).
Complements 1b03391d073dad748636a1ad9668b837cce58265, which added
support for the Alienware 16 Area 51 (2025).
---
v2:
 - Resend using git-send-email to fix whitespace/tab corruption.

 sound/soc/intel/boards/sof_sdw.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/sound/soc/intel/boards/sof_sdw.c b/sound/soc/intel/boards/sof_sdw.c
index c013e31d0..f486bd74b 100644
--- a/sound/soc/intel/boards/sof_sdw.c
+++ b/sound/soc/intel/boards/sof_sdw.c
@@ -749,6 +749,14 @@ static const struct dmi_system_id sof_sdw_quirk_table[] = {
 		},
 		.driver_data = (void *)(SOC_SDW_CODEC_SPKR),
 	},
+	{
+		.callback = sof_sdw_quirk_cb,
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "Alienware"),
+			DMI_EXACT_MATCH(DMI_PRODUCT_SKU, "0CCD")
+		},
+		.driver_data = (void *)(SOC_SDW_CODEC_SPKR),
+	},
 	/* Pantherlake devices*/
 	{
 		.callback = sof_sdw_quirk_cb,
-- 
2.52.0


  reply	other threads:[~2026-01-16 19:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03 21:11 [PATCH] ASoC: Intel: sof_sdw: Add quirk for Alienware Area 51 (2025), 0CCD SKU Oliver Freyermuth
2026-01-16 19:46 ` Oliver Freyermuth [this message]
2026-01-25 19:54 ` [PATCH v3] ASoC: Intel: sof_sdw: Add quirk for Alienware Area 51 (2025) " Oliver Freyermuth
2026-02-22 20:50   ` Oliver Freyermuth
2026-02-24 19:02 ` [PATCH v4] " Oliver Freyermuth
2026-02-25 12:43   ` Pierre-Louis Bossart
2026-03-03 11:19   ` Mark Brown

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=20260116194604.21099-1-o.freyermuth@googlemail.com \
    --to=o.freyermuth@googlemail.com \
    --cc=linux-sound@vger.kernel.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