From: Sinan Kaya <okaya@codeaurora.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
timur@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Bjorn Helgaas <bhelgaas@google.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 3/7] PCI: make pci_flr_wait() generic and rename to pci_dev_wait()
Date: Mon, 4 Dec 2017 08:17:20 -0500 [thread overview]
Message-ID: <0248af7b-0459-2b77-e439-bfcdfebcd7f6@codeaurora.org> (raw)
In-Reply-To: <20171129173801.GD27742@infradead.org>
On 11/29/2017 12:38 PM, Christoph Hellwig wrote:
> On Mon, Nov 27, 2017 at 01:20:24AM -0500, 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.
>
> Should we keep a helper for the FLR wait? If not I guess the reference
> for AF_FLR should be the PCI spec, not the PCIE spec.
>
Bjorn,
what is your opinion?
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.
WARNING: multiple messages have this Message-ID (diff)
From: Sinan Kaya <okaya@codeaurora.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
timur@codeaurora.org, open list <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 3/7] PCI: make pci_flr_wait() generic and rename to pci_dev_wait()
Date: Mon, 4 Dec 2017 08:17:20 -0500 [thread overview]
Message-ID: <0248af7b-0459-2b77-e439-bfcdfebcd7f6@codeaurora.org> (raw)
In-Reply-To: <20171129173801.GD27742@infradead.org>
On 11/29/2017 12:38 PM, Christoph Hellwig wrote:
> On Mon, Nov 27, 2017 at 01:20:24AM -0500, 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.
>
> Should we keep a helper for the FLR wait? If not I guess the reference
> for AF_FLR should be the PCI spec, not the PCIE spec.
>
Bjorn,
what is your opinion?
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.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/7] PCI: make pci_flr_wait() generic and rename to pci_dev_wait()
Date: Mon, 4 Dec 2017 08:17:20 -0500 [thread overview]
Message-ID: <0248af7b-0459-2b77-e439-bfcdfebcd7f6@codeaurora.org> (raw)
In-Reply-To: <20171129173801.GD27742@infradead.org>
On 11/29/2017 12:38 PM, Christoph Hellwig wrote:
> On Mon, Nov 27, 2017 at 01:20:24AM -0500, 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.
>
> Should we keep a helper for the FLR wait? If not I guess the reference
> for AF_FLR should be the PCI spec, not the PCIE spec.
>
Bjorn,
what is your opinion?
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:[~2017-12-04 13:17 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 6:20 [PATCH V2 0/7] PCI: handle CRS response following Hot Reset and D3hot->D0 Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` [PATCH V2 1/7] PCI: protect restore with device lock to be consistent Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-29 17:36 ` Christoph Hellwig
2017-11-29 17:36 ` Christoph Hellwig
2017-11-29 17:36 ` Christoph Hellwig
2017-11-29 17:36 ` Christoph Hellwig
2017-11-27 6:20 ` [PATCH V2 2/7] PCI: handle FLR failure and allow other reset types Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-29 17:36 ` Christoph Hellwig
2017-11-29 17:36 ` Christoph Hellwig
2017-11-29 17:36 ` Christoph Hellwig
2017-11-29 17:36 ` Christoph Hellwig
2017-11-27 6:20 ` [PATCH V2 3/7] PCI: make pci_flr_wait() generic and rename to pci_dev_wait() Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-29 17:38 ` Christoph Hellwig
2017-11-29 17:38 ` Christoph Hellwig
2017-11-29 17:38 ` Christoph Hellwig
2017-12-04 13:17 ` Sinan Kaya [this message]
2017-12-04 13:17 ` Sinan Kaya
2017-12-04 13:17 ` Sinan Kaya
2017-12-13 22:43 ` Bjorn Helgaas
2017-12-13 22:43 ` Bjorn Helgaas
2017-12-13 22:43 ` Bjorn Helgaas
2018-01-02 15:47 ` Sinan Kaya
2018-01-02 15:47 ` Sinan Kaya
2017-11-27 6:20 ` [PATCH V2 4/7] PCI: wait device ready after pci_pm_reset() Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-29 17:38 ` Christoph Hellwig
2017-11-29 17:38 ` Christoph Hellwig
2017-11-29 17:38 ` Christoph Hellwig
2017-11-27 6:20 ` [PATCH V2 5/7] PCI: add a return type for pci_reset_bridge_secondary_bus() Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-29 17:38 ` Christoph Hellwig
2017-11-29 17:38 ` Christoph Hellwig
2017-11-29 17:38 ` Christoph Hellwig
2017-11-27 6:20 ` [PATCH V2 6/7] PCI: add device wait after slot and bus reset Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-29 17:39 ` Christoph Hellwig
2017-11-29 17:39 ` Christoph Hellwig
2017-11-29 17:39 ` Christoph Hellwig
2017-11-27 6:20 ` [PATCH V2 7/7] PCI: make reset poll time adjustable Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-27 6:20 ` Sinan Kaya
2017-11-28 14:20 ` Bjorn Helgaas
2017-11-28 14:20 ` Bjorn Helgaas
2017-11-28 14:20 ` Bjorn Helgaas
2017-11-28 14:26 ` Sinan Kaya
2017-11-28 14:26 ` Sinan Kaya
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=0248af7b-0459-2b77-e439-bfcdfebcd7f6@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=timur@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.