From: Ed Swarthout <Ed.Swarthout@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Start pci hose scan from current busno
Date: Tue, 6 Mar 2007 01:02:34 -0600 [thread overview]
Message-ID: <11731645542307-git-send-email-Ed.Swarthout@freescale.com> (raw)
Start the pci hose scan from hose->current_busno instead of
first_busno. This allows the PCIe controllers to be scanned
downstream from bridge.
Ensure hose->current_busno is equal or greater than first_busno. This
fixes broken board code which leave current_busno=0 when first_busno
is greater than 0 for the cases with multiple controllers.
Signed-off-by: Ed Swarthout <Ed.Swarthout@freescale.com>
---
This change will simplify the pending common PCI and PCIe code for the
fsl 85xx and 86xx soc boards.
drivers/pci.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/drivers/pci.c b/drivers/pci.c
index 050582f..4158919 100644
--- a/drivers/pci.c
+++ b/drivers/pci.c
@@ -490,10 +490,16 @@ int pci_hose_scan_bus(struct pci_controller *hose, int bus)
int pci_hose_scan(struct pci_controller *hose)
{
+ /* Start scan at current_busno.
+ * PCIe will start scan at first_busno+1.
+ */
+ /* For legacy support, ensure current>=first */
+ if (hose->first_busno > hose->current_busno)
+ hose->current_busno = hose->first_busno;
#ifdef CONFIG_PCI_PNP
pciauto_config_init(hose);
#endif
- return pci_hose_scan_bus(hose, hose->first_busno);
+ return pci_hose_scan_bus(hose, hose->current_busno);
}
void pci_init(void)
--
1.5.0.2.279.g4808
next reply other threads:[~2007-03-06 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 7:02 Ed Swarthout [this message]
2007-03-06 15:18 ` [U-Boot-Users] [PATCH] Start pci hose scan from current busno Jon Loeliger
2007-03-06 16:08 ` Andy Fleming
2007-03-13 2:25 ` Kumar Gala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11731645542307-git-send-email-Ed.Swarthout@freescale.com \
--to=ed.swarthout@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox