Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alexandra Yates <alexandra.yates@linux.intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Intel device IDs Audio
Date: Wed, 04 Nov 2015 06:59:19 +0100	[thread overview]
Message-ID: <s5hegg6nw3s.wl-tiwai@suse.de> (raw)
In-Reply-To: <1446595967-9671-1-git-send-email-alexandra.yates@linux.intel.com>

On Wed, 04 Nov 2015 01:12:47 +0100,
Alexandra Yates wrote:
> 
> Adding Intel codename Lewisburg platform device IDs for audio.
> 
> Signed-off-by: Alexandra Yates <alexandra.yates@linux.intel.com>
> ---
>  sound/pci/hda/hda_intel.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
> index c38c68f..51d6ff3 100644
> --- a/sound/pci/hda/hda_intel.c
> +++ b/sound/pci/hda/hda_intel.c
> @@ -2099,6 +2099,11 @@ static const struct pci_device_id azx_ids[] = {
>  	/* 9 Series */
>  	{ PCI_DEVICE(0x8086, 0x8ca0),
>  	  .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH },
> +	/* Lewisburg */
> +	{ PCI_DEVICE(0x8086, 0xa1f0),
> +	  .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH },
> +	{ PCI_DEVICE(0x8086, 0xa270),
> +	  .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH },
>  	/* Wellsburg */
>  	{ PCI_DEVICE(0x8086, 0x8d20),
>  	  .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH },

Is this the best position to add?  That is, is Lewisburg an older chip
than Wellsburg?


thanks,

Takashi

       reply	other threads:[~2015-11-04  5:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1446595967-9671-1-git-send-email-alexandra.yates@linux.intel.com>
2015-11-04  5:59 ` Takashi Iwai [this message]
     [not found]   ` <563A56D3.7080304@linux.intel.com>
2015-11-04 21:35     ` [PATCH] Intel device IDs Audio 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=s5hegg6nw3s.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alexandra.yates@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    /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