> >
> > Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
> > Cc:
kristen.c.accardi@intel.com
> > Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> > ---
> > drivers/pci/hotplug/acpi_pcihp.c | 41
> > ++++++++++++++++++++++++++----------- 1 files changed, 29 insertions(+), 12
> > deletions(-)
> >
> > diff --git a/drivers/pci/hotplug/acpi_pcihp.c
> > b/drivers/pci/hotplug/acpi_pcihp.c index 93e37f0..bd83197 100644
> > --- a/drivers/pci/hotplug/acpi_pcihp.c
> > +++ b/drivers/pci/hotplug/acpi_pcihp.c
> > @@ -382,7 +382,7 @@ EXPORT_SYMBOL_GPL(acpi_get_hp_params_from_firmware);
> > int acpi_get_hp_hw_control_from_firmware(struct pci_dev *dev, u32 flags)
> > {
> > acpi_status status;
> > - acpi_handle chandle, handle = DEVICE_ACPI_HANDLE(&(dev->dev));
> > + acpi_handle chandle, handle;
> > struct pci_dev *pdev = dev;
> > struct pci_bus *parent;
> > struct acpi_buffer string = { ACPI_ALLOCATE_BUFFER, NULL };
> > @@ -399,10 +399,28 @@ int acpi_get_hp_hw_control_from_firmware(struct
> > pci_dev *dev, u32 flags) * Per PCI firmware specification, we should run
> > the ACPI _OSC
> > * method to get control of hotplug hardware before using it. If
> > * an _OSC is missing, we look for an OSHP to do the same thing.
> > - * To handle different BIOS behavior, we look for _OSC and OSHP
> > - * within the scope of the hotplug controller and its parents,
> > + * To handle different BIOS behavior, we look for _OSC on a root
> > + * bridge preferentially (according to PCI fw spec). Later for
> > + * OSHP within the scope of the hotplug controller and its parents,
> > * upto the host bridge under which this controller exists.
> > */
> > + while (pdev->bus->self)
> > + pdev = pdev->bus->self;
> > + handle = acpi_get_pci_rootbridge_handle(pci_domain_nr(pdev->bus),
> > + pdev->bus->number);