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 17:12:16 -0400 [thread overview]
Message-ID: <51969D30.1070502@ubuntu.com> (raw)
In-Reply-To: <CAErSpo6ZKB-4PTa_2Cthx_8S2txCbGyatbPmDUPYexCQFg-A=A@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 5/17/2013 4:24 PM, Bjorn Helgaas wrote:
> Oh, wait a minute... You mentioned the radeon driver. The Radeon
> device in your system is at 01:00.0, and that is below the 00:01.0
> bridge that said "ASPM unknown." If the bridge leading to the
> Radeon device doesn't support ASPM, then of course, we won't be
> able to turn on ASPM for it.
That's what I was asking about before when I said surely the bridge
higher up doesn't have to have aspm enabled in order to enable it on
the downstream link?
> That doesn't explain why we don't turn on ASPM for the *other*
> devices (03:00.0, 05:00.0, 06:00.0, 09:00.0) though.
00:01.0 says it is the root complex, so wouldn't that make it upstream
of *everything*? As I understand it, the root complex is built into
the CPU and has 16 lanes going to the video slot, and another 4 lanes
running at gen3 speed that Intel calls the DMI that goes to the PCH,
which has some internal functions, and bridges to another 20 pcie lanes.
Since the root complex is built into the cpu, I wouldn't think ASPM
could possibly make sense on it, so it showing that it doesn't support
ASPM makes sense to me. That doesn't seem like it should preclude
using ASPM on the link down to the video card.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRlp0wAAoJEJrBOlT6nu7543QIAMfU7GnhweyxmunYl8fKq0B9
KCX3PSQaXXmknKxKtSDPtI3BhuTN+5g9KjXX+tDngETRPwq/5ZRXhIAcNjQCpv0d
K5Io/1vh652Aa0eVm1Yae+ejBWB/hWSu/AM/U0L1wyWGqat53QwfSHlMcQOFeuxq
oHoRrE5JtmcSbRbWtXFsOgRx5iXkgMzcwDxZ93Z4djhWjYGX+pGSk0DOTlttG/AP
RyT+oKYs8BmCytk/9/PFE0v/CtaAiNjEL42WAgv3nJMNuezG/CiBeUi7q9+vqKE8
1r+kGTbenKeEkboROWHXN/JCq3IsKCkff6rQC/s+oXBdORpCw46PcwpBno5kK+Q=
=sZdM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-05-17 21:12 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 [this message]
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=51969D30.1070502@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