summaryrefslogtreecommitdiffstats
path: root/drivers/pci/msi.c
diff options
context:
space:
mode:
authorAndrew Lunn <andrew@lunn.ch>2014-02-05 11:55:49 +0100
committerBjorn Helgaas <bhelgaas@google.com>2014-02-12 14:05:54 -0700
commit322a8e91844f4ae2093e0d3d8a318d0ef2596756 (patch)
treee69832b32b65e8cc04aa9c46de797306d147fef9 /drivers/pci/msi.c
parent38dbfb59d1175ef458d006556061adeaa8751b72 (diff)
downloadop-kernel-dev-322a8e91844f4ae2093e0d3d8a318d0ef2596756.zip
op-kernel-dev-322a8e91844f4ae2093e0d3d8a318d0ef2596756.tar.gz
PCI: mvebu: Use Device ID and revision from underlying endpoint
Marvell SoCs place the SoC number into the PCIe endpoint device ID. The SoC stepping is placed into the PCIe revision. The old plat-orion PCIe driver allowed this information to be seen in user space with a simple lspci command. The new driver places a virtual PCI-PCI bridge on top of these endpoints. It has its own hard coded PCI device ID. Thus it is no longer possible to see what the SoC is using lspci. When initializing the PCI-PCI bridge, set its device ID and revision from the underlying endpoint, thus restoring this functionality. Debian would like to use this in order to aid installing the correct DTB file. Fixes: 45361a4fe4464 ("pci: PCIe driver for Marvell Armada 370/XP systems") Signed-off-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Jason Cooper <jason@lakedaemon.net> Cc: stable@vger.kernel.org # v3.11+
Diffstat (limited to 'drivers/pci/msi.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud