On Wed, Apr 3, 2013 at 12:30 AM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > On Tue, Apr 2, 2013 at 9:02 AM, Martin Mokrejs > <mmokrejs@xxxxxxxxxxxxxxxxxx> wrote: >> Hi Ying, >> >> huang ying wrote: > >>> And please give me the full dmesg for boot and incremental dmesg for >>> operations. >> >> >> The incremental bits here, the full dmesg will send only directly to your email, due to its size. > > Is there a bugzilla for this issue? Please attach the complete dmesg > there or somewhere similar so we can all benefit. > > I think we have two problems that may be relevant to this discussion. > > 1) The _OSC "PCI Express Capability Structure control" bit. I don't > think Linux pays attention to whether the BIOS has granted us control > over the capability, so we may do things to it that the BIOS doesn't > expect. > > 2) acpiphp currently uses the presence of _ADR/_EJ0/_RMV to detect > hotplug slots. I don't think this is sufficient (see > https://bugzilla.kernel.org/show_bug.cgi?id=54981 for details). > Therefore, I don't think pci_bus_has_hotplug_slots() in port_dbg.patch > can be accurate. I think it returns "false" for some buses where it > should return "true," such as the ExpressCard slot on Chris Clayton's > system (see bug 54981). Yes. pci_bus_has_hotplug_slots() is not accurate. But I still think it can be used in port runtime PM. Because if there is no hotplug slots registered, the hotplug itself can not work properly, with or without port runtime PM enabled. And we should add necessary pm_runtime_get_sync/put_sync into pci_scan_bus to deal with "rescan". What do you think about that? pci_dev->is_hotplug_bridge is not accurate too. It reports a internal port of my X220 as a hotplug-able port. But it appears that it will report more instead of less. It can report correctly for port in bug 54981. Do you think that is a good choice for port runtime PM filtering? Best Regards, Huang Ying -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
