From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: "Pali Rohár" <pali@kernel.org>
Cc: David Laight <David.Laight@ACULAB.COM>,
'Amey Narkhede' <ameynarkhede03@gmail.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"helgaas@kernel.org" <helgaas@kernel.org>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"kabel@kernel.org" <kabel@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"raphael.norwitz@nutanix.com" <raphael.norwitz@nutanix.com>
Subject: Re: How long should be PCIe card in Warm Reset state?
Date: Tue, 30 Mar 2021 17:22:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2103301714450.18977@angie.orcam.me.uk> (raw)
In-Reply-To: <20210330150458.gzz44gczhraxc6bc@pali>
On Tue, 30 Mar 2021, Pali Rohár wrote:
> > The spec does not give any exceptions AFAICT as to the timeouts required
> > between the three kinds of a Conventional Reset (Hot, Warm, or Cold) and
> > refers to them collectively as a Conventional Reset across the relevant
> > parts of the document, so clearly the same rules apply.
>
> There are specified more timeouts related to Warm reset and PERST#
> signal. Just they are not in Base spec, but in CEM spec. See previous
> Amey's email where are described some timeouts and also links in my
> first email where I put other timeouts defined in specs relevant for
> PERST# signal and therefore also for Warm Reset.
I specifically referred to the time allowed for devices to take between a
reset and the first successful configuration cycle David wondered about.
I don't think I can comment on the timeouts given in the CEM spec as I
don't have a copy. Sorry.
Maciej
next prev parent reply other threads:[~2021-03-30 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 11:05 How long should be PCIe card in Warm Reset state? Pali Rohár
2021-03-23 16:19 ` Amey Narkhede
2021-03-23 16:27 ` Pali Rohár
2021-03-23 16:57 ` Amey Narkhede
2021-03-25 9:18 ` David Laight
2021-03-30 13:04 ` Maciej W. Rozycki
2021-03-30 13:10 ` Pali Rohár
2021-03-30 14:34 ` Maciej W. Rozycki
2021-03-30 15:04 ` Pali Rohár
2021-03-30 15:22 ` Maciej W. Rozycki [this message]
2021-04-25 15:39 ` Pali Rohár
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=alpine.DEB.2.21.2103301714450.18977@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=David.Laight@ACULAB.COM \
--cc=alex.williamson@redhat.com \
--cc=ameynarkhede03@gmail.com \
--cc=helgaas@kernel.org \
--cc=kabel@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pali@kernel.org \
--cc=raphael.norwitz@nutanix.com \
/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).