summaryrefslogtreecommitdiffstats
path: root/include/pci.h
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2015-07-08 13:06:40 +0800
committerSimon Glass <sjg@chromium.org>2015-07-14 18:03:20 -0600
commit6c89663cb152bb49f7618f283d999c417fd85746 (patch)
tree6486961d773dd8cbd849a890b19f1117d0154c65 /include/pci.h
parente1783b5ba3d32c0471a2b963ebec54e7e7cde264 (diff)
downloadblackbird-obmc-uboot-6c89663cb152bb49f7618f283d999c417fd85746.tar.gz
blackbird-obmc-uboot-6c89663cb152bb49f7618f283d999c417fd85746.zip
pci: Configure expansion ROM during auto config process
Currently PCI expansion ROM address is assigned by a call to pciauto_setup_rom() outside of the pci auto config process. This does not work when expansion ROM is on a device behind PCI bridge where bridge's memory limit register was already programmed to a value that does not cover the newly assigned expansion ROM address. To fix this, we should configure the ROM address during the auto config process. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'include/pci.h')
-rw-r--r--include/pci.h9
1 files changed, 0 insertions, 9 deletions
diff --git a/include/pci.h b/include/pci.h
index 3af511b38d..542e68bceb 100644
--- a/include/pci.h
+++ b/include/pci.h
@@ -722,15 +722,6 @@ void pci_write_bar32(struct pci_controller *hose, pci_dev_t dev, int barnum,
u32 pci_read_bar32(struct pci_controller *hose, pci_dev_t dev, int barnum);
/**
- * pciauto_setup_rom() - Set up access to a device ROM
- *
- * @hose: PCI hose to use
- * @dev: PCI device to adjust
- * @return 0 if done, -ve on error
- */
-int pciauto_setup_rom(struct pci_controller *hose, pci_dev_t dev);
-
-/**
* pci_hose_find_devices() - Find devices by vendor/device ID
*
* @hose: PCI hose to search
OpenPOWER on IntegriCloud