I had old Marvell Sky2 hardware that had slow flash. -----Original Message----- From: Andrew Donnellan [mailto:andrew.donnellan@xxxxxxxxxxx] Sent: Monday, November 21, 2016 4:16 PM To: Bjorn Helgaas <helgaas@xxxxxxxxxx>; Matthew R. Ochs <mrochs@xxxxxxxxxxxxxxxxxx> Cc: linux-pci@xxxxxxxxxxxxxxx; Frederic Barrat <fbarrat@xxxxxxxxxxxxxxxxxx>; Uma Krishnan <ukrishn@xxxxxxxxxxxxxxxxxx>; Ian Munsie <imunsie@xxxxxxxxxxx>; Bjorn Helgaas <bhelgaas@xxxxxxxxxx>; linuxppc-dev@xxxxxxxxxxxxxxxx; Stephen Hemminger <sthemmin@xxxxxxxxxxxxx> Subject: Re: [PATCH 1/2] PCI: Add pci_set_vpd_timeout() to set VPD access timeout On 22/11/16 09:05, Bjorn Helgaas wrote: > Hi Matthew, > > On Mon, Nov 21, 2016 at 03:09:49PM -0600, Matthew R. Ochs wrote: >> The PCI core uses a fixed 50ms timeout when waiting for VPD accesses >> to complete. When an access does not complete within this period, a >> warning is logged and an error returned to the caller. >> >> While this default timeout is valid for most hardware, some devices >> can experience longer access delays under certain circumstances. For >> example, one of the IBM CXL Flash devices can take up to ~120ms in a >> worst-case scenario. These types of devices can benefit from an >> extended timeout that is specific to their hardware constraints. >> >> To support per-device VPD access timeouts, pci_set_vpd_timeout() is >> added as an exported service. PCI devices will continue to default >> with the 50ms timeout and use a per-device timeout when a driver calls this new service. > > Can you include a pointer to something in the spec that's behind the > default 50ms timeout, or did somebody just pull that number out of the > air? It looks like Stephen Hemminger added the 50ms timeout in 1120f8b8169f, which seems to indicate that 50ms was chosen because it's longer than the 13ms per word that was measured on one device. -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnellan@xxxxxxxxxxx IBM Australia Limited -- 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