From: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, lgirdwood@gmail.com, patches.audio@intel.com,
broonie@kernel.org, Vinod Koul <vinod.koul@intel.com>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: [PATCH 3/4] ASoC: Intel: Skylake: Add Geminlake IDs
Date: Thu, 9 Feb 2017 16:44:03 +0530 [thread overview]
Message-ID: <1486638844-17975-4-git-send-email-subhransu.s.prusty@intel.com> (raw)
In-Reply-To: <1486638844-17975-1-git-send-email-subhransu.s.prusty@intel.com>
From: Vinod Koul <vinod.koul@intel.com>
Geminilake is next gen SoC, so add the IDs for Geminilake.
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
---
sound/soc/intel/skylake/skl-messages.c | 7 +++++++
sound/soc/intel/skylake/skl.c | 7 +++++++
2 files changed, 14 insertions(+)
diff --git a/sound/soc/intel/skylake/skl-messages.c b/sound/soc/intel/skylake/skl-messages.c
index e79cbcf6e462..e66870474f10 100644
--- a/sound/soc/intel/skylake/skl-messages.c
+++ b/sound/soc/intel/skylake/skl-messages.c
@@ -220,6 +220,13 @@ static struct skl_dsp_loader_ops bxt_get_loader_ops(void)
.init_fw = bxt_sst_init_fw,
.cleanup = bxt_sst_dsp_cleanup
},
+ {
+ .id = 0x3198,
+ .loader_ops = bxt_get_loader_ops,
+ .init = bxt_sst_dsp_init,
+ .init_fw = bxt_sst_init_fw,
+ .cleanup = bxt_sst_dsp_cleanup
+ },
};
const struct skl_dsp_ops *skl_get_dsp_ops(int pci_id)
diff --git a/sound/soc/intel/skylake/skl.c b/sound/soc/intel/skylake/skl.c
index 1152e46daede..0c57d4eaae3a 100644
--- a/sound/soc/intel/skylake/skl.c
+++ b/sound/soc/intel/skylake/skl.c
@@ -883,6 +883,10 @@ static void skl_remove(struct pci_dev *pci)
{}
};
+static struct sst_acpi_mach sst_glk_devdata[] = {
+ { "INT343A", "glk_alc298s_i2s", "intel/dsp_fw_glk.bin", NULL, NULL, NULL },
+};
+
/* PCI IDs */
static const struct pci_device_id skl_ids[] = {
/* Sunrise Point-LP */
@@ -894,6 +898,9 @@ static void skl_remove(struct pci_dev *pci)
/* KBL */
{ PCI_DEVICE(0x8086, 0x9D71),
.driver_data = (unsigned long)&sst_kbl_devdata},
+ /* GLK */
+ { PCI_DEVICE(0x8086, 0x3198),
+ .driver_data = (unsigned long)&sst_glk_devdata},
{ 0, }
};
MODULE_DEVICE_TABLE(pci, skl_ids);
--
1.9.1
next prev parent reply other threads:[~2017-02-09 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 11:14 [PATCH 0/4] ASoC: Intel: Skylake: Enable Geminilake support Subhransu S. Prusty
2017-02-09 11:14 ` [PATCH 1/4] ASoC: Intel: Skylake: Check device type to get endpoint configuration Subhransu S. Prusty
2017-02-16 19:04 ` Applied "ASoC: Intel: Skylake: Check device type to get endpoint configuration" to the asoc tree Mark Brown
2017-02-09 11:14 ` [PATCH 2/4] ASoC: rt298: Add DMI match for Geminilake reference platform Subhransu S. Prusty
2017-02-16 19:04 ` Applied "ASoC: rt298: Add DMI match for Geminilake reference platform" to the asoc tree Mark Brown
2017-02-09 11:14 ` Subhransu S. Prusty [this message]
2017-02-16 19:03 ` Applied "ASoC: Intel: Skylake: Add Geminlake IDs" " Mark Brown
2017-02-09 11:14 ` [PATCH 4/4] ASoC: hdac_hdmi: Add device id for Geminilake Subhransu S. Prusty
2017-02-16 19:03 ` Applied "ASoC: hdac_hdmi: Add device id for Geminilake" to the asoc tree 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=1486638844-17975-4-git-send-email-subhransu.s.prusty@intel.com \
--to=subhransu.s.prusty@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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