PCI/PM: refactor pci_pm_suspend_noirq()
PATCH v7 1/2 PCI/PM: refactor pci_pm_suspend_noirq()
The state of the device is saved during pci_pm_suspend_noirq(), if it has not already been saved, regardless of the skip_bus_pm flag value. So skip_bus_pm check is removed before saving the device state.
---
v1 -> v2: add comments to the changes
v2 -> v3: move changelog after "---" marker
v3 -> v4: add "---" marker after changelog
v4 -> v5: no change
v5 -> v6: no change
v6 -> v7: no change
--- drivers/pci/pci-driver.c | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-)
drivers/pci/pci-driver.c +6 -12
@@ -867,20 +867,14 @@ static int pci_pm_suspend_noirq(struct device *dev) } } -if (pci_dev->skip_bus_pm) { +if (!pci_dev->state_saved) { +pci_save_state (pci_dev);/* -* Either the device is a bridge with a child in D0 below it, or -* the function is running for the second time in a row without -* going through full resume, which is possible only during -* suspend-to-idle in a spurious wakeup case. The device should -* be in D0 at this point, but if it is a bridge, it may be -* necessary to save its state. +* If the device is a bridge with a child in D0 below it, it needs to +* stay in D0, so check skip_bus_pm to avoid putting it into a +* low-power state in that case. */ -if (!pci_dev->state_saved) -pci_save_state (pci_dev); - }else if (!pci_dev->state_saved) { -pci_save_state (pci_dev); -if (pci_power_manageable (pci_dev)) +if (!pci_dev->skip_bus_pm &&pci_power_manageable (pci_dev))pci_prepare_to_sleep (pci_dev); }
Signature · 1 line
2.25.1
PATCH v7 2/2 PCI/PM: Disable PTM on all devices
On receiving a PTM Request from a downstream device, if PTM is disabled on the root port, as per PCIe specification, such request would cause an Unsupported Request error. So disable PTM for any downstream devices. PTM state needs to be saved before disabling it to be restored later.
Set ptm_enabled from 'struct pci_dev' to 0 in pci_ptm_disable() and it is used in pci_save_state() before saving PTM state to avoid double save.
---
v1 -> v2: add Fixes tag in commit message
v2 -> v3: move changelog after "---" marker
v3 -> v4: add "---" marker after changelog
v4 -> v5: move pci_disable_ptm() out of the pci_dev->state_saved check.
disable PTM for all devices, not just root ports.
v5 -> v6: move pci_disable_ptm() to pci_pm_suspend()
set pci_dev->ptm_enabled to 0 in pci_ptm_disable() and it is used in pci_save_state() before saving PTM state to avoid double save. v6 -> v7: add #ifdef CONFIG_PCIE_PTM in pci_save_state() before saving PTM state --- drivers/pci/pci-driver.c | 21 ++++++++++++++++++++- drivers/pci/pci.c | 28 +++++++++++++--------------- drivers/pci/pcie/ptm.c | 1 + 3 files changed, 34 insertions(+), 16 deletions(-)
drivers/pci/pci-driver.c +20 -1
@@ -803,14 +803,33 @@ static int pci_pm_suspend(struct device *dev)pci_dev_adjust_pme (pci_dev); } +/* +* If a PTM Requester is put in a low-power state, a PTM Responder +* upstream from it may also be put in a low-power state. Putting a +* Port in D1, D2, or D3hot does not prohibit it from sending or +* responding to PTM Requests. We want to disable PTM on Responders +* when they are in a low-power state. Per 6.21.3, a PTM Requester +* must not be enabled when the upstream PTM Responder is disabled. +* Therefore, we must disable all PTM on all downstream PTM +* Requesters before disabling it on the PTM Responder, e.g., a Root +* Port. +* +* Also, to restore the PTM state, it needs to be saved before +* disabling it for all devices. +*/ +pci_save_ptm_state (pci_dev); +pci_disable_ptm (pci_dev); +if (pm->suspend) {pci_power_t prev = pci_dev->current_state;int error; error = pm->suspend (dev);suspend_report_result (dev, pm->suspend, error); -if (error) +if (error) { +pci_restore_ptm_state (pci_dev);return error; + }if (!pci_dev->state_saved && pci_dev->current_state !=PCI_D0 && pci_dev->current_state !=PCI_UNKNOWN ) {
drivers/pci/pci.c +13 -15
@@ -1669,7 +1669,15 @@ int pci_save_state(struct pci_dev *dev)pci_save_ltr_state (dev);pci_save_dpc_state (dev);pci_save_aer_state (dev); -pci_save_ptm_state (dev); +#ifdef CONFIG_PCIE_PTM +/* +* PCI PM core disables PTM during suspend and saves PTM state before +* that to be able to restore the ptm state restored later. So PCI core +* needs this check to avoid double save. +*/ +if (dev->ptm_enabled) +pci_save_ptm_state (dev); +#endif return pci_save_vc_state (dev); }EXPORT_SYMBOL (pci_save_state);
@@ -2710,24 +2718,12 @@ int pci_prepare_to_sleep(struct pci_dev *dev)if (target_state ==PCI_POWER_ERROR )return -EIO ; -/* -* There are systems (for example, Intel mobile chips since Coffee -* Lake) where the power drawn while suspended can be significantly -* reduced by disabling PTM on PCIe root ports as this allows the -* port to enter a lower-power PM state and the SoC to reach a -* lower-power idle state as a whole. -*/ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) -pci_disable_ptm (dev); -pci_enable_wake (dev, target_state, wakeup); error =pci_set_power_state (dev, target_state); -if (error) { +if (error)pci_enable_wake (dev, target_state, false); -pci_restore_ptm_state (dev); - }return error; }
@@ -2775,8 +2771,10 @@ int pci_finish_runtime_suspend(struct pci_dev *dev)* port to enter a lower-power PM state and the SoC to reach a * lower-power idle state as a whole. */ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) +if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) { +pci_save_ptm_state (dev);pci_disable_ptm (dev); + }__pci_enable_wake (dev, target_state,pci_dev_run_wake (dev));
drivers/pci/pcie/ptm.c +1 -0
@@ -44,6 +44,7 @@ void pci_disable_ptm(struct pci_dev *dev)pci_read_config_word (dev, ptm +PCI_PTM_CTRL , &ctrl); ctrl &= ~(PCI_PTM_CTRL_ENABLE |PCI_PTM_CTRL_ROOT );pci_write_config_word (dev, ptm +PCI_PTM_CTRL , ctrl); + dev->ptm_enabled =0 ; }void pci_save_ptm_state (struct pci_dev *dev)
Signature · 1 line
2.25.1
Re: [PATCH v7 2/2] PCI/PM: Disable PTM on all devices
Quoted 44 lines · Rajvi Jingar
On receiving a PTM Request from a downstream device, if PTM is disabled on the root port, as per PCIe specification, such request would cause an Unsupported Request error. So disable PTM for any downstream devices. PTM state needs to be saved before disabling it to be restored later.
Set
ptm_enabledfrom 'structpci_dev' to 0 inpci_ptm_disable()and it is used inpci_save_state()before saving PTM state to avoid double save.Fixes a697f072f5da ("PCI: Disable PTM during suspend to save power")Signed-off-by Rajvi Jingar <[email protected]>Suggested-by David E. Box <[email protected]>---
v1 -> v2: add Fixes tag in commit message
v2 -> v3: move changelog after "---" marker
v3 -> v4: add "---" marker after changelog
v4 -> v5: movepci_disable_ptm()out of thepci_dev->state_savedcheck.
disable PTM for all devices, not just root ports.
v5 -> v6: movepci_disable_ptm()topci_pm_suspend()set pci_dev->ptm_enabled to 0 in pci_ptm_disable() and it is used in pci_save_state() before saving PTM state to avoid double save. v6 -> v7: add #ifdef CONFIG_PCIE_PTM in pci_save_state() before saving PTM state --- drivers/pci/pci-driver.c | 21 ++++++++++++++++++++- drivers/pci/pci.c | 28 +++++++++++++--------------- drivers/pci/pcie/ptm.c | 1 + 3 files changed, 34 insertions(+), 16 deletions(-)drivers/pci/pci-driver.c +6
-0@@ -803,14 +803,33 @@ static int pci_pm_suspend(struct device *dev)pci_dev_adjust_pme (pci_dev); } +/* +* If a PTM Requester is put in a low-power state, a PTM Responder +* upstream from it may also be put in a low-power state. Putting a +* Port in D1, D2, or D3hot does not prohibit it from sending or +* responding to PTM Requests. We want to disable PTM on Responders +* when they are in a low-power state. Per 6.21.3, a PTM Requester
drivers/pci/pci-driver.c static int pci_pm_suspend(struct device *dev) · line 821
Quoted 10 lines
drivers/pci/pci-driver.c +10
-0+* must not be enabled when the upstream PTM Responder is disabled. +* Therefore, we must disable all PTM on all downstream PTM +* Requesters before disabling it on the PTM Responder, e.g., a Root +* Port. +* +* Also, to restore the PTM state, it needs to be saved before +* disabling it for all devices. +*/ +pci_save_ptm_state (pci_dev); +pci_disable_ptm (pci_dev);
I think this is a little bit too magical. The PTM disable doesn't really fit here in pci_pm_suspend(). It's more like the wakeup configuration done by pci_pm_suspend_noirq() in pci_prepare_to_sleep().
IIUC, the reason it's here in pci_pm_suspend() is because of the weird nvme thing where nvme_suspend() puts the device in a device-specific low-power flavor of D0 and subsequent config accesses take it out of that low-power situation [1].
I don't think this is a maintainable situation because there's nothing about this pci_disable_ptm() that says "this cannot be done after pm->suspend()". That's a completely nvme-specific thing that we can't deduce from the code and are likely to break in the future.
We *do* have the rule that if the driver sets pdev->state_saved (normally by calling pci_save_state()), it means the driver is responsible for *all* the device state, even the standard config space that the PCI core would normally handle.
When the driver does set pdev->state_saved, I don't think pci_pm_suspend_noirq() actually touches the device itself, and I'm a little more comfortable relying on that assumption.
If this nvme weirdness plays a part here, I think the commit log and probably a comment really should mention what's going on because it's just feels fragile.
[1] https://lore.kernel.org/r/CAJZ5v0iNaAd=yP3DgDVVpffKU6kt+nSpPeqxWJyRddaX5K4FRA@mail.gmail.com
Quoted 22 lines
drivers/pci/pci-driver.c +3
-1if (pm->suspend) {pci_power_t prev = pci_dev->current_state;int error; error = pm->suspend (dev);suspend_report_result (dev, pm->suspend, error); -if (error) +if (error) { +pci_restore_ptm_state (pci_dev);return error; + }if (!pci_dev->state_saved && pci_dev->current_state !=PCI_D0 && pci_dev->current_state !=PCI_UNKNOWN ) {drivers/pci/pci.c +0
-0@@ -1669,7 +1669,15 @@ int pci_save_state(struct pci_dev *dev)pci_save_ltr_state (dev);pci_save_dpc_state (dev);pci_save_aer_state (dev);
drivers/pci/pci.c int pci_save_state(struct pci_dev *dev) · line 1680
Quoted 10 lines
drivers/pci/pci.c +9
-1-pci_save_ptm_state (dev); +#ifdef CONFIG_PCIE_PTM +/* +* PCI PM core disables PTM during suspend and saves PTM state before +* that to be able to restore the ptm state restored later. So PCI core +* needs this check to avoid double save. +*/ +if (dev->ptm_enabled) +pci_save_ptm_state (dev); +#endif
This ptm_enabled check doesn't fit with the rest of the function and the semantics are fairly complicated.
Quoted 46 lines
drivers/pci/pci.c +4
-14return pci_save_vc_state (dev); }EXPORT_SYMBOL (pci_save_state);@@ -2710,24 +2718,12 @@ int pci_prepare_to_sleep(struct pci_dev *dev)if (target_state ==PCI_POWER_ERROR )return -EIO ; -/* -* There are systems (for example, Intel mobile chips since Coffee -* Lake) where the power drawn while suspended can be significantly -* reduced by disabling PTM on PCIe root ports as this allows the -* port to enter a lower-power PM state and the SoC to reach a -* lower-power idle state as a whole. -*/ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) -pci_disable_ptm (dev); -pci_enable_wake (dev, target_state, wakeup); error =pci_set_power_state (dev, target_state); -if (error) { +if (error)pci_enable_wake (dev, target_state, false); -pci_restore_ptm_state (dev); - }return error; }@@ -2775,8 +2771,10 @@ int pci_finish_runtime_suspend(struct pci_dev *dev)* port to enter a lower-power PM state and the SoC to reach a * lower-power idle state as a whole. */ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) +if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) { +pci_save_ptm_state (dev);pci_disable_ptm (dev); + }__pci_enable_wake (dev, target_state,pci_dev_run_wake (dev));drivers/pci/pcie/ptm.c +0
-0
drivers/pci/pcie/ptm.c void pci_disable_ptm(struct pci_dev *dev) · line 47
Quoted 4 lines
drivers/pci/pcie/ptm.c +1
-0@@ -44,6 +44,7 @@ void pci_disable_ptm(struct pci_dev *dev)pci_read_config_word (dev, ptm +PCI_PTM_CTRL , &ctrl); ctrl &= ~(PCI_PTM_CTRL_ENABLE |PCI_PTM_CTRL_ROOT );pci_write_config_word (dev, ptm +PCI_PTM_CTRL , ctrl); + dev->ptm_enabled =0 ;
This looks like a bug fix that could be in a separate patch.
drivers/pci/pcie/ptm.c void pci_disable_ptm(struct pci_dev *dev) · line 50
Quoted 3 lines
drivers/pci/pcie/ptm.c +0
-0}void pci_save_ptm_state (struct pci_dev *dev)
I think something like the sketch below would fit better in the power management framework. PTM disable is closely related to device power states, so I tried to put it as close as possible to the power state transitions. I'm sure there are things missing and things I'm overlooking:
drivers/pci/pci.c +8 -12
@@ -2705,28 +2705,21 @@ int pci_prepare_to_sleep(struct pci_dev *dev) {bool wakeup =device_may_wakeup (&dev->dev);pci_power_t target_state =pci_target_state (dev, wakeup); +bool ptm =pcie_ptm_enabled (dev);int error;if (target_state ==PCI_POWER_ERROR )return -EIO ; -/* -* There are systems (for example, Intel mobile chips since Coffee -* Lake) where the power drawn while suspended can be significantly -* reduced by disabling PTM on PCIe root ports as this allows the -* port to enter a lower-power PM state and the SoC to reach a -* lower-power idle state as a whole. -*/ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) -pci_disable_ptm (dev); - +pci_disable_ptm (dev);pci_enable_wake (dev, target_state, wakeup); error =pci_set_power_state (dev, target_state);if (error) {pci_enable_wake (dev, target_state, false); -pci_restore_ptm_state (dev); +if (ptm) +pci_enable_ptm (dev); }return error;
@@ -2762,6 +2755,7 @@ EXPORT_SYMBOL(pci_back_from_sleep);int pci_finish_runtime_suspend (struct pci_dev *dev) {pci_power_t target_state; +bool ptm =pcie_ptm_enabled (dev);int error; target_state =pci_target_state (dev,device_can_wakeup (&dev->dev));
@@ -2778,13 +2772,15 @@ int pci_finish_runtime_suspend(struct pci_dev *dev)if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT )pci_disable_ptm (dev); +pci_disable_ptm (dev);__pci_enable_wake (dev, target_state,pci_dev_run_wake (dev)); error =pci_set_power_state (dev, target_state);if (error) {pci_enable_wake (dev, target_state, false); -pci_restore_ptm_state (dev); +if (ptm) +pci_enable_ptm (dev); }return error;
Re: [PATCH v7 2/2] PCI/PM: Disable PTM on all devices
Sorry for the delay here.
Quoted 67 lines · Bjorn Helgaas
Quoted 44 lines · Rajvi Jingar
On receiving a PTM Request from a downstream device, if PTM is disabled on the root port, as per PCIe specification, such request would cause an Unsupported Request error. So disable PTM for any downstream devices. PTM state needs to be saved before disabling it to be restored later.
Set
ptm_enabledfrom 'structpci_dev' to 0 inpci_ptm_disable()and it is used inpci_save_state()before saving PTM state to avoid double save.Fixes a697f072f5da ("PCI: Disable PTM during suspend to save power")Signed-off-by Rajvi Jingar <[email protected]>Suggested-by David E. Box <[email protected]>---
v1 -> v2: add Fixes tag in commit message
v2 -> v3: move changelog after "---" marker
v3 -> v4: add "---" marker after changelog
v4 -> v5: movepci_disable_ptm()out of thepci_dev->state_savedcheck.
disable PTM for all devices, not just root ports.
v5 -> v6: movepci_disable_ptm()topci_pm_suspend()
setpci_dev->ptm_enabledto 0 inpci_ptm_disable()and it is used inpci_save_state()before saving PTM state to avoid double save.
v6 -> v7: add #ifdefCONFIG_PCIE_PTMinpci_save_state()before saving
PTM state--- drivers/pci/pci-driver.c | 21 ++++++++++++++++++++- drivers/pci/pci.c | 28 +++++++++++++--------------- drivers/pci/pcie/ptm.c | 1 + 3 files changed, 34 insertions(+), 16 deletions(-)drivers/pci/pci-driver.c +6
-0@@ -803,14 +803,33 @@ static int pci_pm_suspend(struct device *dev)pci_dev_adjust_pme (pci_dev); } +/* +* If a PTM Requester is put in a low-power state, a PTM Responder +* upstream from it may also be put in a low-power state. Putting a +* Port in D1, D2, or D3hot does not prohibit it from sending or +* responding to PTM Requests. We want to disable PTM on Responders +* when they are in a low-power state. Per 6.21.3, a PTM Requester drivers/pci/pci-driver.c static int pci_pm_suspend(struct device *dev) · line 821
Quoted 10 lines
drivers/pci/pci-driver.c +10
-0+* must not be enabled when the upstream PTM Responder is disabled. +* Therefore, we must disable all PTM on all downstream PTM +* Requesters before disabling it on the PTM Responder, e.g., a Root +* Port. +* +* Also, to restore the PTM state, it needs to be saved before +* disabling it for all devices. +*/ +pci_save_ptm_state (pci_dev); +pci_disable_ptm (pci_dev);I think this is a little bit too magical. The PTM disable doesn't really fit here in
pci_pm_suspend(). It's more like the wakeup configuration done bypci_pm_suspend_noirq()inpci_prepare_to_sleep().IIUC, the reason it's here in
pci_pm_suspend()is because of the weird nvme thing wherenvme_suspend()puts the device in a device-specific low-power flavor of D0 and subsequent config accesses take it out of that low-power situation [1].
Quoted 4 lines
I don't think this is a maintainable situation because there's nothing about this
pci_disable_ptm()that says "this cannot be done afterpm->suspend()". That's a completely nvme-specific thing that we can't deduce from the code and are likely to break in the future.
Well, I'm not sure it is nvme-specific really.
Pretty much the same goes for any driver that wants to do their own power management (whatever it is) in the ->suspend() callback and indicate that by calling pci_save_state() by itself.
Quoted 8 lines
We *do* have the rule that if the driver sets
pdev->state_saved(normally by callingpci_save_state()), it means the driver is responsible for *all* the device state, even the standard config space that the PCI core would normally handle.When the driver does set
pdev->state_saved, I don't thinkpci_pm_suspend_noirq()actually touches the device itself, and I'm a little more comfortable relying on that assumption.
It can be relied on right now which is also why the $subject patch cannot put the PTM disabling in there and do it regardless of the state_saved value.
Quoted 3 lines
If this nvme weirdness plays a part here, I think the commit log and probably a comment really should mention what's going on because it's just feels fragile.
Totally agree on that one.
Quoted 93 lines
[1] https://lore.kernel.org/r/CAJZ5v0iNaAd=yP3DgDVVpffKU6kt+nSpPeqxWJyRddaX5K4FRA@mail.gmail.com
Quoted 22 lines
drivers/pci/pci-driver.c +3
-1if (pm->suspend) {pci_power_t prev = pci_dev->current_state;int error; error = pm->suspend (dev);suspend_report_result (dev, pm->suspend, error); -if (error) +if (error) { +pci_restore_ptm_state (pci_dev);return error; + }if (!pci_dev->state_saved && pci_dev->current_state !=PCI_D0 && pci_dev->current_state !=PCI_UNKNOWN ) {drivers/pci/pci.c +0
-0@@ -1669,7 +1669,15 @@ int pci_save_state(struct pci_dev *dev)pci_save_ltr_state (dev);pci_save_dpc_state (dev);pci_save_aer_state (dev);drivers/pci/pci.c int pci_save_state(struct pci_dev *dev) · line 1680
Quoted 10 lines
drivers/pci/pci.c +9
-1-pci_save_ptm_state (dev); +#ifdef CONFIG_PCIE_PTM +/* +* PCI PM core disables PTM during suspend and saves PTM state before +* that to be able to restore the ptm state restored later. So PCI core +* needs this check to avoid double save. +*/ +if (dev->ptm_enabled) +pci_save_ptm_state (dev); +#endif This
ptm_enabledcheck doesn't fit with the rest of the function and the semantics are fairly complicated.Quoted 46 lines
drivers/pci/pci.c +4
-14return pci_save_vc_state (dev); }EXPORT_SYMBOL (pci_save_state);@@ -2710,24 +2718,12 @@ int pci_prepare_to_sleep(struct pci_dev *dev)if (target_state ==PCI_POWER_ERROR )return -EIO ; -/* -* There are systems (for example, Intel mobile chips since Coffee -* Lake) where the power drawn while suspended can be significantly -* reduced by disabling PTM on PCIe root ports as this allows the -* port to enter a lower-power PM state and the SoC to reach a -* lower-power idle state as a whole. -*/ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) -pci_disable_ptm (dev); -pci_enable_wake (dev, target_state, wakeup); error =pci_set_power_state (dev, target_state); -if (error) { +if (error)pci_enable_wake (dev, target_state, false); -pci_restore_ptm_state (dev); - }return error; }@@ -2775,8 +2771,10 @@ int pci_finish_runtime_suspend(struct pci_dev *dev)* port to enter a lower-power PM state and the SoC to reach a * lower-power idle state as a whole. */ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) +if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) { +pci_save_ptm_state (dev);pci_disable_ptm (dev); + }__pci_enable_wake (dev, target_state,pci_dev_run_wake (dev));drivers/pci/pcie/ptm.c +0
-0drivers/pci/pcie/ptm.c void pci_disable_ptm(struct pci_dev *dev) · line 47
Quoted 4 lines
drivers/pci/pcie/ptm.c +1
-0@@ -44,6 +44,7 @@ void pci_disable_ptm(struct pci_dev *dev)pci_read_config_word (dev, ptm +PCI_PTM_CTRL , &ctrl); ctrl &= ~(PCI_PTM_CTRL_ENABLE |PCI_PTM_CTRL_ROOT );pci_write_config_word (dev, ptm +PCI_PTM_CTRL , ctrl); + dev->ptm_enabled =0 ;This looks like a bug fix that could be in a separate patch.
Quoted 2 lines
drivers/pci/pcie/ptm.c +0
-0}
Quoted 8 lines
drivers/pci/pcie/ptm.c void pci_disable_ptm(struct pci_dev *dev) · line 50
Quoted 1 line
drivers/pci/pcie/ptm.c +0
-0void pci_save_ptm_state (struct pci_dev *dev)I think something like the sketch below would fit better in the power management framework. PTM disable is closely related to device power states, so I tried to put it as close as possible to the power state transitions. I'm sure there are things missing and things I'm overlooking:
There are PCI devices that pci_prepare_to_sleep() is not called for, so disabling PTM in there may not work in general.
Quoted 62 lines
drivers/pci/pci.c +8
-12@@ -2705,28 +2705,21 @@ int pci_prepare_to_sleep(struct pci_dev *dev) {bool wakeup =device_may_wakeup (&dev->dev);pci_power_t target_state =pci_target_state (dev, wakeup); +bool ptm =pcie_ptm_enabled (dev);int error;if (target_state ==PCI_POWER_ERROR )return -EIO ; -/* -* There are systems (for example, Intel mobile chips since Coffee -* Lake) where the power drawn while suspended can be significantly -* reduced by disabling PTM on PCIe root ports as this allows the -* port to enter a lower-power PM state and the SoC to reach a -* lower-power idle state as a whole. -*/ -if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT ) -pci_disable_ptm (dev); - +pci_disable_ptm (dev);pci_enable_wake (dev, target_state, wakeup); error =pci_set_power_state (dev, target_state);if (error) {pci_enable_wake (dev, target_state, false); -pci_restore_ptm_state (dev); +if (ptm) +pci_enable_ptm (dev); }return error;@@ -2762,6 +2755,7 @@ EXPORT_SYMBOL(pci_back_from_sleep);int pci_finish_runtime_suspend (struct pci_dev *dev) {pci_power_t target_state; +bool ptm =pcie_ptm_enabled (dev);int error; target_state =pci_target_state (dev,device_can_wakeup (&dev->dev));@@ -2778,13 +2772,15 @@ int pci_finish_runtime_suspend(struct pci_dev *dev)if (pci_pcie_type (dev) ==PCI_EXP_TYPE_ROOT_PORT )pci_disable_ptm (dev); +pci_disable_ptm (dev);__pci_enable_wake (dev, target_state,pci_dev_run_wake (dev)); error =pci_set_power_state (dev, target_state);if (error) {pci_enable_wake (dev, target_state, false); -pci_restore_ptm_state (dev); +if (ptm) +pci_enable_ptm (dev); }return error;