Re: [RFC PATCH] PCIe: Add PCIe runtime D3cold support

From: huang ying
Date: Tue Apr 17 2012 - 01:32:19 EST

On Tue, Apr 17, 2012 at 10:12 AM, Yan, Zheng <zheng.z.yan@xxxxxxxxx> wrote:
> On 04/17/2012 01:07 AM, Rafael J. Wysocki wrote:
>> BTW, can you please explain to me what the #WAKE signal is and how it is
>> different from PME#?
> #WAKE signal is triggered by a pin connected to the root complex or other
> motherboard logic. PME# is triggered by PME message sent to the port.

PME# is a PCI pin, while WAKE# is a PCI Express pin. In PCI Express,
there is no PME#, PME is delivered between end point device and root
port or root complex event collector via PME message, and the PME
message will trigger IRQ on root port or root complex event collector.
WAKE# is not used for PCI Express D1, D2 and D3hot, it is just used
by D3cold. When remote wakeup detected by end point device, it will
assert WAKE# to notify power controller (implemented via ACPI on some
platform), then power controller will turn on power for main link,
after link goes back to L0, PME message will be sent to root port or
root complex event collector by end point device.

Best Regards,
Huang Ying
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at