From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: Len Brown <lenb@kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Matthew Wilcox <matthew@wil.cx>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [RFC][PATCH 6/10] PCI PM: Rearrange code in pci-driver.c
Date: Mon, 5 Jan 2009 14:32:27 +0100 [thread overview]
Message-ID: <200901051432.27718.rjw@sisk.pl> (raw)
In-Reply-To: <20090105112501.GK27199@atrey.karlin.mff.cuni.cz>
On Monday 05 January 2009, Pavel Machek wrote:
> Hi!
>
> > Rename two functions and rearrange code in drivers/pci/pci-driver.c
> > so that it's easier to follow. In particular, separate invocations
> > of the legacy callbacks from the rest of the new callbacks' code.
> >
> > No functional changes should result from this.
> >
> > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> > ---
> > drivers/pci/pci-driver.c | 104 +++++++++++++++++++++++++++++------------------
> > 1 file changed, 65 insertions(+), 39 deletions(-)
> >
>
> > @@ -504,17 +504,21 @@ static int pci_pm_suspend(struct device
> > struct device_driver *drv = dev->driver;
> > int error = 0;
> >
> > + if (pci_has_legacy_pm_support(pci_dev)) {
> > + error = pci_legacy_suspend(dev, PMSG_SUSPEND);
> > + goto Exit;
> > + }
> > +
> > if (drv && drv->pm) {
> > if (drv->pm->suspend) {
> > error = drv->pm->suspend(dev);
> > suspend_report_result(drv->pm->suspend, error);
> > }
> > - } else if (pci_has_legacy_pm_support(pci_dev)) {
> > - error = pci_legacy_suspend(dev, PMSG_SUSPEND);
> > } else {
> > pci_pm_default_suspend(pci_dev);
> > }
> >
>
> Does this mean that pci_has_legacy_pm_support() => !(drv && drv->pm) ?
Yes, it does.
> Should pci_has_legacy_pm_support() check for that and WARN() in case
> both sets of callbacks are set?
Yes, I think I can add a WARN_ON() in there.
Thanks,
Rafael
next prev parent reply other threads:[~2009-01-05 13:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812190049.34343.rjw@sisk.pl>
2008-12-28 15:07 ` [RFC][PATCH] PCI PM: Make new suspend-resume callbacks carry out core operations (rev. 2) Rafael J. Wysocki
2008-12-30 22:33 ` [RFC][PATCH 0/10] PCI PM: Make new suspend-resume callbacks carry out core operations Rafael J. Wysocki
2008-12-30 22:35 ` [RFC][PATCH 1/10] PCI PM: Fix poweroff and restore callbacks Rafael J. Wysocki
2009-01-05 10:00 ` Pavel Machek
2008-12-30 22:37 ` [RFC][PATCH 2/10] PCI PM: Add suspend counterpart of pci_reenable_device Rafael J. Wysocki
2009-01-05 10:49 ` Pavel Machek
2009-01-05 13:17 ` Rafael J. Wysocki
2008-12-30 22:38 ` [RFC][PATCH 3/10] PCI PM: Power-manage devices without drivers during suspend-resume Rafael J. Wysocki
2009-01-05 10:51 ` Pavel Machek
2008-12-30 22:40 ` [RFC][PATCH 4/10] PCI PM: Move pci_has_legacy_pm_support Rafael J. Wysocki
2009-01-05 10:51 ` Pavel Machek
2008-12-30 22:41 ` [RFC][PATCH 5/10] PCI PM: Avoid touching devices behind bridges in unknown state Rafael J. Wysocki
2009-01-01 21:09 ` [RFC][PATCH 5/10] PCI PM: Avoid touching devices behind bridges in unknown state (rev. 2) Rafael J. Wysocki
2009-01-05 10:58 ` Pavel Machek
2009-01-05 13:30 ` Rafael J. Wysocki
2009-01-07 22:32 ` Pavel Machek
2009-01-07 23:02 ` Rafael J. Wysocki
2008-12-30 22:43 ` [RFC][PATCH 6/10] PCI PM: Rearrange code in pci-driver.c Rafael J. Wysocki
2009-01-05 11:25 ` Pavel Machek
2009-01-05 13:32 ` Rafael J. Wysocki [this message]
2008-12-30 22:44 ` [RFC][PATCH 7/10] PCI PM: Call pci_fixup_device from legacy routines Rafael J. Wysocki
2009-01-05 11:25 ` Pavel Machek
2008-12-30 22:45 ` [RFC][PATCH 8/10] PCI PM: Register power state of devices during initialization Rafael J. Wysocki
2009-01-05 11:19 ` Pavel Machek
2008-12-30 22:47 ` [RFC][PATCH 9/10] PCI PM: Run default PM callbacks for all devices using new framework Rafael J. Wysocki
2009-01-05 11:26 ` Pavel Machek
2008-12-30 22:49 ` [RFC][PATCH 10/10] PCI PM: Put PM callbacks in the order of execution Rafael J. Wysocki
2009-01-05 11:21 ` Pavel Machek
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=200901051432.27718.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=matthew@wil.cx \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®