Skip to contentSkip to conversation

BUG: no PCI/PCIe devices found in 85xx architecture

DISCUSSION Stefani Seibold 2 participants 3 messages Jun 25, 2013 – Jun 26, 2013

lore
Share & tools
lore
#0 lore raw

Hi,

there is a bug in kernel 3.9 which the new fsl_pci platform driver. The pcibios_init in pci_32.c will be called before the platform driver probe will be invoked.

The call order for a p2020 board with linux 3.9 is currently:

fsl_pci_init
pcibios_init
fsl_pci_probe
fsl_pci_probe
fsl_pci_probe

Therefore the PCI/PCIe bridge will be added after the PCI/PCIe busses was scanned for devices. So no PCI/PCIe devices are available.

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.

Any solution for this issue?

- Stefani

#1 lore raw
Quoted 17 lines · Stefani Seibold

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

Quoted 8 lines

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=

#2 lore raw

Am Dienstag, den 25.06.2013, 18:46 -0500 schrieb Scott Wood:

Quoted 30 lines · Stefani Seibold
Quoted 19 lines

Hi,

there is a bug in kernel 3.9 which the new fsl_pci platform driver. The
pcibios_init in pci_32.c will be called before the platform driver probe
will be invoked.

The call order for a p2020 board with linux 3.9 is currently:

fsl_pci_init
pcibios_init
fsl_pci_probe
fsl_pci_probe
fsl_pci_probe

Therefore the PCI/PCIe bridge will be added after the PCI/PCIe busses was scanned for devices. So no PCI/PCIe devices are available.

Quoted 6 lines

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.

Any solution for this issue?

I can't reproduce this on p3041 -- pcibios_init gets called after fsl_pci_probe, and its PCIe e1000 gets detected and used.

Quoted 8 lines

fsl_pci_probe should be called when of_platform_bus_probe is called, which is in a machine_arch_initcall. pcibios_init is a subsys_initcall, which should happen later.

Which p2020 board are you using? Could you check when it is calling of_platform_bus_probe?

-Scott

Great, you are my hero. This is the solution.

In my old board support package for the kernel 3.4 there was a machine_device_initcall(). I did not saw the tiny difference against machine_arch_initcall() used by the other 85xx boards as i ported it to 3.9.

Thanks

- Stefani