From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Seth Heasley <seth.heasley@intel.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.37-rc2] irq: irq and pci_ids patch for Intel Patsburg
Date: Fri, 10 Dec 2010 13:06:49 -0800 [thread overview]
Message-ID: <20101210130649.33a31b8a@jbarnes-desktop> (raw)
In-Reply-To: <201011171112.08712.seth.heasley@intel.com>
On Wed, 17 Nov 2010 12:12:08 -0700
Seth Heasley <seth.heasley@intel.com> wrote:
> This patch adds an additional LPC Controller DeviceID for the Intel Patsburg PCH.
>
> Signed-off-by: Seth Heasley <seth.heasley@intel.com>
>
> --- linux-2.6.37-rc2/include/linux/pci_ids.h.orig 2010-11-17 10:00:31.000000000 -0800
> +++ linux-2.6.37-rc2/include/linux/pci_ids.h 2010-11-17 10:01:49.000000000 -0800
> @@ -2466,7 +2466,8 @@
> #define PCI_DEVICE_ID_INTEL_COUGARPOINT_LPC_MIN 0x1c41
> #define PCI_DEVICE_ID_INTEL_COUGARPOINT_LPC_MAX 0x1c5f
> #define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS 0x1d22
> -#define PCI_DEVICE_ID_INTEL_PATSBURG_LPC 0x1d40
> +#define PCI_DEVICE_ID_INTEL_PATSBURG_LPC_0 0x1d40
> +#define PCI_DEVICE_ID_INTEL_PATSBURG_LPC_1 0x1d41
> #define PCI_DEVICE_ID_INTEL_82801AA_0 0x2410
> #define PCI_DEVICE_ID_INTEL_82801AA_1 0x2411
> #define PCI_DEVICE_ID_INTEL_82801AA_3 0x2413
> --- linux-2.6.37-rc2/arch/x86/pci/irq.c.orig 2010-11-17 10:01:13.000000000 -0800
> +++ linux-2.6.37-rc2/arch/x86/pci/irq.c 2010-11-17 10:01:33.000000000 -0800
> @@ -589,7 +589,8 @@
> case PCI_DEVICE_ID_INTEL_ICH10_1:
> case PCI_DEVICE_ID_INTEL_ICH10_2:
> case PCI_DEVICE_ID_INTEL_ICH10_3:
> - case PCI_DEVICE_ID_INTEL_PATSBURG_LPC:
> + case PCI_DEVICE_ID_INTEL_PATSBURG_LPC_0:
> + case PCI_DEVICE_ID_INTEL_PATSBURG_LPC_1:
> r->name = "PIIX/ICH";
> r->get = pirq_piix_get;
> r->set = pirq_piix_set;
>
applied to my linux-next branch, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-12-10 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 19:12 Seth Heasley
2010-12-10 21:06 ` Jesse Barnes [this message]
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=20101210130649.33a31b8a@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seth.heasley@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
Powered by JetHome