diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2010-02-17 23:39:08 +0100 |
---|---|---|
committer | Jesse Barnes <jbarnes@virtuousgeek.org> | 2010-02-22 16:20:31 -0800 |
commit | c7f486567c1d0acd2e4166c47069835b9f75e77b (patch) | |
tree | 5552890ac80fc53f61dd9c53a6211610375efa1f /sound/usb | |
parent | 58ff463396ad00828e922d50998787e97fd32512 (diff) | |
download | linux-3.10-c7f486567c1d0acd2e4166c47069835b9f75e77b.tar.gz linux-3.10-c7f486567c1d0acd2e4166c47069835b9f75e77b.tar.bz2 linux-3.10-c7f486567c1d0acd2e4166c47069835b9f75e77b.zip |
PCI PM: PCIe PME root port service driver
PCIe native PME detection mechanism is based on interrupts generated
by root ports or event collectors every time a PCIe device sends a
PME message upstream.
Once a PME message has been sent by an endpoint device and received
by its root port (or event collector in the case of root complex
integrated endpoints), the Requester ID from the message header is
registered in the root port's Root Status register. At the same
time, the PME Status bit of the Root Status register is set to
indicate that there's a PME to handle. If PCIe PME interrupt is
enabled for the root port, it generates an interrupt once the PME
Status has been set. After receiving the interrupt, the kernel can
identify the PCIe device that generated the PME using the Requester
ID from the root port's Root Status register. [For details, see PCI
Express Base Specification, Rev. 2.0.]
Implement a driver for the PCIe PME root port service working in
accordance with the above description.
Based on a patch from Shaohua Li <shaohua.li@intel.com>.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'sound/usb')
0 files changed, 0 insertions, 0 deletions