On Tue, 2014-12-16 at 09:20 -0700, Bjorn Helgaas wrote: > I think we're in this path: > > tg3_init_hw > tg3_reset_hw > tg3_disable_ints > tg3_stop_fw > tg3_write_sig_pre_reset > tg3_chip_reset > pci_device_is_present > pci_bus_read_dev_vendor_id > > and in this case pci_device_is_present() also passes a timeout of zero > to pci_bus_read_dev_vendor_id(). My guess is that tg3 is resetting > the device, so it's not too surprising that the config read returns > CRS status immediately afterward. > At the point of calling pci_device_is_present(), chip reset hasn't started yet, so there should be no problem reading config space. In all the newer tg3 chips, chip reset does not reset the PCIE block. So I think config space should always be accesible even during reset. > -- 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
