From: huang ying <huang.ying.caritas@gmail.com>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
bhelgaas@google.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
Lin Ming <ming.m.lin@intel.com>, Zhang Rui <rui.zhang@intel.com>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [RFC PATCH] PCIe: Add PCIe runtime D3cold support
Date: Tue, 17 Apr 2012 13:32:20 +0800 [thread overview]
Message-ID: <CAC=cRTMk-NTvo+DJ2mAq6_ZeVLbeqiGx+ttZG6Hr_hQyyYkfLw@mail.gmail.com> (raw)
In-Reply-To: <4F8CD18A.5080903@intel.com>
On Tue, Apr 17, 2012 at 10:12 AM, Yan, Zheng <zheng.z.yan@intel.com> 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
next prev parent reply other threads:[~2012-04-17 5:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 2:35 [RFC PATCH] PCIe: Add PCIe runtime D3cold support Yan, Zheng
2012-04-13 6:06 ` Alex He
2012-04-13 6:28 ` Yan, Zheng
2012-04-16 8:15 ` huang ying
2012-04-13 19:41 ` Rafael J. Wysocki
2012-04-16 0:48 ` Lin Ming
2012-04-16 16:26 ` Rafael J. Wysocki
2012-04-16 2:23 ` Yan, Zheng
2012-04-16 17:07 ` Rafael J. Wysocki
2012-04-17 2:07 ` huang ying
2012-04-17 20:20 ` Rafael J. Wysocki
2012-04-18 1:19 ` huang ying
2012-04-18 19:51 ` Rafael J. Wysocki
2012-04-17 2:12 ` Yan, Zheng
2012-04-17 5:32 ` huang ying [this message]
2012-04-17 20:43 ` Rafael J. Wysocki
2012-04-18 1:22 ` huang ying
2012-04-18 19:52 ` Rafael J. Wysocki
2012-04-17 20:35 ` Rafael J. Wysocki
2012-04-16 7:49 ` Yan, Zheng
2012-04-16 21:11 ` Rafael J. Wysocki
2012-04-16 8:58 ` huang ying
2012-04-16 21:30 ` Rafael J. Wysocki
2012-04-17 2:02 ` huang ying
2012-04-17 21:03 ` Rafael J. Wysocki
2012-04-18 1:45 ` huang ying
2012-04-18 21:00 ` Rafael J. Wysocki
2012-04-19 2:47 ` huang ying
2012-04-19 12:31 ` Rafael J. Wysocki
2012-04-20 0:48 ` huang ying
2012-04-17 5:13 ` huang ying
2012-04-17 21:10 ` Rafael J. Wysocki
2012-04-18 2:01 ` huang ying
2012-04-18 20:51 ` Rafael J. Wysocki
2012-04-19 2:08 ` huang ying
2012-04-19 12:36 ` Rafael J. Wysocki
2012-04-20 0:53 ` huang ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=cRTMk-NTvo+DJ2mAq6_ZeVLbeqiGx+ttZG6Hr_hQyyYkfLw@mail.gmail.com' \
--to=huang.ying.caritas@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
--cc=zheng.z.yan@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).