diff options
| author | Bjorn Helgaas <bhelgaas@google.com> | 2014-08-30 07:23:01 -0600 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2014-09-12 20:12:14 -0600 |
| commit | 1302fcf0d03e6ea74846c7fee14736306ab2ce4b (patch) | |
| tree | a7aa92d1b4a0f5c5451d2f13ba82bd1e2761cbd6 /drivers/pci | |
| parent | 302328c00341f1c161bfe32d085d3e6549a08f2d (diff) | |
| download | op-kernel-dev-1302fcf0d03e6ea74846c7fee14736306ab2ce4b.zip op-kernel-dev-1302fcf0d03e6ea74846c7fee14736306ab2ce4b.tar.gz | |
PCI: Configure *all* devices, not just hot-added ones
There's not really a good way to determine whether firmware has already
configured a device with _HPP/_HPX settings. On legacy systems, the BIOS
has probably configured everything, but on UEFI systems it is not required
to do so.
Per the PCI Firmware Specification, rev 3.1, sec 3.5, if PCI_COMMAND_IO or
PCI_COMMAND_MEMORY is set, we can assume firmware has set the corresponding
BARs and maybe we can assume it has configured the rest of the device. And
if a bridge has PCI_COMMAND_PARITY or PCI_COMMAND_SERR set, we can assume
firmware has configured the bridge. But we can't tell much about devices
without BARs.
I think it should be safe to apply _HPP and _HPX settings anyway, even if
firmware has already configured the device, so configure everything we
find.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Diffstat (limited to 'drivers/pci')
| -rw-r--r-- | drivers/pci/probe.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c index cb411fb..290c657 100644 --- a/drivers/pci/probe.c +++ b/drivers/pci/probe.c @@ -1358,9 +1358,6 @@ static void pci_configure_device(struct pci_dev *dev) struct hotplug_params hpp; int ret; - if (system_state == SYSTEM_BOOTING) - return; - memset(&hpp, 0, sizeof(hpp)); ret = pci_get_hp_params(dev, &hpp); if (ret) |
