linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Colin Ian King <colin.king@canonical.com>
To: Andy Whitcroft <robobotbotbot@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Matthew Garrett <mjg@redhat.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Colin King <colin.king@canonical.com>
Subject: Re: [PATCH] PCI: Allow pcie_aspm=force to work even when FADT indicates it is unsupported
Date: Fri, 30 Mar 2012 11:05:08 +0100	[thread overview]
Message-ID: <4F758554.1060907@canonical.com> (raw)
In-Reply-To: <CAAq6er0DUGcT_PuL3gOBNdcEVDxhW8EuP1dfFa_Sa9vNZmhfQA@mail.gmail.com>

On 30/03/12 10:55, Andy Whitcroft wrote:
> On Thu, Mar 22, 2012 at 4:49 PM, Colin King<colin.king@canonical.com>  wrote:
>> From: Colin Ian King<colin.king@canonical.com>
>>
>> Right now using pcie_aspm=force will not enable ASPM if the FADT indicates
>> ASPM is unsupported.  However, the semantics of force should probably allow
>> for this, especially as they did before the ASPM disable rework with commit
>> 3c076351c4027a56d5005a39a0b518a4ba393ce2
>>
>> This patch just skips the clearing of any ASPM setup that the firmware has
>> carried out on this bus if pcie_aspm=force is being used.
>>
>> BugLink: https://bugs.launchpad.net/ubuntu/+bug/962038
>>
>> Signed-off-by: Colin Ian King<colin.king@canonical.com>
>> ---
>>   drivers/pci/pcie/aspm.c |    3 +++
>>   1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
>> index 24f049e..e406429 100644
>> --- a/drivers/pci/pcie/aspm.c
>> +++ b/drivers/pci/pcie/aspm.c
>> @@ -783,6 +783,9 @@ void pcie_clear_aspm(struct pci_bus *bus)
>>   {
>>         struct pci_dev *child;
>>
>> +       if (aspm_force)
>> +               return;
>> +
>>         /*
>>          * Clear any ASPM setup that the firmware has carried out on this bus
>>          */
>> --
>> 1.7.9.1
> Andrew, I believe the above is also needed to fix some additional
> regressions with the new ASPM code.  If you are picking up the one
> below this probably should go with it:
>
>      + aspm-fix-pcie-devices-with-non-pcie-children.patch added to -mm tree
Just to add, I have tested this on a variety of modern SNB i3 based 
laptops (Dell, Lenovo) and also user has tested this and has confirmed 
it works.

Colin

      reply	other threads:[~2012-03-30 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 16:49 [PATCH] PCI: Allow pcie_aspm=force to work even when FADT indicates it is unsupported Colin King
2012-03-30  9:55 ` Andy Whitcroft
2012-03-30 10:05   ` Colin Ian King [this message]

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=4F758554.1060907@canonical.com \
    --to=colin.king@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=robobotbotbot@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;
as well as URLs for NNTP newsgroup(s).