Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4463604pxf; Tue, 30 Mar 2021 08:24:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyd6/+yMYpGaEjsJyaz2KhcQYpvmPRZrcOvMuns2p7fAzYE6h1TxJ5rRHhp9kN/7CEaK2Ws X-Received: by 2002:a17:907:2093:: with SMTP id pv19mr34264123ejb.134.1617117894861; Tue, 30 Mar 2021 08:24:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617117894; cv=none; d=google.com; s=arc-20160816; b=hQQBkYFLJa9kaWzGED0mAtprCW3J5quh8P/SKKSwx91ermgNioAXx5LHkCmGzgD3vM BrxDTls+UXRmMKubCZcnwBB9feOyMt21jHVRJ8rg6123BKt9Qcbi761Xk+8wJnlZRg3N BzGeWbkoodIiJnmMgLL+AWDxj2gnMlXmBf4gdnzhGZ9L+5w8o3D0kkrzm5BnAiJypxvO 6ssc8dU/2RzUzEICeNuSy1OLUt37bZoKYLgo7aDD135uCvJaAIe7izAFeawKmaKfcS1e fajzVyJTootA+49/0XorfnROLhEVmJWdaNedsFGmvFBxGotE+AqcvD/H4ujTm/p/5/Ie Es0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:message-id:in-reply-to:subject:cc:to:from :date; bh=1Q2nPlTL7K7xU973DnM8RqxkuYn4dnF4JGtHNH5fFB0=; b=ZU14Ie0ZkVmupw9VRH1OnhoT2piTuRvdIIm9mJ0/q1uCEfielkXUBZoXdaFE5Y1+lt XETy4LY0r8f+Iqu1S0999YfQ0hL5rn5nCJ6IZfQ4xLRBBwizHh7KQUonDWKBpBc5ELp+ WWOHdt77+w26rfMwQ0y0siRUhN1OuiBL2KHDKBbgs7XQZUQaGBn+/oawyIsInZM9blRT 2prO24IfTLgTwBBGpny6QUSmqNmahVC2fRr6+Vx/9Uc1CMeJxs8B9z6jZZQWJArmUwbK IHHOJ88TmIT368+DhpDwPzwG3ECvGttVeBSB3w1ght0m+sORlNe8lDICLUuSee3oT3k5 yJ6Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t16si15725016edc.448.2021.03.30.08.24.31; Tue, 30 Mar 2021 08:24:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231701AbhC3PXH (ORCPT + 99 others); Tue, 30 Mar 2021 11:23:07 -0400 Received: from angie.orcam.me.uk ([157.25.102.26]:38218 "EHLO angie.orcam.me.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231808AbhC3PWx (ORCPT ); Tue, 30 Mar 2021 11:22:53 -0400 Received: by angie.orcam.me.uk (Postfix, from userid 500) id D62EC92009C; Tue, 30 Mar 2021 17:22:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id CEC7892009B; Tue, 30 Mar 2021 17:22:51 +0200 (CEST) Date: Tue, 30 Mar 2021 17:22:51 +0200 (CEST) From: "Maciej W. Rozycki" To: =?UTF-8?Q?Pali_Roh=C3=A1r?= cc: David Laight , 'Amey Narkhede' , "alex.williamson@redhat.com" , "helgaas@kernel.org" , "lorenzo.pieralisi@arm.com" , "kabel@kernel.org" , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "raphael.norwitz@nutanix.com" Subject: Re: How long should be PCIe card in Warm Reset state? In-Reply-To: <20210330150458.gzz44gczhraxc6bc@pali> Message-ID: References: <20210310110535.zh4pnn4vpmvzwl5q@pali> <20210323161941.gim6msj3ruu3flnf@archlinux> <20210323162747.tscfovntsy7uk5bk@pali> <20210323165749.retjprjgdj7seoan@archlinux> <20210330131018.gby4ze3u6mii23ls@pali> <20210330150458.gzz44gczhraxc6bc@pali> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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