From: Bjorn Helgaas <bhelgaas@google.com>
To: Martin Mares <mj@ucw.cz>
Cc: Ben Hutchings <bhutchings@solarflare.com>, linux-pci@vger.kernel.org
Subject: [PATCH] lspci: Decode PCIe Link registers only for devices with links
Date: Wed, 28 Aug 2013 13:08:34 -0600 [thread overview]
Message-ID: <20130828190834.2198.99446.stgit@bhelgaas-glaptop> (raw)
Root Complex Integrated Endpoints and Root Complex Event Collectors do not
have links and are not permitted to implement Link or Link 2 registers,
per PCIe spec r3.0, sec 1.3.2.3. Decoding them is useless and misleading.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
---
ls-caps.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/ls-caps.c b/ls-caps.c
index 752a771..be19d38 100644
--- a/ls-caps.c
+++ b/ls-caps.c
@@ -1074,6 +1074,7 @@ cap_express(struct device *d, int where, int cap)
int type = (cap & PCI_EXP_FLAGS_TYPE) >> 4;
int size;
int slot = 0;
+ int link = 1;
printf("Express ");
if (verbose >= 2)
@@ -1104,9 +1105,11 @@ cap_express(struct device *d, int where, int cap)
printf("PCI/PCI-X to PCI-Express Bridge");
break;
case PCI_EXP_TYPE_ROOT_INT_EP:
+ link = 0;
printf("Root Complex Integrated Endpoint");
break;
case PCI_EXP_TYPE_ROOT_EC:
+ link = 0;
printf("Root Complex Event Collector");
break;
default:
@@ -1125,7 +1128,8 @@ cap_express(struct device *d, int where, int cap)
return;
cap_express_dev(d, where, type);
- cap_express_link(d, where, type);
+ if (link)
+ cap_express_link(d, where, type);
if (slot)
cap_express_slot(d, where);
if (type == PCI_EXP_TYPE_ROOT_PORT)
@@ -1141,7 +1145,8 @@ cap_express(struct device *d, int where, int cap)
return;
cap_express_dev2(d, where, type);
- cap_express_link2(d, where, type);
+ if (link)
+ cap_express_link2(d, where, type);
if (slot)
cap_express_slot2(d, where);
}
next reply other threads:[~2013-08-28 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 19:08 Bjorn Helgaas [this message]
2013-11-10 11:30 ` [PATCH] lspci: Decode PCIe Link registers only for devices with links Martin Mares
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=20130828190834.2198.99446.stgit@bhelgaas-glaptop \
--to=bhelgaas@google.com \
--cc=bhutchings@solarflare.com \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
/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