On Fri, May 17, 2013 at 12:04 PM, Phillip Susi <psusi@xxxxxxxxxx> wrote:
> -----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?
Nope, that one shouldn't affect the other devices. I was just curious.
I just sent a patch to make lspci decode all possible values there.
In the PCIe r2.1 spec, only 1 ("L0s") and 3 ("L0s and L1") were
defined. The r3 spec added 0 ("not supported") and 2 ("L1"), but
lspci hadn't quite kept up.
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
