diff options
author | Lucas Stach <l.stach@pengutronix.de> | 2019-02-27 17:52:19 +0100 |
---|---|---|
committer | Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> | 2019-03-01 12:05:45 +0000 |
commit | 3afc8299f39a27b60e1519a28e18878ce878e7dd (patch) | |
tree | 0eb1b2c208ca2437cdd9ef7294a58348b44eb6f3 /Documentation/block | |
parent | 44ddb77b2fdc6352a45ebc7b5804e4afe9161956 (diff) | |
download | linux-3afc8299f39a27b60e1519a28e18878ce878e7dd.tar.gz linux-3afc8299f39a27b60e1519a28e18878ce878e7dd.tar.bz2 linux-3afc8299f39a27b60e1519a28e18878ce878e7dd.zip |
PCI: dwc: skip MSI init if MSIs have been explicitly disabled
Since 7c5925afbc58 (PCI: dwc: Move MSI IRQs allocation to IRQ domains
hierarchical API) the MSI init claims one of the controller IRQs as a
chained IRQ line for the MSI controller. On some designs, like the i.MX6,
this line is shared with a PCIe legacy IRQ. When the line is claimed for
the MSI domain, any device trying to use this legacy IRQs will fail to
request this IRQ line.
As MSI and legacy IRQs are already mutually exclusive on the DWC core,
as the core won't forward any legacy IRQs once any MSI has been enabled,
users wishing to use legacy IRQs already need to explictly disable MSI
support (usually via the pci=nomsi kernel commandline option). To avoid
any issues with MSI conflicting with legacy IRQs, just skip all of the
DWC MSI initalization, including the IRQ line claim, when MSI is disabled.
Fixes: 7c5925afbc58 ("PCI: dwc: Move MSI IRQs allocation to IRQ domains hierarchical API")
Tested-by: Tim Harvey <tharvey@gateworks.com>
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Acked-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'Documentation/block')
0 files changed, 0 insertions, 0 deletions