All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org
Cc: Takashi Iwai <tiwai@suse.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@redhat.com>,
	dayer3@gmail.com, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH 0/2] x86/PCI: enable pci=use_crs for more machines
Date: Tue, 16 Jun 2015 11:55:36 -0500	[thread overview]
Message-ID: <20150616165033.9306.78046.stgit@bhelgaas-glaptop2.roam.corp.google.com> (raw)

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(-)

             reply	other threads:[~2015-06-16 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 16:55 Bjorn Helgaas [this message]
2015-06-16 16:55 ` [PATCH 1/2] x86/PCI: Use host bridge _CRS info on Foxconn K8M890-8237A Bjorn Helgaas
2015-06-16 16:55 ` [PATCH 2/2] x86/PCI: Use host bridge _CRS info on systems with >32 bit addressing Bjorn Helgaas
2015-06-17 22:28 ` [PATCH 0/2] x86/PCI: enable pci=use_crs for more machines Bjorn Helgaas

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=20150616165033.9306.78046.stgit@bhelgaas-glaptop2.roam.corp.google.com \
    --to=bhelgaas@google.com \
    --cc=dayer3@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.de \
    --cc=x86@kernel.org \
    --cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.