summaryrefslogtreecommitdiff
path: root/dts
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2015-09-03 05:37:24 -0700
committerSimon Glass <sjg@chromium.org>2015-09-09 07:48:03 -0600
commitaa09505ba1677c25e83115375a6775a5eae444ef (patch)
tree4d9f4501d233baf80582452bb190b1a2e1eb2c0c /dts
parent5750e5e29a4d4e90cb0ce3ec71233f8efbf5ebaa (diff)
downloadu-boot-imx-aa09505ba1677c25e83115375a6775a5eae444ef.zip
u-boot-imx-aa09505ba1677c25e83115375a6775a5eae444ef.tar.gz
u-boot-imx-aa09505ba1677c25e83115375a6775a5eae444ef.tar.bz2
x86: quark: Avoid chicken and egg problem
If we convert to use driver model pci on quark, we will encounter some chicken and egg problems like below: - To enable PCIe root ports, we need program some registers on the message bus via pci bus. With driver model, the first time to access pci bus, the pci enumeration process will be triggered. But without first enabling PCIe root ports, pci enumeration just hangs when scanning PCIe root ports. - Similar situation happens when trying to access GPIO from the PCIe enabling codes, as GPIO requires its block base address to be assigned via a pci configuration register in the bridge. To avoid such dilemma, replace all pci calls in the quark codes to use the local version which does not go through driver model. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'dts')
0 files changed, 0 insertions, 0 deletions