diff options
| author | Lukas Wunner | 2019-03-20 12:05:30 +0100 |
|---|---|---|
| committer | Bjorn Helgaas | 2019-03-25 23:59:07 +0100 |
| commit | 0fa635aec9abd718bd18c0bda2261351a0811efc (patch) | |
| tree | 28feed152619c3557db954549f513abcb9bdc797 /drivers/pci/pci.h | |
| parent | PCI/LINK: Clear bandwidth notification interrupt before enabling it (diff) | |
| download | kernel-qcow2-linux-0fa635aec9abd718bd18c0bda2261351a0811efc.tar.gz kernel-qcow2-linux-0fa635aec9abd718bd18c0bda2261351a0811efc.tar.xz kernel-qcow2-linux-0fa635aec9abd718bd18c0bda2261351a0811efc.zip | |
PCI/LINK: Deduplicate bandwidth reports for multi-function devices
If a multi-function device's bandwidth is already limited when it is
enumerated, a message is logged only for function 0. By contrast, when
downtraining occurs after enumeration, a message is logged for all
functions. That's because the former uses pcie_report_downtraining(),
whereas the latter uses __pcie_print_link_status() (which doesn't filter
functions != 0). I am seeing this happen on a MacBookPro9,1 with a GPU
(function 0) and an integrated HDA controller (function 1).
Avoid this incongruence by calling pcie_report_downtraining() in both
cases.
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Alexandru Gagniuc <alex.gagniuc@dellteam.com>
Diffstat (limited to 'drivers/pci/pci.h')
| -rw-r--r-- | drivers/pci/pci.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h index 224d88634115..d994839a3e24 100644 --- a/drivers/pci/pci.h +++ b/drivers/pci/pci.h @@ -273,6 +273,7 @@ enum pcie_link_width pcie_get_width_cap(struct pci_dev *dev); u32 pcie_bandwidth_capable(struct pci_dev *dev, enum pci_bus_speed *speed, enum pcie_link_width *width); void __pcie_print_link_status(struct pci_dev *dev, bool verbose); +void pcie_report_downtraining(struct pci_dev *dev); /* Single Root I/O Virtualization */ struct pci_sriov { |