From: Takashi Iwai <tiwai@suse.de>
To: "Alexandra Yates" <alexandra.yates@linux.intel.com>
Cc: <alsa-devel@alsa-project.org>, <perex@perex.cz>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] Intel device IDs Audio
Date: Thu, 05 Nov 2015 11:29:27 +0100 [thread overview]
Message-ID: <s5h37wk3fjs.wl-tiwai@suse.de> (raw)
In-Reply-To: <1446681369-15596-1-git-send-email-alexandra.yates@linux.intel.com>
On Thu, 05 Nov 2015 00:56:09 +0100,
Alexandra Yates wrote:
>
> Adding Intel codename Lewisburg platform device IDs for audio.
>
> Signed-off-by: Alexandra Yates <alexandra.yates@linux.intel.com>
Thanks. Though, I still believe the position after Wellsburg is best
(which is the similar chip that has the same driver type and driver
caps bits), so I rearranged it. Also the subject was aligned.
And last but not least, Cc to stable was added.
Takashi
> ---
> 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..e8d1151 100644
> --- a/sound/pci/hda/hda_intel.c
> +++ b/sound/pci/hda/hda_intel.c
> @@ -2168,6 +2168,11 @@ static const struct pci_device_id azx_ids[] = {
> /* ICH10 */
> { PCI_DEVICE(0x8086, 0x3a6e),
> .driver_data = AZX_DRIVER_ICH | AZX_DCAPS_INTEL_ICH },
> + /* 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 },
> /* Generic Intel */
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_ANY_ID),
> .class = PCI_CLASS_MULTIMEDIA_HD_AUDIO << 8,
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2015-11-05 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH V2] Intel device IDs Audio>
2015-11-04 23:56 ` [PATCH V2] Intel device IDs Audio Alexandra Yates
2015-11-05 10:29 ` Takashi Iwai [this message]
2015-11-05 19:51 ` Alexandra Yates
2015-11-05 21:17 ` 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=s5h37wk3fjs.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alexandra.yates@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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