On Tue, Sep 27, 2011 at 10:54:47PM +0200, Rafael J. Wysocki wrote: > On Tuesday, September 27, 2011, Sarah Sharp wrote: > > On Tue, Sep 27, 2011 at 12:20:26AM +0200, Rafael J. Wysocki wrote: > > > On Sunday, September 25, 2011, Rafael J. Wysocki wrote: > > > > On Thursday, September 22, 2011, Sarah Sharp wrote: > > > > > On Mon, Sep 19, 2011 at 11:43:33PM +0200, Rafael J. Wysocki wrote: > > > > Without looking at the tables at the moment (I'll do that later), > > > > I think that they are missing the information that GPE 0D is a wakeup > > > > GPE for the xHCI device. > > > > > > The DSDT appears to contain that information, so I'm not sure what's > > > going on. Perhaps you can put a debug printk into acpi_dev_run_wake() > > > to see if that function is called for the xHCI controllers? > > > > I put a printk in acpi_dev_run_wake(), and that shows up in the original > > dmesg I sent: > > > > Sep 22 10:47:09 talon kernel: [ 2026.211933] xhci_hcd 0000:00:14.0: acpi_pci_run_wake - enable dev wake > > Sep 22 10:47:09 talon kernel: [ 2026.211936] acpi device:34: acpi_dev_run_wake - enable dev wake > > Sep 22 10:47:09 talon kernel: [ 2026.211955] acpi device:34: acpi_dev_run_wake - return -19 > > OK, can you printk() dev->wakeup.gpe_number here? > > [/me realizes that "error" is not really used in this function. Bah.] Ok, here's what dmesg says (I used %u not 0x%x for the GPE number): Sep 27 16:30:34 talon kernel: [ 882.301023] xhci_hcd 0000:00:14.0: xhci_pci_suspend Sep 27 16:30:34 talon kernel: [ 882.301029] xhci_hcd 0000:00:14.0: xhci_suspend Sep 27 16:30:34 talon kernel: [ 882.301039] xhci_hcd 0000:00:14.0: // Setting command ring address to 0x30c3f001 Sep 27 16:30:34 talon kernel: [ 882.301090] xhci_hcd 0000:00:14.0: hcd_pci_runtime_suspend: 0 Sep 27 16:30:34 talon kernel: [ 882.301140] acpi_bus_power_manageable - result 0, device->flags.power_manageable 0 Sep 27 16:30:34 talon kernel: [ 882.301143] xhci_hcd 0000:00:14.0: acpi_pci_power_manageable - dev is not power manageable Sep 27 16:30:34 talon kernel: [ 882.301146] acpi_bus_power_manageable - result 0, device->flags.power_manageable 0 Sep 27 16:30:34 talon kernel: [ 882.301149] xhci_hcd 0000:00:14.0: __pci_enable_wake - enable runtimewake Sep 27 16:30:34 talon kernel: [ 882.301156] xhci_hcd 0000:00:14.0: PME# enabled Sep 27 16:30:34 talon kernel: [ 882.301159] xhci_hcd 0000:00:14.0: acpi_pci_run_wake - enable dev wake Sep 27 16:30:34 talon kernel: [ 882.301162] acpi device:34: acpi_dev_run_wake - enable dev wake Sep 27 16:30:34 talon kernel: [ 882.301175] acpi device:34: acpi_dev_run_wake - enable gpe 13 Sep 27 16:30:34 talon kernel: [ 882.301185] acpi device:34: acpi_dev_run_wake - return -19 Sep 27 16:30:34 talon kernel: [ 882.301188] xhci_hcd 0000:00:14.0: pci_raw_set_power_state from 0 to 3 Sep 27 16:30:34 talon kernel: [ 882.312288] acpi_bus_power_manageable - result 0, device->flags.power_manageable 0 Sep 27 16:30:34 talon kernel: [ 882.312293] xhci_hcd 0000:00:14.0: acpi_pci_power_manageable - dev is not power manageable Sep 27 16:30:34 talon kernel: [ 882.312296] acpi_bus_power_manageable - result 0, device->flags.power_manageable 0 Sep 27 16:30:34 talon kernel: [ 882.312299] xhci_hcd 0000:00:14.0: pci_platform_power_transition - is NOT power managable If I wake up the host controller by plugging in a webcam into an external hub: Sep 27 16:31:46 talon kernel: [ 953.645014] ehci_hcd 0000:00:1d.0: pci_acpi_wake_dev Sep 27 16:31:46 talon kernel: [ 953.645023] ehci_hcd 0000:00:1a.0: pci_acpi_wake_dev Sep 27 16:31:46 talon kernel: [ 953.645029] snd_hda_intel 0000:00:1b.0: pci_acpi_wake_dev Sep 27 16:31:46 talon kernel: [ 953.645034] e1000e 0000:00:19.0: pci_acpi_wake_dev Sep 27 16:31:46 talon kernel: [ 953.645089] ehci_hcd 0000:00:1d.0: pci_acpi_wake_dev Sep 27 16:31:46 talon kernel: [ 953.645094] ehci_hcd 0000:00:1a.0: pci_acpi_wake_dev Sep 27 16:31:46 talon kernel: [ 953.645098] snd_hda_intel 0000:00:1b.0: pci_acpi_wake_dev Sep 27 16:31:46 talon kernel: [ 953.645103] e1000e 0000:00:19.0: pci_acpi_wake_dev Those lines repeat constantly until I echo on to the power/control file for the xHCI device. If I cat the /sys/firmware/acpi/interrupts/gpe0D file *before* I disable D3, I see: root@talon:/sys/firmware/acpi/interrupts# cat gpe0D 211327 enabled root@talon:/sys/firmware/acpi/interrupts# I think I was catting the file after I ran `echo on > power/control` previously. Sorry for the confusion. So it looks like gpe 0xD is enabled when the host goes into D3, and acpi_dev_run_wake is calling acpi_enable_gpe() with GPE 13 (i.e. 0xD), correct? Sarah Sharp -- 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
