diff options
author | Wang Dongsheng <dongsheng.wang@freescale.com> | 2014-04-25 07:59:49 (GMT) |
---|---|---|
committer | Jose Rivera <German.Rivera@freescale.com> | 2014-04-29 16:16:59 (GMT) |
commit | 9659e78cb8f5f086f661cd0b7f6b32bce18bbc34 (patch) | |
tree | aa2d93f9b698239804ade8fd2ce257487f4c5ad1 /mm/zbud.c | |
parent | 4f7b508a0a88bf49cd4ac0747769a3dc966034ad (diff) | |
download | linux-fsl-qoriq-9659e78cb8f5f086f661cd0b7f6b32bce18bbc34.tar.xz |
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Change-Id: Id82d2e92994e466de1b2a4eb9ecef73c112ec753
Reviewed-on: http://git.am.freescale.net:8181/11538
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Yang Li <LeoLi@freescale.com>
Reviewed-by: Jose Rivera <German.Rivera@freescale.com>
Diffstat (limited to 'mm/zbud.c')
0 files changed, 0 insertions, 0 deletions