On Mon, 30 Jul 2012, Huang Ying wrote: > > Yup, that worked in the quick test I just did. > > > > lspci reading the device config will still not wake the bridge, but I > > assume that is intentional? But loading the device driver now wakes > > both the bridge and the device, so that works. > > Do you have time to test the following patch to fix the lspci issue? > > Subject: [BUGFIX] PCI/PM: Keep parent bridge active when read/write config reg > > This patch fixes the following bug: > > http://marc.info/?l=linux-pci&m=134338059022620&w=2 > > Where lspci does not work properly if a device and the corresponding > parent bridge (such as PCIe port) is suspended. This is because the > device configuration space registers will be not accessible if the > corresponding parent bridge is suspended. > > To solve the issue, the bridge/PCIe port connected to the device is > put into active state before read/write configuration space registers. What happens when you run lspci and the device is in D3cold? Then even if the parent bridge is active, lspci will still fail. It seems that in this case you need to resume the device itself, not just its parent. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
