aboutsummaryrefslogtreecommitdiff
path: root/arch/microblaze
diff options
context:
space:
mode:
authorWang Dongsheng <dongsheng.wang@freescale.com>2014-03-20 11:19:37 +0800
committerScott Wood <scottwood@freescale.com>2014-03-19 22:37:44 -0500
commit48b16180d0d91324e5d2423c6d53d97bbe3dcc14 (patch)
tree522da33ee1abe3f0a3ed55a337756903cb7ea74e /arch/microblaze
parent093943735718a28d45dcfcc74a737ed39e402893 (diff)
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> Signed-off-by: Scott Wood <scottwood@freescale.com>
Diffstat (limited to 'arch/microblaze')
0 files changed, 0 insertions, 0 deletions