From: Scott Wood <scottwood@freescale.com>
To: Stefani Seibold <stefani@seibold.net>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BUG: no PCI/PCIe devices found in 85xx architecture
Date: Tue, 25 Jun 2013 18:46:35 -0500 [thread overview]
Message-ID: <1372203995.8183.26@snotra> (raw)
In-Reply-To: <1372185614.4726.12.camel@wall-e> (from stefani@seibold.net on Tue Jun 25 13:40:14 2013)
On 06/25/2013 01:40:14 PM, Stefani Seibold wrote:
> Hi,
>=20
> there is a bug in kernel 3.9 which the new fsl_pci platform driver. =20
> The
> pcibios_init in pci_32.c will be called before the platform driver =20
> probe
> will be invoked.
>=20
> The call order for a p2020 board with linux 3.9 is currently:
>=20
> fsl_pci_init
> pcibios_init
> fsl_pci_probe
> fsl_pci_probe
> fsl_pci_probe
>=20
> Therefore the PCI/PCIe bridge will be added after the PCI/PCIe busses
> was scanned for devices. So no PCI/PCIe devices are available.
>=20
> Everything works fine by reverting the fsl_pci.[ch] to the version in
> linux 3.4, because the PCI/PCIe bridges will be added in
> the ..._setup_arch() function, before the pcibios_init function is
> called.
>=20
> Any solution for this issue?
I can't reproduce this on p3041 -- pcibios_init gets called after =20
fsl_pci_probe, and its PCIe e1000 gets detected and used.
fsl_pci_probe should be called when of_platform_bus_probe is called, =20
which is in a machine_arch_initcall. pcibios_init is a =20
subsys_initcall, which should happen later.
Which p2020 board are you using? Could you check when it is calling =20
of_platform_bus_probe?
-Scott=
next prev parent reply other threads:[~2013-06-25 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 18:40 BUG: no PCI/PCIe devices found in 85xx architecture Stefani Seibold
2013-06-25 23:46 ` Scott Wood [this message]
2013-06-26 5:21 ` Stefani Seibold
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=1372203995.8183.26@snotra \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stefani@seibold.net \
/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;
as well as URLs for NNTP newsgroup(s).