On Fri, Sep 4, 2015 at 9:44 AM, Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx> wrote: > On Fri, Sep 04, 2015 at 05:00:35PM +0100, Yinghai Lu wrote: > > The problem here is not the last retry, it is the first bridge scan. > > By moving pci_read_bridge_bases() to core PCI code, if we do not > vet the bridge apertures (ie claim them and reset them if the claiming > fails) we end up calling (on ARM) __pci_bus_size_bridges() with apertures > that can have sizes != 0, which does not make any sense since we are calling > __pci_bus_size_bridges() to *discover* what the aperture size should > be on first bridge scan, correct ? for x86, in pcibios_allocate_bridge_resources(), we do validate the bridge resources, and reset size to 1 (strange ?!). and they are called before pci_asssign_unassigned_resources() so arch ARM would support pcibios_allocate_bridge_resources or other call to do the same thing? wonder some arches even claim fails, they still does not want you to reset it. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
