Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754362AbbFPQzt (ORCPT ); Tue, 16 Jun 2015 12:55:49 -0400 Received: from mail-ie0-f173.google.com ([209.85.223.173]:33868 "EHLO mail-ie0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751089AbbFPQzi (ORCPT ); Tue, 16 Jun 2015 12:55:38 -0400 Subject: [PATCH 0/2] x86/PCI: enable pci=use_crs for more machines To: linux-pci@vger.kernel.org From: Bjorn Helgaas Cc: Takashi Iwai , x86@kernel.org, linux-kernel@vger.kernel.org, Ingo Molnar , dayer3@gmail.com, "H. Peter Anvin" , Thomas Gleixner , Yinghai Lu Date: Tue, 16 Jun 2015 11:55:36 -0500 Message-ID: <20150616165033.9306.78046.stgit@bhelgaas-glaptop2.roam.corp.google.com> User-Agent: StGit/0.16 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1189 Lines: 29 We have a few reports of sound devices not working because the BIOS didn't assign space for the device and the PCI core put it at an address that doesn't work. The Foxconn system has two PCI host bridges, and without the information from _CRS, the PCI core assigns space under the wrong bridge. We also have reports from pre-2008 systems (where we normally ignore _CRS) that support more than 32 physical address bits. After d56dbf5bab8c ("PCI: Allocate 64-bit BARs above 4G when possible"), we prefer to use that high space when we can, but it seems the host bridge doesn't respond to it. _CRS tells us how to avoid both problems, so these patches enable it for these cases. --- Bjorn Helgaas (2): x86/PCI: Use host bridge _CRS info on Foxconn K8M890-8237A x86/PCI: Use host bridge _CRS info on systems with >32 bit addressing arch/x86/pci/acpi.c | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/