alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: libin.yang@intel.com
To: alsa-devel@alsa-project.org, tiwai@suse.de, mengdong.lin@intel.com
Cc: Libin Yang <libin.yang@intel.com>
Subject: [PATCH 1/2] ALSA: hda - add PCI IDs for Intel Braswell
Date: Wed, 23 Jul 2014 08:55:37 +0800	[thread overview]
Message-ID: <1406076938-97633-1-git-send-email-libin.yang@intel.com> (raw)

From: Libin Yang <libin.yang@intel.com>

Add HD Audio Device PCI ID for the Intel Braswell platform.

Signed-off-by: Libin Yang <libin.yang@intel.com>
---
 sound/pci/hda/hda_intel.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index 387fc73..f758729 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -2017,6 +2017,9 @@ static const struct pci_device_id azx_ids[] = {
 	/* BayTrail */
 	{ PCI_DEVICE(0x8086, 0x0f04),
 	  .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH_NOPM },
+	/* Braswell */
+	{ PCI_DEVICE(0x8086, 0x2284),
+	  .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH_NOPM },
 	/* ICH */
 	{ PCI_DEVICE(0x8086, 0x2668),
 	  .driver_data = AZX_DRIVER_ICH | AZX_DCAPS_OLD_SSYNC |
-- 
1.9.1

             reply	other threads:[~2014-07-23  0:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  0:55 libin.yang [this message]
2014-07-23  0:55 ` [PATCH 2/2] ALSA: hda - add codec ID for Braswell display audio codec libin.yang
2014-07-23 10:07 ` [PATCH 1/2] ALSA: hda - add PCI IDs for Intel Braswell Takashi Iwai
2014-07-24  3:57   ` Yang, Libin
2014-07-24 12:59     ` Yang, Libin
2014-07-24 13:21       ` Takashi Iwai
2014-07-25  1:06         ` Yang, Libin
  -- strict thread matches above, loose matches on Subject: below --
2014-07-25  8:19 libin.yang
2014-07-25  8:31 ` Takashi Iwai
2014-07-25 13:21   ` Yang, Libin
2014-08-04  1:22 libin.yang
2014-08-04  9:16 ` 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=1406076938-97633-1-git-send-email-libin.yang@intel.com \
    --to=libin.yang@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=mengdong.lin@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).