From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Seth Heasley <seth.heasley@intel.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
james.d.ralston@intel.com
Subject: Re: [PATCH 6/6] pci: irq and pci_ids patch for Intel Lynx Point DeviceIDs
Date: Fri, 27 Jan 2012 10:31:10 -0800 [thread overview]
Message-ID: <20120127103110.2a4d667f@jbarnes-desktop> (raw)
In-Reply-To: <201201231646.24194.seth.heasley@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
On Mon, 23 Jan 2012 16:46:24 -0800
Seth Heasley <seth.heasley@intel.com> wrote:
> This patch adds the LPC Controller DeviceIDs for the Intel Lynx Point PCH.
>
> Signed-off-by: Seth Heasley <seth.heasley@intel.com>
> ---
> arch/x86/pci/irq.c | 4 +++-
> include/linux/pci_ids.h | 2 ++
> 2 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/pci/irq.c b/arch/x86/pci/irq.c
> index 372e9b8..22468b6 100644
> --- a/arch/x86/pci/irq.c
> +++ b/arch/x86/pci/irq.c
> @@ -604,7 +604,9 @@ static __init int intel_router_probe(struct irq_router *r, struct pci_dev *route
> || (device >= PCI_DEVICE_ID_INTEL_DH89XXCC_LPC_MIN &&
> device <= PCI_DEVICE_ID_INTEL_DH89XXCC_LPC_MAX)
> || (device >= PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MIN &&
> - device <= PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MAX)) {
> + device <= PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MAX)
> + || (device >= PCI_DEVICE_ID_INTEL_LYNXPOINT_LPC_MIN &&
> + device <= PCI_DEVICE_ID_INTEL_LYNXPOINT_LPC_MAX)) {
> r->name = "PIIX/ICH";
> r->get = pirq_piix_get;
> r->set = pirq_piix_set;
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index 31d77af..6a0359a 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -2800,6 +2800,8 @@
> #define PCI_DEVICE_ID_INTEL_82454NX 0x84cb
> #define PCI_DEVICE_ID_INTEL_84460GX 0x84ea
> #define PCI_DEVICE_ID_INTEL_IXP4XX 0x8500
> +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LPC_MIN 0x8c40
> +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LPC_MAX 0x8c5f
> #define PCI_DEVICE_ID_INTEL_IXP2800 0x9004
> #define PCI_DEVICE_ID_INTEL_S21152BB 0xb152
>
Seems we add every new GMCH or PCH anyway, why not just use the piix
routines for any unknown (therefore presumably new) Intel PCH device?
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-27 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 0:46 [PATCH 6/6] pci: irq and pci_ids patch for Intel Lynx Point DeviceIDs Seth Heasley
2012-01-24 1:14 ` Greg KH
2012-01-27 18:31 ` Jesse Barnes [this message]
2012-01-27 18:56 ` Heasley, Seth
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=20120127103110.2a4d667f@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=james.d.ralston@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).