diff options
| author | Jon Hunter <jonathanh@nvidia.com> | 2020-02-14 16:53:53 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-04-23 11:38:03 +0300 |
| commit | 595f6853a92cb47d7da46c7a583693c9c5182cc6 (patch) | |
| tree | 5b0576bc112d0d0b09516e0a19396ba959f90e56 /drivers/vhost | |
| parent | 3cfb1d2a5744c230da7cc9639c8d6bd21f1653a7 (diff) | |
| download | linux-595f6853a92cb47d7da46c7a583693c9c5182cc6.tar.xz | |
arm64: tegra: Fix Tegra194 PCIe compatible string
[ Upstream commit f9f711efd441ad0d22874be49986d92121862335 ]
If the kernel configuration option CONFIG_PCIE_DW_PLAT_HOST is enabled
then this can cause the kernel to incorrectly probe the generic
designware PCIe platform driver instead of the Tegra194 designware PCIe
driver. This causes a boot failure on Tegra194 because the necessary
configuration to access the hardware is not performed.
The order in which the compatible strings are populated in Device-Tree
is not relevant in this case, because the kernel will attempt to probe
the device as soon as a driver is loaded and if the generic designware
PCIe driver is loaded first, then this driver will be probed first.
Therefore, to fix this problem, remove the "snps,dw-pcie" string from
the compatible string as we never want this driver to be probe on
Tegra194.
Fixes: 2602c32f15e7 ("arm64: tegra: Add P2U and PCIe controller nodes to Tegra194 DT")
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/vhost')
0 files changed, 0 insertions, 0 deletions