From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ajaykumar Hotchandani <ajaykumar.hotchandani@oracle.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Set device power state to PCI_D0 for device without native PM support
Date: Thu, 6 Oct 2011 19:20:42 +0200 [thread overview]
Message-ID: <201110061920.42557.rjw@sisk.pl> (raw)
In-Reply-To: <CAE9FiQUjsa5CtpiqgMgHpt7av+v5NZFFOtuKC0a10Hwgwtm0Jg@mail.gmail.com>
On Thursday, October 06, 2011, Yinghai Lu wrote:
> On Wed, Oct 5, 2011 at 12:41 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > Hi,
> >> drivers/pci/pci.c | 3 +++
> >> 1 files changed, 3 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> >> index e9651f0..ca8c82d 100644
> >> --- a/drivers/pci/pci.c
> >> +++ b/drivers/pci/pci.c
> >> @@ -664,6 +664,9 @@ static int pci_platform_power_transition(struct pci_dev *dev, pci_power_t state)
> >> error = platform_pci_set_power_state(dev, state);
> >> if (!error)
> >> pci_update_current_state(dev, state);
> >> + /* Fall back to PCI_D0 if native PM is not supported */
> >> + else if (!dev->pm_cap)
> >> + dev->current_state = PCI_D0;
> >> } else {
> >> error = -ENODEV;
> >> /* Fall back to PCI_D0 if native PM is not supported */
> >>
> >
> > I have some vague memories that we tried that and it broke something.
>
> Do have any hint for us to dig out the configuration for failing?
>
> >
> > How thoroughly has it been tested?
>
> tested in setups with intel cpus from Nehalem.
Can you test it on older hardware too, please?
Rafael
next prev parent reply other threads:[~2011-10-06 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 11:34 [PATCH] PCI: Set device power state to PCI_D0 for device without native PM support Ajaykumar Hotchandani
2011-10-05 19:41 ` Rafael J. Wysocki
2011-10-06 16:10 ` Yinghai Lu
2011-10-06 17:20 ` Rafael J. Wysocki [this message]
2011-10-06 10:39 ` Stefano Stabellini
2011-10-06 16:05 ` Yinghai Lu
2011-10-06 16:17 ` Stefano Stabellini
2011-10-10 12:02 ` Ajaykumar Hotchandani
2011-10-13 14:30 ` Stefano Stabellini
2011-10-18 13:52 ` Ajaykumar Hotchandani
2011-10-27 13:14 ` Stefano Stabellini
2011-10-27 14:34 ` Ajaykumar Hotchandani
2011-10-27 15:01 ` Stefano Stabellini
2011-10-28 12:06 ` Ajaykumar Hotchandani
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=201110061920.42557.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ajaykumar.hotchandani@oracle.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yhlu.kernel@gmail.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