On Thu, May 12, 2011 at 9:52 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 12 May 2011, Xu, Andiry wrote: > >> > -----Original Message----- >> > From: linux-usb-owner@xxxxxxxxxxxxxxx [mailto:linux-usb- >> > owner@xxxxxxxxxxxxxxx] On Behalf Of Dwight Schauer >> > Sent: Thursday, May 12, 2011 12:58 AM >> > To: linux-usb@xxxxxxxxxxxxxxx >> > Cc: dschauer@xxxxxx >> > Subject: xHCI and suspend/resume >> > >> > What is the current state of suspend/resume in xhci_hcd? >> > >> >> Xhci-hcd supports suspend/resume/remote wakeup. >> >> > I'm using 2.6.39-rc7-gregkh and the NEC (pci 1033:0194) and the TI >> > USB-3 (pci 104c:8241) host controllers don't show up in >> > /proc/acpi/wakeup (and do not have a >> > /sys/bus/usb/devices/XXX/power/wakeup entry). >> > >> >> I think the /proc/acpi/wakeup list is set up by BIOS through ACPI >> table. On my platform the on-board xHCI controller is showed in >> /proc/acpi/wakeup as XHC0 and XHC1, but the external NEC host >> controller does not appear in it. > > Right; an add-on device isn't known to the ACPI and hence doesn't show > up (although devices on the motherboard should appear). Besides, > /proc/acpi/wakeup is deprecated anyway; nowadays you're supposed to use > /sys/.../power/wakeup instead. > > Dwight's problem is that he is looking in the wrong place. The xHCI > controller is not a USB device; it's a PCI device -- i.e., it > communicates with the computer over a PCI bus and not over a USB bus. > Therefore it shows up under /sys/bus/pci, not /sys/bus/usb. > OK, thanks. I see that now. I've gone into /sys/bus/pci/.../power/ for the xHCI controller in question and put "enabled" in wakeup, but it does not seem to have the same effect as enabled wakeups in /proc/acpi/wakeup. -- Dwight -- 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
