Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1702457
| From | Sinan Kaya <okaya@codeaurora.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V7 1/3] PCI: limit FLR wait time to 100ms maximum |
| Date | 2017-08-02 22:40 +0200 |
| Message-ID | <ua8AV-6r3-11@gated-at.bofh.it> (permalink) |
| References | <ua7lv-5EM-9@gated-at.bofh.it> <ua8rh-6nd-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 8/2/2017 4:27 PM, Bjorn Helgaas wrote: > I haven't worked through all the details of what 6.6.2 says, but I > think it uses 100ms in the context of the *minimum* time software must > wait between initiating an FLR and initializing the function Here is what spec says in 6.6.2 "After an FLR has been initiated by writing a 1b to the Initiate Function Level Reset bit, the Function must complete the FLR within 100 ms." I interpret this as maximum. -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH V7 1/3] PCI: limit FLR wait time to 100ms maximum Sinan Kaya <okaya@codeaurora.org> - 2017-08-02 21:20 +0200
[PATCH V7 2/3] PCI: handle CRS returned by device after FLR Sinan Kaya <okaya@codeaurora.org> - 2017-08-02 21:20 +0200
[PATCH V7 3/3] PCI: display not responding message while device is unreachable Sinan Kaya <okaya@codeaurora.org> - 2017-08-02 21:20 +0200
Re: [PATCH V7 1/3] PCI: limit FLR wait time to 100ms maximum Bjorn Helgaas <helgaas@kernel.org> - 2017-08-02 22:30 +0200
Re: [PATCH V7 1/3] PCI: limit FLR wait time to 100ms maximum Sinan Kaya <okaya@codeaurora.org> - 2017-08-02 22:40 +0200
Re: [PATCH V7 1/3] PCI: limit FLR wait time to 100ms maximum Sinan Kaya <okaya@codeaurora.org> - 2017-08-02 23:30 +0200
csiph-web