aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/xway_legacy
diff options
context:
space:
mode:
authorMathias Kresin <dev@kresin.me>2019-06-23 20:17:08 +0200
committerMathias Kresin <dev@kresin.me>2019-07-04 08:29:13 +0200
commit961b8efb5b12fee42bec5b93ec31912af5eee995 (patch)
treecb361d3f3a03a60b5f5aa13fb4260ec9470c37de /target/linux/lantiq/xway_legacy
parenteb72439dbb4acc936cbabf16cb0683a5a230e897 (diff)
downloadupstream-961b8efb5b12fee42bec5b93ec31912af5eee995.tar.gz
upstream-961b8efb5b12fee42bec5b93ec31912af5eee995.tar.bz2
upstream-961b8efb5b12fee42bec5b93ec31912af5eee995.zip
lantiq: 4.19: load PCIe driver after PCI driver
In case a PCI device is physical present, the Lantiq PCI driver need to be loaded prior to the Lantiq PCIe driver. Otherwise none of them will work because updating the BAR 0 of a device attached to the PCIe Bus will fail. Till kernel commit 9667bb039bf6 ("MIPS: lantiq: remove unnecessary of_platform_default_populate call"), the Lantiq PCI driver was probed early in the boot process via plat_of_setup(). Since the mentioned commit, both drivers are probed via of_platform_default_populate_init() and they are probed according to their order in the devicetree source file. If the Lantiq PCI driver is enabled in the devicetree, defer the probing og the Lantiq PCIe driver till the Lantiq PCI driver is probed. Use the presence of a PCU bus as indicater for a loaded Lantiq PCI driver. This way we don't need to shuffle the PCI/PCIe nodes in the devicetree source file, as they are already (correctly) ordered based on the unit address. Signed-off-by: Mathias Kresin <dev@kresin.me>
Diffstat (limited to 'target/linux/lantiq/xway_legacy')
0 files changed, 0 insertions, 0 deletions