Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933151AbbFQW3A (ORCPT ); Wed, 17 Jun 2015 18:29:00 -0400 Received: from mail-yh0-f49.google.com ([209.85.213.49]:33918 "EHLO mail-yh0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753463AbbFQW24 (ORCPT ); Wed, 17 Jun 2015 18:28:56 -0400 MIME-Version: 1.0 In-Reply-To: <20150616165033.9306.78046.stgit@bhelgaas-glaptop2.roam.corp.google.com> References: <20150616165033.9306.78046.stgit@bhelgaas-glaptop2.roam.corp.google.com> From: Bjorn Helgaas Date: Wed, 17 Jun 2015 17:28:35 -0500 Message-ID: Subject: Re: [PATCH 0/2] x86/PCI: enable pci=use_crs for more machines To: "linux-pci@vger.kernel.org" Cc: Takashi Iwai , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , Ingo Molnar , dayer3@gmail.com, "H. Peter Anvin" , Thomas Gleixner , Yinghai Lu Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1253 Lines: 28 On Tue, Jun 16, 2015 at 11:55 AM, Bjorn Helgaas wrote: > 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 I applied both patches to pci/resource for v4.2. -- 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/