PCI: handle CRS response following Hot Reset and D3hot->D0
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 2/20 of 6 patches 0 repliesNew
- v3 posting 1/26 patches 0 repliesSuperseded
- v27 patches 11 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 | 5 patches | 10 replies | Superseded |
Patches in v3 posting 2/2 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH V3 0/6] PCI: handle CRS response following Hot Reset and D3hot->D0
Hi Bjorn,
Quoted 21 lines · Sinan Kaya
Rev 3.1 Sec 2.3.1 Request Handling Rules:
Valid reset conditions after which a device is permitted to return CRS are:
* Cold, Warm, and Hot Resets,
* FLR
* A reset initiated in response to a D3hot to D0 uninitializedTry to reuse FLR implementation towards other reset types.
Changes from v2:
* Correct Conventional PCI spec reference forAF_FLR
* Commit message update to capitilize the first word following colonSinan Kaya (6):
PCI: Protect restore with device lock to be consistent
PCI: Handle FLR failure and allow other reset types
PCI: Makepci_flr_wait()generic and rename topci_dev_wait()
PCI: Wait device ready afterpci_pm_reset()
PCI: Add a return type forpci_reset_bridge_secondary_bus()
PCI: Add device wait after slot and bus reset
Quoted 4 lines
drivers/pci/pci.c | 70 ++++++++++++++++++++++++++++++++++------------------- include/linux/pci.h | 4 +-- 2 files changed, 47 insertions(+), 27 deletions(-)
Do you think this is ready for merge or do you have more feedback?
Sinan
Signature · 3 lines
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.