linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Rajvi Jingar <rajvi.jingar@intel.com>,
	bhelgaas@google.com, david.e.box@linux.intel.com,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v4 1/2] PCI/PM: refactor pci_pm_suspend_noirq()
Date: Wed, 20 Apr 2022 11:30:26 -0500	[thread overview]
Message-ID: <20220420163026.GA1304353@bhelgaas> (raw)
In-Reply-To: <cb94e592-0fd8-3274-aeeb-49fbd6f74761@intel.com>

On Thu, Apr 14, 2022 at 07:53:25PM +0200, Rafael J. Wysocki wrote:
> On 3/25/2022 8:50 PM, Rajvi Jingar wrote:
> > 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.
> > 
> > Signed-off-by: Rajvi Jingar <rajvi.jingar@intel.com>
> > Suggested-by: David E. Box <david.e.box@linux.intel.com>
> 
> Sorry for the delay here.
> 
> Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Rajvi, can you post these again?  It looks like they didn't make it to
the linux-pci mailing list, and I can't find them in the lore archives:

  https://lore.kernel.org/all/?q=f%3Arajvi.jingar

Maybe some formatting issue that vger didn't like?  Some possible
issues here:

  http://vger.kernel.org/majordomo-info.html

They should appear on the list so others can comment and so the lore
URL can be included in the commit when applying.

Please incorporate Rafael's reviewed-by when you repost.

> > ---
> >   v1 -> v2: add comments to the changes
> >   v2 -> v3: move changelog after "---" marker
> >   v3 -> v4: add "---" marker after changelog
> > ---
> >   drivers/pci/pci-driver.c | 18 ++++++------------
> >   1 file changed, 6 insertions(+), 12 deletions(-)
> > 
> > diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> > index 4ceeb75fc899..8b55a90126a2 100644
> > --- a/drivers/pci/pci-driver.c
> > +++ b/drivers/pci/pci-driver.c
> > @@ -845,20 +845,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);
> >   	}
> 
> 

  reply	other threads:[~2022-04-20 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220325195053.769373-1-rajvi.jingar@intel.com>
2022-04-14 17:53 ` [PATCH v4 1/2] PCI/PM: refactor pci_pm_suspend_noirq() Rafael J. Wysocki
2022-04-20 16:30   ` Bjorn Helgaas [this message]
     [not found] ` <20220325195053.769373-2-rajvi.jingar@intel.com>
2022-04-14 17:54   ` [PATCH v4 2/2] PCI/PM: Fix pci_pm_suspend_noirq() to disable PTM Rafael J. Wysocki
2022-04-22 22:24     ` Bjorn Helgaas
2022-04-23  0:43       ` Jingar, Rajvi
2022-04-23 15:01         ` Bjorn Helgaas
2022-04-25 18:32           ` David E. Box
2022-04-25 18:39             ` Rafael J. Wysocki
2022-04-26 16:50             ` Bjorn Helgaas
2022-04-27  4:22               ` David E. Box

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=20220420163026.GA1304353@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=david.e.box@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rajvi.jingar@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).