Message ID | 20130909231345.30095.61638.stgit@bhelgaas-glaptop (mailing list archive) |
---|---|
State | New, archived |
Delegated to: | Bjorn Helgaas |
Headers | show |
Hi! > The PCIe Link Capabilities "L0s Exit Latency" is the latency to exit > L0s, not L0, so label it "L0s" instead of "L0". This matches the > way we label the Device Capabilities "Endpoint L0s Acceptable Latency" > field as "Latency L0s". This also adds "Exit" to the description to > help distinguish it from the "Acceptable Latency" fields in the > Device Capabilities register. Applied the whole patch set. Have a nice fortnight
diff --git a/ls-caps.c b/ls-caps.c index be19d38..a1a1546 100644 --- a/ls-caps.c +++ b/ls-caps.c @@ -753,7 +753,7 @@ static void cap_express_link(struct device *d, int where, int type) u16 w; t = get_conf_long(d, where + PCI_EXP_LNKCAP); - printf("\t\tLnkCap:\tPort #%d, Speed %s, Width x%d, ASPM %s, Latency L0 %s, L1 %s\n", + printf("\t\tLnkCap:\tPort #%d, Speed %s, Width x%d, ASPM %s, Exit Latency L0s %s, L1 %s\n", t >> 24, link_speed(t & PCI_EXP_LNKCAP_SPEED), (t & PCI_EXP_LNKCAP_WIDTH) >> 4, aspm_support((t & PCI_EXP_LNKCAP_ASPM) >> 10),
The PCIe Link Capabilities "L0s Exit Latency" is the latency to exit L0s, not L0, so label it "L0s" instead of "L0". This matches the way we label the Device Capabilities "Endpoint L0s Acceptable Latency" field as "Latency L0s". This also adds "Exit" to the description to help distinguish it from the "Acceptable Latency" fields in the Device Capabilities register. Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> --- ls-caps.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html