From: Phillip Susi <psusi@ubuntu.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: enabling aspm on ati radeon
Date: Fri, 17 May 2013 19:36:53 -0400 [thread overview]
Message-ID: <5196BF15.3050208@ubuntu.com> (raw)
In-Reply-To: <CAErSpo4H-=dnHON3vDvJEme2hGD0z0r_NSsm-Bk9tZ4QqtBTCw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/17/2013 05:28 PM, Bjorn Helgaas wrote:> A link has two ends.
Both ends have to support ASPM in order for it
> to work. But ASPM on a particular link has no dependency on
> things elsewhere in the hierarchy.
Got you... I guess I was still thinking regular PCI and the naming
"root complex" made me think it was the whole root bridge, when it
really is that particular x16 pcie port that goes to the radeon.
> The link between 00:01.0 and 01:00.0 apparently only supports ASPM
> on one end (the downstream end), so ASPM won't work on it.
I'll check the Intel spec sheet again, but I'm pretty sure it really
does support ASPM. The CPU probably allows writes to the register,
and my bios must have configured it to say it doesn't support aspm. I
guess I just need to wrangle setpci into trying to enable it despite
it not advertising support, or maybe see if I can get grub to poke the
capability register to make it say it supports it.
One question I have though is how to identify which port device
corresponds to which downstream device connected to it. In other
words, how do you know 00:01.0 links to 01:00.0 ( other than seeing
that it's the x16 and knowing the radeon is plugged into the x16 slot ).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJRlr8VAAoJEJrBOlT6nu75zL8IAImEt+ql6u1pqDSFPuDlLwSE
fbFWYYxZAzEGnzbAKGMUhueKHAa4rEnH2ztM8CYxdj3GVfSoTpwgcvz21L/fq/6L
z4OtChaw2cDiCevi95BR2xry2qBLnrHNq1qbD1yb832b5njCSr5SnTvUBUiH/4pN
twEAJ3HZp7Vblts4UMmn5sOT3cGd1Yr6sJp4Y068vPSGyx5Ixm5ROYEedN5tBnBl
zkeC+2vYXk0nIbMgJLWt4ZJRxXmX3/DXt8F1VL12NzlHpotuS5rPRpTR/el3sSty
J6HH/jlgSm+L3zuSPTicVAQBvYGcRhi/NbKDFPnZGGB8E7HsE9SIwNxzjzImyV0=
=X54u
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-05-17 23:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <519443A1.8050905@ubuntu.com>
2013-05-16 8:58 ` enabling aspm on ati radeon Rafael J. Wysocki
2013-05-16 16:42 ` Bjorn Helgaas
[not found] ` <5195596C.3000406@ubuntu.com>
2013-05-17 17:31 ` Bjorn Helgaas
2013-05-17 18:04 ` Phillip Susi
2013-05-17 19:52 ` Bjorn Helgaas
2013-05-17 20:10 ` Phillip Susi
2013-05-17 20:24 ` Bjorn Helgaas
2013-05-17 21:12 ` Phillip Susi
2013-05-17 21:28 ` Bjorn Helgaas
2013-05-17 23:36 ` Phillip Susi [this message]
2013-05-17 23:52 ` Bjorn Helgaas
2013-05-18 0:15 ` Phillip Susi
2013-05-18 0:40 ` Bjorn Helgaas
2013-05-18 1:20 ` Phillip Susi
2013-05-20 13:34 ` Bjorn Helgaas
2013-05-20 20:01 ` Rafael J. Wysocki
2013-05-21 13:31 ` Phillip Susi
2013-05-21 18:50 ` Sebastian
2013-05-24 19:57 ` Phillip Susi
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=5196BF15.3050208@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
/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