diff options
| author | Sinan Kaya <okaya@codeaurora.org> | 2017-08-29 14:45:44 -0500 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2017-08-29 14:45:44 -0500 |
| commit | 62bc6a6f7468bc6d6cb39177504e79df401aea76 (patch) | |
| tree | 0d53c180be8a502c7f8d0db3d23184346b37d162 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 9f98275671a58516f87b7eb02a3497635861930a (diff) | |
| download | linux-stable-62bc6a6f7468bc6d6cb39177504e79df401aea76.tar.gz linux-stable-62bc6a6f7468bc6d6cb39177504e79df401aea76.tar.bz2 linux-stable-62bc6a6f7468bc6d6cb39177504e79df401aea76.zip | |
PCI: Add pci_bus_crs_vendor_id() to detect CRS response data
Add pci_bus_crs_vendor_id() to determine whether data returned for a config
read of the Vendor ID indicates a Configuration Request Retry Status (CRS)
response.
Per PCIe r3.1, sec 2.3.2, this data is only returned if:
- CRS Software Visibility is enabled,
- a config read includes both bytes of the Vendor ID, and
- the read receives a CRS completion
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
[bhelgaas: changelog, change name to pci_bus_crs_vendor_id(), make static
in probe.c, use it in pci_bus_read_dev_vendor_id()]
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions