On Tue, Oct 2, 2012 at 3:38 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > On Tue, Oct 2, 2012 at 3:47 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: >> On Tue, Oct 2, 2012 at 1:45 PM, Greg Kroah-Hartman > > We enumerate ACPI devices by doing a depth-first traversal of the > namespace. We should be able to bind a driver to a device as soon as > we discover it. For PNP0A03/08 host bridges, that will be the > pci_root.c driver. That driver's .add() method enumerates all the PCI > devices behind the host bridge, which is another depth-first > traversal, this time of the PCI hierarchy. Similarly, we ought to be > able to bind drivers to the PCI devices as we discover them. before introducing this per device .drivers_autoprobe, i did one acpi to pci bind version as attached patch. that mean that will have two version: for booting path: use pci to acpi binding. and hot plug path will use acpi to pci binding. Also that make code pretty ugly to consider platform_notifier at the same time. and acp_get_pci_dev in that acpi_pci_hp_notifier is not very efficient. -Yinghai
Attachment:
add_acpi_pci_notifier_xx.patch
Description: Binary data
