linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@intel.com>
To: Len Brown <len.brown@intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	x86@kernel.org, linux-pci@vger.kernel.org,
	linux-acpi@vger.kernel.org
Cc: Feng Tang <feng.tang@intel.com>
Subject: [PATCH] x86/PCI: Add quirk for "CheckPoint P-20-00" to not use bridge _CRS_ info
Date: Fri, 12 Oct 2012 09:15:09 +0800	[thread overview]
Message-ID: <1350004509-17414-1-git-send-email-feng.tang@intel.com> (raw)

This is to fix a regression https://bugzilla.kernel.org/show_bug.cgi?id=47981

The CheckPoint P-20-00 works ok before new machines (2008 and later) are
forced to use the bridge _CRS info by default in 2.6.34. Add this quirk
to restore its old way of working: not using bridge _CRS info.

Signed-off-by: Feng Tang <feng.tang@intel.com>
---
 arch/x86/pci/acpi.c |   10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
index 192397c..7010c19 100644
--- a/arch/x86/pci/acpi.c
+++ b/arch/x86/pci/acpi.c
@@ -98,6 +98,16 @@ static const struct dmi_system_id pci_use_crs_table[] __initconst = {
 			DMI_MATCH(DMI_BIOS_VERSION, "6JET85WW (1.43 )"),
 		},
 	},
+	/* https://bugzilla.kernel.org/show_bug.cgi?id=47981 */
+	{
+		.callback = set_nouse_crs,
+		.ident = "CheckPoint P-20-00",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "CheckPoint"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "P-20-00"),
+			DMI_MATCH(DMI_BOARD_NAME, "Bridgeport"),
+		},
+	},
 	{}
 };
 
-- 
1.7.9.5


                 reply	other threads:[~2012-10-11  9:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1350004509-17414-1-git-send-email-feng.tang@intel.com \
    --to=feng.tang@intel.com \
    --cc=bhelgaas@google.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).