[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200902071448.13877.rjw@sisk.pl>
Date: Sat, 7 Feb 2009 14:48:13 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Pavel Machek <pavel@...e.cz>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux PCI <linux-pci@...r.kernel.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] PCI PM: Do not disable and enable bridges during suspend-resume
On Saturday 07 February 2009, Pavel Machek wrote:
> Hi!
>
> > their standard config spaces are restored. Fix this by not attempting
> > to disable bridges during suspend and enable them during resume.
>
> ...
>
> > Index: linux-2.6/drivers/pci/pci-driver.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/pci/pci-driver.c
> > +++ linux-2.6/drivers/pci/pci-driver.c
> > @@ -428,16 +428,18 @@ static int pci_pm_default_resume(struct
> > {
> > pci_fixup_device(pci_fixup_resume, pci_dev);
> >
> > - if (!pci_is_bridge(pci_dev))
> > - pci_enable_wake(pci_dev, PCI_D0, false);
> > + if (pci_is_bridge(pci_dev))
> > + return 0;
> >
> > + pci_enable_wake(pci_dev, PCI_D0, false);
> > return pci_pm_reenable_device(pci_dev);
> > }
>
> Are you sure? This goes from doing reenable_device to not doing it for
> bridges, seemingly contradicting changelog?
Can you explain what you mean, please?
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists