From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/6] PCI: handle CRS response following Hot Reset and D3hot->D0
Date: Sun, 25 Feb 2018 17:25:09 -0500 [thread overview]
Message-ID: <9826c7b4-8ebc-e70b-ab21-bc2ec7af8a14@codeaurora.org> (raw)
In-Reply-To: <1514912423-13341-1-git-send-email-okaya@codeaurora.org>
Hi Bjorn,
On 1/2/2018 12:00 PM, Sinan Kaya wrote:
> 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 uninitialized
>
> Try to reuse FLR implementation towards other reset types.
>
> Changes from v2:
> * Correct Conventional PCI spec reference for AF_FLR
> * Commit message update to capitilize the first word following colon
>
> Sinan Kaya (6):
> PCI: Protect restore with device lock to be consistent
> PCI: Handle FLR failure and allow other reset types
> PCI: Make pci_flr_wait() generic and rename to pci_dev_wait()
> PCI: Wait device ready after pci_pm_reset()
> PCI: Add a return type for pci_reset_bridge_secondary_bus()
> PCI: Add device wait after slot and bus reset
>
> 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
--
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.
next prev parent reply other threads:[~2018-02-25 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 17:00 [PATCH V3 0/6] PCI: handle CRS response following Hot Reset and D3hot->D0 Sinan Kaya
2018-01-02 17:00 ` [PATCH V3 1/6] PCI: Protect restore with device lock to be consistent Sinan Kaya
2018-01-02 17:00 ` [PATCH V3 2/6] PCI: Handle FLR failure and allow other reset types Sinan Kaya
2018-01-02 17:00 ` [PATCH V3 3/6] PCI: Make pci_flr_wait() generic and rename to pci_dev_wait() Sinan Kaya
2018-01-02 17:00 ` [PATCH V3 4/6] PCI: Wait device ready after pci_pm_reset() Sinan Kaya
2018-01-02 17:00 ` [PATCH V3 5/6] PCI: Add a return type for pci_reset_bridge_secondary_bus() Sinan Kaya
2018-01-02 17:00 ` [PATCH V3 6/6] PCI: Add device wait after slot and bus reset Sinan Kaya
2018-02-25 22:25 ` Sinan Kaya [this message]
2018-02-27 20:15 ` [PATCH V3 0/6] PCI: handle CRS response following Hot Reset and D3hot->D0 Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9826c7b4-8ebc-e70b-ab21-bc2ec7af8a14@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).