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 14:04:42 -0400 [thread overview]
Message-ID: <5196713A.1010102@ubuntu.com> (raw)
In-Reply-To: <CAErSpo6wSgquzJc22tFJozp8cfx0vpULnO3KZN2gr2YHt8EHrw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 5/17/2013 1:31 PM, Bjorn Helgaas wrote:
> You also have this bridge where lspci says "ASPM unknown":
>
> 00:01.0 bridge to [bus 01] ASPM unknown
>
> Just out of curiosity, can you collect the output of "lspci -xxxs
> 00:01.0"? There are only two bits in the Link Capabilities ASPM
> support field, and all four encodings are defined, so I'm curious
> about why lspci says "unknown".
I'll get that as soon as I get home, but why would the ASPM status of
the root complex have anything to do with the rest of the devices?
Enabling ASPM on one link doesn't require it to be enabled on all
upstream links does it?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRlnE6AAoJEJrBOlT6nu75nWUIAI7iOcoOklDWhS1FriQJmXTm
X8OJ4VZB8VVPeIuzrW+I6sppUrxqpnnxvrJT7Trnh5SDwwJjwx3m6BVrZHphrlCN
armoZ5jLSuBS9mn4mpeAOfUS7uypAuyL4fEo6DYJa9fPZycL1LukjkuwZMRJ+bfw
sjXQ7soHC52r2wxWhDHZbOl9UEWtYHhBypoI+PpYMO00lQp3gGnJXedm2zHti+a3
2ZtIieydLw++nXDr18WxDbJ5h1rQi626rVip0IcO6VUhhNxcd8hzGFkRAc7vNodw
bjW6wp8f+sddfX5uHkh9zYzwaEblLgBkxqw93xzRdh1ujJHet4R/jL1NTLZ8EZY=
=W4Uc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-05-17 18:04 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 [this message]
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
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=5196713A.1010102@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