From: Andrew Morton <akpm@linux-foundation.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, jbarnes@virtuousgeek.org,
linux-kernel@vger.kernel.org, mjg@redhat.com
Subject: Re: [PATCH] PCI: Enable ASPM state clearing regardless of policy
Date: Thu, 7 Apr 2011 15:23:10 -0700 [thread overview]
Message-ID: <20110407152310.5bfeab8b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110310185351.3394.54996.stgit@s20.home>
On Thu, 10 Mar 2011 11:54:16 -0700
Alex Williamson <alex.williamson@redhat.com> wrote:
> Commit 2f671e2d allowed us to clear ASPM state when the FADT
> tells us it isn't supported, but we don't put this into effect
> if the aspm_policy is set to POLICY_POWERSAVE. Enable the
> state to be cleared regardless of policy.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> drivers/pci/pcie/aspm.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
> index 3188cd9..eb8ac5c 100644
> --- a/drivers/pci/pcie/aspm.c
> +++ b/drivers/pci/pcie/aspm.c
> @@ -607,7 +607,7 @@ void pcie_aspm_init_link_state(struct pci_dev *pdev)
> * the BIOS's expectation, we'll do so once pci_enable_device() is
> * called.
> */
> - if (aspm_policy != POLICY_POWERSAVE) {
> + if (aspm_policy != POLICY_POWERSAVE || aspm_clear_state) {
> pcie_config_aspm_path(link);
> pcie_set_clkpm(link, policy_to_clkpm_state(link));
> }
hm. why. Presumably this change has some user-observeable effect.
What is that effect, and why is it desirable? ;)
next prev parent reply other threads:[~2011-04-07 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 18:54 [PATCH] PCI: Enable ASPM state clearing regardless of policy Alex Williamson
2011-04-07 22:23 ` Andrew Morton [this message]
2011-04-08 2:24 ` Alex Williamson
2011-04-08 19:50 ` Jesse Barnes
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=20110407152310.5bfeab8b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg@redhat.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